Subject: Re: "esp" driver reorg proposal
To: Jason Thorpe <email@example.com>
From: Chris G. Demetriou <firstname.lastname@example.org>
Date: 01/25/1997 21:47:14
> Ok... since it's going to live in sys/dev/ic... :-)
> sys/dev/ic/ncr53c9x.c (note, lack of "esp" and "asc" :-)
> sys/arch/alpha/tc/esp.c (not on tc; really on tcds)
> sys/arch/sparc/dev/esp.c (multiple attachments in one file)
Actually, on the alpha, i'd call it 'asc'... 8-)
> I do _not_ like the notion of <machine/espvar.h>, or whatever. That
> doesn't scale; perhaps you have some weird machine that has a 53c9x
> on two very different busses... "oops!"
It's not just a matter of this...
If every driver using MI code starts requiring a header in <machine>,
things quickly get out of hand...
> The functionality that is provided by the current macros in the header
> files could be provided by function pointers.
> I'd also like to see softc layering a'la the MI 5380 driver. (That
> even allows ports to arbitrarily rename it :-)