Messages in this thread | | | Date | Tue, 4 Mar 2003 17:57:00 -0500 | From | Jeff Garzik <> | Subject | Re: Displaying/modifying PCI device id tables via sysfs |
| |
On Tue, Mar 04, 2003 at 02:22:13PM -0600, Kai Germaschewski wrote: > On 3 Mar 2003, Matt Domsch wrote: > > > /sys > > `-- bus > > `-- pci > > `-- drivers > > `-- 3c59x > > |-- dynamic_id_0 (these are simple DRIVER_ATTRs) > > |-- dynamic_id_1 > > |-- dynamic_id_2 > > `-- new_id > > > > Where dynamic_id_[012] are new dynamic entries, created by writing > > values into new_id. Both file types would be of the format (analogous > > to pci_show_resources): > > echo "0x0000 0x0000 0x0000 0x0000 0x0000 0x0000" > new_id > > with fields being vendor, device, subvendor, subdevice, class, > > class_mask. > > I dont' think what you actually want is changing the id table - after all, > it's only walked when registering the driver (+ hotplug). > > What you really want is a way to call the drivers' probe routine for a > device which isn't in its tables. > > So why not simply > > echo "0x0000 0x0000 0x0000 0x0000 0x0000 0x0000" > .../3c59x/probe
I think there is value in decoupling the two operations:
echo "0x0000 0x0000 0x0000 0x0000 0x0000 0x0000" > .../3c59x/table echo 1 > .../3c59x/probe_it
Because you want the id table additions to be persistant in the face of cardbus unplug/replug, and for the case where cardbus card may not be present yet, but {will,may} be soon.
Jeff
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |