public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Daniel Stodden <stodden@in.tum.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: pci: dev->driver "runtime" acquisition?
Date: Mon, 3 Dec 2001 19:22:36 -0800	[thread overview]
Message-ID: <20011203192236.D18576@kroah.com> (raw)
In-Reply-To: <1007400598.6982.2.camel@atbode65>
In-Reply-To: <1007400598.6982.2.camel@atbode65>

On Mon, Dec 03, 2001 at 06:29:57PM +0100, Daniel Stodden wrote:
> hi.
> 
> supposing i've got a "hotplug" style pci_driver,

Any hints on what kind of driver this is? :)

> but who's going to gain access to a device _not_ at initialization time,
> i.e. not within pci_register_driver(), but rather somehere in a bottom
> half. no pci_device_id* at pci_register_driver( ), since i don't
> know the signature yet.

Take a look at the pci_read_config_*_nodev() and
pci_write_config_*_nodev() functions in the
drivers/hotplug/pci_hotplug.h file.  Do these functions help you out?

thanks,

greg k-h

      reply	other threads:[~2001-12-04  3:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 17:29 pci: dev->driver "runtime" acquisition? Daniel Stodden
2001-12-04  3:22 ` Greg KH [this message]

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=20011203192236.D18576@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stodden@in.tum.de \
    /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