The best solution for niche x86 architectures is to get x86-subarch
support merged first (See how arch/arm is laid out for an example)
James also has patches to do this, but there are a few other bits
pending in this area right now, such as Patrick Mochels work to split
up some of the larger parts. The bigger chunk of this is in my tree,
and has proven to be ok, so I'm pushing that to Linus sometime real
soon.
With that out of the way, the only remaining work in that area
is of small enough scale (apart from ACPI perhaps) that merging
the subarch support should be a logical progression.
And with that merged, things like Voyager, NUMAQ, and other weirdo
x86en can follow on without disrupting any of the common x86 code
that 99.9% of people will be running.
So it's not being ignored, it's just that trying to fit together
a puzzle whilst all the players want to put a piece in the same
place needs an element of coordination.
Dave.
-- | 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/