From: Greg KH <email@example.com>
To: Jeff Garzik <firstname.lastname@example.org>
Cc: Matt_Domsch@Dell.com, email@example.com,
Subject: Re: [RFC][PATCH] Dynamic PCI Device IDs
Date: Mon, 5 May 2003 17:17:09 -0700 [thread overview]
Message-ID: <20030506001709.GB3945@kroah.com> (raw)
On Mon, May 05, 2003 at 01:37:52AM -0400, Jeff Garzik wrote:
> Greg KH wrote:
> >But by adding the device ids, they will be persistant, for that driver,
> >right? Then when the device is plugged in, the core will iterate over
> >the static and dynamic ids, right? If so, I don't see how a "probe_it"
> >file is needed.
> Consider the case:
> Device already exists, and is plugged in. Like a standard PCI card.
> Driver doesn't support PCI id, and the sysadmin uses /bin/echo to add one.
Great, probe gets run right then, and that's what we want, right?
> For unplugged case, you know you don't need to re-run the probe.
But a probe scan across all devices doesn't really take much time,
right? And yes this would be "redundant" but it's a whole lot tougher
to figure out that we don't need to re-run a probe, than to just always
do it :)
next prev parent reply other threads:[~2003-05-06 0:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 0:39 [RFC][PATCH] Dynamic PCI Device IDs Matt_Domsch
2003-05-02 23:15 ` Greg KH
2003-05-05 5:37 ` Jeff Garzik
2003-05-06 0:17 ` Greg KH [this message]
2003-05-05 22:51 ` Matt Domsch
2003-05-06 0:15 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-05-06 2:04 Matt_Domsch
2003-05-06 3:56 ` Greg KH
2003-05-06 16:35 ` Matt Domsch
2003-05-10 0:11 ` Greg KH
2003-05-13 21:28 ` Patrick Mochel
2003-05-13 21:33 ` Patrick Mochel
2003-04-30 21:45 Matt Domsch
2003-04-30 21:53 ` Jeff Garzik
2003-04-30 22:24 ` Greg KH
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).