All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bill Bruce" <bill_bruce@terago.com>
To: linux-hotplug@vger.kernel.org
Subject: PCI Hot Plug Operation
Date: Fri, 03 May 2002 16:00:10 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-102044169519609@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102044288121120@msgid-missing>

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.

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?

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

Thanks

Bill Bruce
Terago Communications



_______________________________________________________________

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:00 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 [this message]
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-102044169519609@msgid-missing \
    --to=bill_bruce@terago.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.