Messages in this thread | | | Date | Wed, 15 Apr 1998 15:26:18 +0200 | From | Martin Mares <> | Subject | Re: 2.1.93.. |
| |
Hi,
> I disagree. There is no fundamental reason that either ordering is more > "correct" for network cards. Here we have historical precedent to deal with, > but that's all. It is not completely outrageous to change the ordering if > sufficient warning is given.
I think we should preserve the same ordering as we had in 2.0 and solve this finally in 2.3 by introducing a resource manager and devfs.
> With BusLogic SCSI and Mylex DAC960 boards that have their own BIOS there is a > more fundamental issue: the BIOS itself iterates using the PCI BIOS function in > order to determine the order of board recognition (and hence which device to > boot from), and this information *must* be available to the driver.
I still don't understand why is ordering in BusLogic driver more important than ordering anywhere else. Is there any reason for handling the bootup SCSI controller different than the rest?
> Hence my proposal: The kernel finds the devices directly using direct access > which avoids PCI BIOS problems, and the PCI BIOS pcibios_find_device function > is only used when requested by a driver, but the information from the direct > probe is returned. That is the minimum possible use of the PCI BIOS, is it > not?
I definitely think the same would be needed for other drivers, so it can be simply solving by preserving BIOS ordering whenever BIOS is enabled.
Have a nice fortnight -- Martin `MJ' Mares <mj@ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth "A student who changes the course of history is probably taking an exam."
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |