On Wednesday 24 May 2006 12:45, Luck, Tony wrote: > I've been thinking of dropping CONFIG_IA32_SUPPORT completely from ia64. > I've heard no complaints that new syscalls are not being added to the > ia32 compat side ... which is an indication that people are not > actively using this. Or maybe the people using ia32 compatibility are just running big apps like Firefox or Open Office that are non-trivial to build for ia64, but may not care as much about shiny new syscalls. Later, Tony wrote: > > Are there any users left? > I've no idea. Two OSDs have been shipping the Intel s/w emulator for > a while now, one installs it by default. So the number of users is > probably diminishing. When people upgrade to Montecito, s/w emulation > is the only option, which will further reduce the user population. I'm a bit worried about this. As I understand it, the Intel software emulator is not open-source. There may be distros like Debian and customer environments where that's not a viable alternative. If we remove CONFIG_IA32_SUPPORT, every ia64 box will require the Intel emulator (or QEMU or some other ill-defined solution) in order to run ia32 code, even though every processor in the field today supports ia32 in hardware. It doesn't feel right to me to remove functionality from machines in the field and offer only a proprietary alternative. Bjorn - : send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
![]() |