hi,

well, that's a start.  I was hoping we could be even more aggressive,
to the point where all the code is MI and the MD part is just a table
(like you've got the majors as a table now).  now that I think about it,
there are probably MD device names that conflict between different platforms
but we can probably get pretty close.  it would also be nice to be able to
do something like "env MACHINE=sparc sh MAKEDEV all" on a pc, ie. have
all the scripts there on all platforms to allow cross-setup.


I was thinking we could end up with:

	MAKEDEV			MI code, with no MD information at all
	MAKEDEV.$MACHINE	MD code (for MD devices) and MD data
				(selection of disk_minor_flavor and such)
	MAKEDEV.$MACHINE.majors	generated MD major table


how does that sound?

-Chuck


On Wed, Sep 04, 2002 at 01:45:28AM +0900, MAEKAWA Masahide wrote:
> Chuck Silvers <chuq@chuq.com> wrote:
> >how about making MAKEDEV entire table-driven and having the
> >script itself common to all platforms?  it would be nice
> >to not have to update all the scripts when adding a new driver.
> >there would be more to parameterize than just the major numbers,
> >but it doesn't seem like there are all *that* many different variants.
> 
> How about this?
>      http://gehenna.as.wakwak.ne.jp/dev/new-makedev/
> 
> MAKEDEV.<arch> - machine dependent part (installed as MAKEDEV)
> MAKEDEV.majors - machine dependent major list (generate by devmajors.awk)
> 
> machine independent parts:
> 
> MAKEDEV.isdn
>         pseudo
>         scsipi
>         subr
>         usb
>         wscons
>         ...
> 
> Machine independent parts called from MD-MAKEDEV and shared with all ports.
> 
> These are imcomplete yet, but reduced total script size.
> 
> --- MAEKAWA Masahide
> --- Key fingerprint = BC5E D8CB 816C 2CB5 8560  FDE3 6CB8 BF5D 8D50 F2EE