Subject: Re: Driver to device bindings
To: None <tech-kern@NetBSD.org>
From: Matt Thomas <email@example.com>
Date: 12/28/2003 13:46:24
At 12:13 PM 12/28/2003, Perry E. Metzger wrote:
>Manuel Bouyer <firstname.lastname@example.org> writes:
> > On Fri, Dec 26, 2003 at 10:09:53AM +0200, Mike M. Volokhov wrote:
> >> Greetings!
> >> Probably, this is already discussed topic, but let me ask once more.
> >> Let say I have some device (for example, NIC) and it is newest clone of
> >> some other well known NIC. This means, I have a drivers for it, but
> >> config_match() is not recognizes my NIC (please correct me if I am
> >> wrong). So, is it possible to specify in my kernel config to bind some
> >> driver to that device?
> > No, you need to update the driver itself to attach to the new
> > vendor/device ID for this.
>It might be neat if, instead, we could keep a table binding drivers to
>PCI IDs etc. separately so that people could update it without having
>to update the drivers themselves.
That doesn't really help. In addition to the PCI Vendor/Device ID (or
subsystem IDs), you will probably need a driver-dependent glob to actually
tell the driver the capabilities of the device. wm, bge, siop, esiop, tlp,
ahc, etc. all need that info as well as the PCI vendor/device ID.
Matt Thomas email: email@example.com
3am Software Foundry www: http://3am-software.com/bio/matt/
Cupertino, CA disclaimer: I avow all knowledge of this message.