Subject: Re: Intent to mkdir sys/arch/arm
To: matthew green <mrg@eterna.com.au>
From: Chris Gilbert <chris@buzzbee.freeserve.co.uk>
List: port-arm32
Date: 01/08/2001 22:49:46
On Thursday 04 January 2001  3:15 am, matthew green wrote:
> I'd like a place to put shared arm26/arm32 kernel source code (and more
>    importantly, header files), and I'd rather not wait for sys/cpu to
> become a reality before I get it.  Thus, I plan to create sys/arch/arm
> (following the precedent of sys/arch/m68k, sys/arch/mips and
> sys/arch/powerpc) in a week or so, unless someone can come up with a better
> solution and implement it in a reasonable time.
>
>    I agree that sys/cpu/arm is ultimately where this code should end up,
> but only when all the other CPU-specific code is moved to sys/cpu.  I don't
> want to wait that long to start sharing code with arm32.
>
>
>
> i see no reason you can't just use /sys/cpu/arm *now*, besides that we've
> not moved anything there yet.  be bold!  be first!

Sounds good to me.  (Note I'm working on getting my riscpc uptodate with 
-current so I'll be in a better position to help on this kinda thing (I've 
finally sorted out having a local CVS repository (although it eats disk space 
having the anoncvs one, the local one, and then finally the working area, ah 
well)

Cheers,
Chris