> Currently you place the voyager information in the APM table, which is problematic
> for the goal of being able to have a kernel that will support everything,
> and it is a little confusing.
Kernels for many of the x86 subarch's that are popping up won't "do the
right thing" on any 'normal' x86 if memory serves me correctly. For eg
a kernel for IBM summit machines won't work on a regular PC.
Getting them to do so would require things like apic.c to become an even
bigger mess than what it currently is
The idea behind the subarch patches is that you get a kernel
specifically for your weirdo machine, whilst keeping the common code
free of ifdefs and other uglies. So we'd end up with perhaps..
o regular i386 boot on any PC kernel
(also things like Athlon etc optimised ones fit here)
o IBM summit kernel
o NCR Voyager kernel
o SGI visws kernel
o Whatever other weirdo subarch pops up.
-- | Dave Jones. http://www.codemonkey.org.uk | SuSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/