Messages in this thread | | | From | Rusty Russell <> | Subject | Re: Displaying/modifying PCI device id tables via sysfs | Date | Sun, 25 May 2003 14:57:31 +1000 |
| |
In message <20030524003712.GA15086@kroah.com> you write: > On Fri, May 23, 2003 at 10:53:51AM +1000, Rusty Russell wrote: > > So the question is, how do you add PCI IDs to a module which isn't loaded? > > Do we really care about this question? I mean, if a user knows that > they want to use a specific module for their device (as they must know > this somehow), then they can just load the module today, and use the > dynamic id feature to add the new id. At that time the device is bound > to the driver.
Jeff's once complained about a distro having to update modules simply to update the PCI tables, which he indicated happened frequently.
But adding new aliases is trivial, so this covers it.
> > You can trivially add a new alias for it, which will cause modprobe to > > find it, but the module won't know it can handle the new PCI ID, and > > will fail to load. > > Not true. The module will load just fine, just not bind to the device.
Yes, Matt pointed this out, which makes it work fine.
Thanks, Rusty. -- Anyone who quotes me in their sig is an idiot. -- Rusty Russell. - 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/
| |