Subject: Re: Driver to device bindings
To: None <email@example.com>
From: Ignatios Souvatzis <firstname.lastname@example.org>
Date: 12/29/2003 20:49:59
Content-Type: text/plain; charset=us-ascii
On Mon, Dec 29, 2003 at 10:51:17AM -0500, Christos Zoulas wrote:
> It is the chicken and egg problem. You'd need to store the information
> about which driver maps to which id somewhere, and that somewhere needs
> to be able to be dynamically updated as you add new drivers. We currently
> take the approach that it is better for the driver to know which variants
> of the device it supports (so that the driver can do different things
> depending on the device flavor) rather than the kernel telling the driver
> this is what kind of card you have.
I don't think a full table is necessary for the problem presented up there.
Instead, I'd implement a "replace prod/id x/y with prod/id z/w when
searching the PCI table" - or rather something slightly more generic
that can be used for Cardbus, PCMCIA, Zorro, SBUS, Podule, and I
suspect USB and Firewire additionaly.
For more than that functionality, you'd need to change the driver anyway,
or write a new one.
Now, supporting loadable modules is a different problem.
seal your e-mail: http://www.gnupg.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
-----END PGP SIGNATURE-----