> i dont think "clean, modern x86 code" will ever happen - x86_64 has and 
quoted text
> is going to have the exact same type of crap. And i'll say a weird thing 

Yes, but it will be new crap, but no old crap anymore.

If you always pile the new crap on the old crap at some point
the whole thing might fall over. 64bit was intended as a fresh start.

Admittedly we're getting more and more workarounds too and sometimes
when I want to remove cruft i find out it is still needed on some
64bit boxes (e.g. see my repeated attempts to clean up the irq 0
routing), but it's still much better than i386.

quoted text
> I think the PowerPC experience (although it is not a fully equivalent 
> case) about them merging their 32-bit and 64-bit architectures was an 
> overwhelmingly positive move, and x86 could learn a thing or two from 
> that.

The equivalent to the powerpc way would be essentially to report i386
into the x86-64 code base and leave the really old hardware only
in arch/i386. I've considered doing it, but it would be an awful
lot of work and to tempt distributions to actually use the new
port would require going back quite a long time. And at least
immediately it would end up with three cases to do things instead
of two like currently.

-Andi

-
unsubscribe notice
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/