Re: Putting PCI-class/vendor/deviceinfo into source of PCI-drivers

Magnus Damm (damm@kieraypc01.p.y.ki.era.ericsson.se)
Mon, 29 Nov 1999 17:13:44 +0100

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Richard B. Johnson: "Re: printk"
Previous message: Magnus Damm: "Re: Putting PCI-class/vendor/deviceinfo into source of PCI-drivers"
Maybe in reply to: Jochen Dolze: "Putting PCI-class/vendor/deviceinfo into source of PCI-drivers"

> Each has its own problems. The first has a centralized database that can
> become corrupted. Provided this is just a text file, you can probably fix
> it. It is still a pain. The second method has the problem that you have to
> have at least the routine to register the device and recognize it's device
> IDs loaded. If this is happening at kernel level, that is not a happy thing.
> If it is happening at application level, you now have two different
> executables for a single device driver. Yuch!

Sorry, I'm a bit slow... =)

No, we don't want two executables / driver.

How do other OS:es solve this problem?

/ magnus

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Richard B. Johnson: "Re: printk"
Previous message: Magnus Damm: "Re: Putting PCI-class/vendor/deviceinfo into source of PCI-drivers"
Maybe in reply to: Jochen Dolze: "Putting PCI-class/vendor/deviceinfo into source of PCI-drivers"