> In article <m2n.s.148iGY-000pkG@chiark.greenend.org.uk> you write:
> >	Given the discussions on a common ELF format for arm26 and arm32
> >	code, might it make more sense to work towards a common 'arch/arm'
> >	and then separate arm26, riscpc, shark, cats, and others ports.
> 
> Actually, I think there'll still be a need for some common arm32 code for
> locore-type stuff, the pmap etc.
> 
> I suspect the thing to do for a new arm32 platform would be to import it as
> a new port, pulling in arm32 bits as necessary, and use this as an
> opportunity to work out what needs changing in the arm32 tree to allow
> separate ports.  Then, as we get maintainers for the new ports, they can
> sort out separating them.

It was my understanding that a "port" (at least in the kernel source tree) 
should be defined by the ability to boot from a single GENERIC kernel.  
That would certainly never be the case between the ARM26 and ARM32 worlds. 
 The question is whether it will ever be possible between cats, RISC PC, 
and shark etc.  If they can (in theory) run from a single kernel, then the 
sources should stay together, if not, then there should probably be a 
split.

R.