All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Matt_Domsch@Dell.com
Cc: mochel@osdl.org, alan@redhat.com, linux-kernel@vger.kernel.org,
	jgarzik@redhat.com
Subject: Re: [RFC][PATCH] Dynamic PCI Device IDs
Date: Mon, 5 May 2003 20:56:35 -0700	[thread overview]
Message-ID: <20030506035635.GA5403@kroah.com> (raw)
In-Reply-To: <1052186678.19726.9.camel@iguana.localdomain>

On Mon, May 05, 2003 at 09:04:35PM -0500, Matt_Domsch@Dell.com wrote:
> > Unfortunatly, looking at the driver core real quickly, I don't see a
> > simple way to kick the probe cycle off again for all pci devices, but
> > I'm probably just missing something somewhere...
> 
> I think drivers/base/bus.c: driver_attach() is what we want, which will
> walk the list of the bus's devices and run bus_match() which is
> pci_bus_match() which will scan for us.  Just need to un-static
> driver_attach() I expect.  Pat, does this sound right?

You can't just call driver_attach(), as the bus semaphore needs to be
locked before doing so.  In short, you almost need to duplicate
bus_add_driver(), but not quite :)

Good luck,

greg k-h

  reply	other threads:[~2003-05-06  3:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06  2:04 [RFC][PATCH] Dynamic PCI Device IDs Matt_Domsch
2003-05-06  3:56 ` Greg KH [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2003-05-01  0:39 Matt_Domsch
2003-05-02 23:15 ` Greg KH
2003-05-05  5:37   ` Jeff Garzik
2003-05-06  0:17     ` Greg KH
2003-05-05 22:51   ` Matt Domsch
2003-05-06  0:15     ` Greg KH
2003-04-30 21:45 Matt Domsch
2003-04-30 21:53 ` Jeff Garzik
2003-04-30 22:24 ` Greg KH

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=20030506035635.GA5403@kroah.com \
    --to=greg@kroah.com \
    --cc=Matt_Domsch@Dell.com \
    --cc=alan@redhat.com \
    --cc=jgarzik@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.