Subject: Re: ISA driver name clashes (Was: Fortran And Ethernet)
To: None <firstname.lastname@example.org>
From: Niklas Hallqvist <email@example.com>
Date: 08/06/1995 22:34:06
Date: Sat, 5 Aug 1995 15:08:29 +0200
From: Ignatios Souvatzis <firstname.lastname@example.org>
It's of course possible, but imagine the inertia to force the largest
port to rename their drivers just because other ports want to use
them. I wonder how many people with amiga's uses if_le.c or if_ed.c,
compared to them with i386's? Anyway I can provide patches for both
if_le.c and if_ed.c if it'll be the amiga-port that changes. This is
part of the ISA-kit for Amiga.
The right thing to do would be to have a chips specific driver, and a
machine/bus specific frontend. Thats, at least, what I plan to do for
the ARCnet driver for SMC90C65 boards on ISA.
Yep, I've thought about this, that's what we did on the SCSI drivers
on the Amiga, with DMA softc's. But, I didn't want to get involved in
major driver redsign, just because I wan't to provide an ISA kit fro
the Amiga platfdorm.
This way, the names would even be the sames... you could even have, on
a, lets say, ISA + ZBUS Amiga, bah0 at zbus0 and bah1 at isabus0.
Nah, don't know about that. It would rather get unique names from the
bus-specific driver source, still like the Amiga 33C93 scsi drivers,
ahsc, atsc, gtsc et. al. The configuration facility don't let you
select different source files when using different X at Y constructs.