Subject: Re: Sparc port names (was Re: Memory leak?)
To: None <is@Beverly.Rhein.DE>
From: None <kpneal@eos.ncsu.edu>
List: current-users
Date: 02/19/1996 13:45:26
> 
> Jason Thorpe (thorpej@nas.nasa.gov) wrote:
> : On Sat, 10 Feb 1996 14:45:14 -0500 (EST) 
> :  Aaron Brown <abrown@eecs.harvard.edu> wrote:
> : 
> :  > Actually, the intent is to merge the sun4m port into the sun4/sun4c port, 
> :  > so one kernel will boot on any sun4/4c/4m sparc machine. Thus 
> :  > NetBSD/sparc seems like a fine name for now, since there are no 
> :  > sun4d/sun4u ports yet.
> : 
> : Well, arguably, it should be NetBSD/sunsparc, but changing it now would 
> : be ... dumb :-)  One of these days, we could probably abstract the CPU 
> : chip stuff and make a sys/arch/cpu/sparc .. :-)
> 
> Ok. Please start with m68k, 
> - moving all of sys/arch/m68k to sys/arch/cpu/m68k 
> - fixing all references in the (6 ?) m68k ports we have.
> 
> :-)
> 
> Regards,
> 	Ignatios Souvatzis
> 

Actually, with a find and a sed script this would not be that big
of a deal. 

If somebody does this, will it get put in? I think it is a good
idea to sep. the cpu code into a specific directory for cpus.
 
XCOMM --------------------------------------------------------
XCOMM Kevin P. Neal, Sophomore CSC/CPE     kpneal@eos.ncsu.edu 
XCOMM North Carolina State University      kevinneal@bix.com
XCOMM --------------------------------------------------------