All of lore.kernel.org
 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 15:16:25 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-102044288121120@msgid-missing> (raw)

On Fri, May 03, 2002 at 11:00:10AM -0500, Bill Bruce wrote:
> My situation:
> 
> The software base is Redhat 7.2. The kernel has been updated to 2.4.9. The
> user-space hot plug files/scripts dated 2002_4_1 from SourceForge have been
> installed.
> 
> I install a PCI card in my system and power it up. It appears on the PCI bus
> (lspci -H1 confirms this).
> 
> There is no driver for this card in the kernel, but according to my reading
> of the hot plug documentation I expect the /sbin/hotplug script to be
> invoked, giving me an opportunity to load a driver. This is not happening.

/sbin/hotplug is not envoked at the first scanning of the PCI bus.  This
might be considered a bug, but as there is no userspace set up at this
point in time, any call out to /sbin/hotplug would not work anyway :)

This will be fixed in 2.5, when we have initramfs working.

> Some rudimentary questions:
> 
> I am assuming the kernel is periodically scanning the PCI bus, looking for
> new devices. Is this correct? If so how often does this happen?

No, this is not happening.

> Do I need to install a driver for my card to make the kernel aware of a
> possible hot pluggable device?

PCI Hotplug only works if you have a PCI Hotplug controller on your
motherboard.  This is usually only on high end servers or cPCI machines.
Do you have such a machine?

If not, you need to manually load the kernel module for your pci device,
sorry, as there are no "hotplug" pci events able to be generated.

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.

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

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03 15:16 Greg KH [this message]
2002-05-03 15:40 ` PCI Hot Plug Operation Greg KH
2002-05-03 16:00 ` Bill Bruce
2002-05-03 16:53 ` Greg KH
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-102044288121120@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 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.