From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: fake hotplug questions
Date: Fri, 28 May 2004 23:18:15 +0000 [thread overview]
Message-ID: <20040528231815.GD14023@kroah.com> (raw)
In-Reply-To: <OF0C2223BC.2FC60A96-ON85256E89.0049F5EC@mck.us.ray.com>
On Mon, May 03, 2004 at 09:51:52AM -0400, David Clemmer wrote:
>
>
>
>
> Hi all,
>
> I was looking at the fakephp code, and noted that it just refuses to touch
> a bridge.
Yes, it only handles PCI devices.
> I was wondering if this is because of not wanting to handle
> recursively disabling devices behind the bridge, or not having code
> available to re-enable them afterwards, or something else I didn't think
> of. (I'm asking because I'd like to fake replugging a bridge.)
It's just because I didn't think of doing that function in the driver.
If you have patches to fix this, I'll gladly take a look at them.
> I also have a couple of specific questions. Is there a better way to find
> which hotplug_slot is associated with a (pci_dev*) device than walking the
> dummy slot list, and looking for one with a matching dev field?
Not really, sorry.
> Also, when re-enabling a device, I'm assuming that storing the
> hotplug_slot object (and a copy of the pci_dev object) would be
> needed, probably along with something indicative of which bus
> something was attached to (and, presumably, a copy of the pci_bus
> object, for bridges).
How about just rescanning all of the pci busses to see if any devices
are there that aren't in our list anymore? That would allow machines
that can add PCI devices without pci hotplug controller to work better.
Sorry for the delay in answering this.
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_idÅ66&op=click
_______________________________________________
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
prev parent reply other threads:[~2004-05-28 23:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 13:51 fake hotplug questions David Clemmer
2004-05-28 23:18 ` 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=20040528231815.GD14023@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).