linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: pci configuration registers
Date: Tue, 14 Mar 2006 19:25:04 +0000	[thread overview]
Message-ID: <20060314192504.GA27012@kroah.com> (raw)
In-Reply-To: <1142348627.9472.31.camel@ikkyo.elis.UGent.be>

On Tue, Mar 14, 2006 at 04:03:47PM +0100, Philippe Faes wrote:
> Hi Gang,
> 
> I've read how I can use fakephp to (virtually) remove an detect devices
> on my PCI bus.
> My problem now is: my (new) device doesn't have its PCI configuration
> registers set. Normally this is done during boot, but since I hot-plug
> it, they are not set. 
> I think pci_setup_device does something similar, but this function is
> not made visible to the modules. 
> 
> What is the proper way to automatically configure the PCI registers?

Use the pci hotplug controller interface :)

good luck,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2006-03-14 19:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-14 15:03 pci configuration registers Philippe Faes
2006-03-14 19:25 ` Greg KH [this message]
2006-03-15  7:49 ` Philippe Faes
2006-03-15 15:57 ` 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=20060314192504.GA27012@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).