mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Greg KH <greg@kroah.com>
Cc: Matt_Domsch@Dell.com, linux-kernel@vger.kernel.org, mochel@osdl.org
Subject: Re: Displaying/modifying PCI device id tables via sysfs
Date: Sun, 25 May 2003 14:57:31 +1000	[thread overview]
Message-ID: <20030526001728.6F50A2C0C9@lists.samba.org> (raw)
In-Reply-To: Your message of "Fri, 23 May 2003 17:37:12 MST." <20030524003712.GA15086@kroah.com>

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.

  reply	other threads:[~2003-05-26  0:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03 17:57 Matt Domsch
2003-03-03 18:25 ` Greg KH
2003-03-03 20:02   ` Alan Cox
2003-03-03 20:56   ` Matt Domsch
2003-03-04  0:31     ` Greg KH
2003-03-04  4:56       ` Matt Domsch
2003-03-04 14:10         ` Patrick Mochel
2003-03-04 20:22         ` Kai Germaschewski
2003-03-04 22:39           ` Alan Cox
2003-03-04 22:57           ` Jeff Garzik
2003-03-04  0:34     ` Jeff Garzik
2003-05-23  0:53   ` Rusty Russell
2003-05-24  0:37     ` Greg KH
2003-05-25  4:57       ` Rusty Russell [this message]
2003-05-23  2:27 Matt_Domsch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030526001728.6F50A2C0C9@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=Matt_Domsch@Dell.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®