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 Hot Plug Operation
Date: Fri, 03 May 2002 16:53:54 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-102044870827409@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102044288121120@msgid-missing>

On Fri, May 03, 2002 at 10:48:23AM -0700, Stephen Williams wrote:
> 
> greg@kroah.com said:
> > I've posted a small module that manually rescans the pci bus and
> > allows events to be generated if it sees a new device, but this is a
> > bit of a hack :)  Check the archives if you're interested. 
> 
> This is interesting. Does this mean that if I install a new PCI
> device (I have an isolating extender with a power switch) I can
> add a new device to a running system? It will get mapped?

Yes.  See this driver:
	http://marc.theaimsgroup.com/?l=linux-hotplug-devel&m\x101312609603679
and the other messages in that thread for more information.

thanks,

greg k-h

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
_______________________________________________
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

  parent reply	other threads:[~2002-05-03 16:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03 15:16 PCI Hot Plug Operation Greg KH
2002-05-03 15:40 ` Greg KH
2002-05-03 16:00 ` Bill Bruce
2002-05-03 16:53 ` Greg KH [this message]
2002-05-03 17:48 ` Stephen Williams
2002-05-04  8:33 ` Paul Hedderly
2002-05-04  8:57 ` David Woodhouse
2002-05-06 16:32 ` Greg KH
2002-05-06 17:16 ` David Brownell

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=marc-linux-hotplug-102044870827409@msgid-missing \
    --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).