All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: jeff millar <jeff@wa1hco.mv.com>
Cc: Carlos E Gorges <carlos@techlinux.com.br>, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Hardware detection tool 0.2
Date: Fri, 31 Aug 2001 16:23:04 -0700	[thread overview]
Message-ID: <20010831162303.A23689@kroah.com> (raw)
In-Reply-To: <01083019402502.01265@skydive.techlinux> <20010830161809.A19258@kroah.com> <002801c13270$86592680$0201a8c0@home>
In-Reply-To: <002801c13270$86592680$0201a8c0@home>; from jeff@wa1hco.mv.com on Fri, Aug 31, 2001 at 06:58:59PM -0400

On Fri, Aug 31, 2001 at 06:58:59PM -0400, jeff millar wrote:
> 
> One reason: Not all hardware has the signals needed to detect when a card
> gets plugged or unplugged.  Consider legacy cPCI systems.  The don't have
> the Hot Swap extensions or backplane hot swap control.  The only way to find
> the cards is to periodically scan the bus for new cards, cards that
> disappeared, or requests for Hot Swap.

But the driver for those devices have a struct pci_driver object that
they use to register themselves with the PCI subsystem, right?  The
MODULE_DEVICE_TABLE uses the id_table structure in the struct pci_driver
object.  That's all, it isn't necessarily a hotplug specific thing.

And having that MODULE_DEVICE_TABLE for those drivers will allow the
kernel to load those modules when the bus is scanned for new cards, like
on boot :)

thanks,

greg k-h

  parent reply	other threads:[~2001-08-31 23:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-30 22:40 [ANNOUNCE] Hardware detection tool 0.2 Carlos E Gorges
2001-08-30 23:18 ` Greg KH
2001-08-31 22:58   ` jeff millar
2001-08-31 23:11     ` SMP, APIC and networking issues java programmer
2001-08-31 23:38       ` Alan Cox
2001-09-01 20:59         ` Jorge Nerin
2001-08-31 23:23     ` Greg KH [this message]
2001-08-31 23:46       ` [ANNOUNCE] Hardware detection tool 0.2 jeff millar
2001-09-01  0:08         ` Greg KH
2001-09-01 10:54 ` Tim Jansen

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=20010831162303.A23689@kroah.com \
    --to=greg@kroah.com \
    --cc=carlos@techlinux.com.br \
    --cc=jeff@wa1hco.mv.com \
    --cc=linux-kernel@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.