From: "jeff millar" <jeff@wa1hco.mv.com>
To: "Greg KH" <greg@kroah.com>, "Carlos E Gorges" <carlos@techlinux.com.br>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Hardware detection tool 0.2
Date: Fri, 31 Aug 2001 18:58:59 -0400 [thread overview]
Message-ID: <002801c13270$86592680$0201a8c0@home> (raw)
In-Reply-To: <01083019402502.01265@skydive.techlinux> <20010830161809.A19258@kroah.com>
----- Original Message -----
From: "Greg KH" <greg@kroah.com>
To: "Carlos E Gorges" <carlos@techlinux.com.br>
Cc: <linux-kernel@vger.kernel.org>
Sent: Thursday, August 30, 2001 7:18 PM
Subject: Re: [ANNOUNCE] Hardware detection tool 0.2
> On Thu, Aug 30, 2001 at 07:40:25PM -0300, Carlos E Gorges wrote:
> > Hardware detection tool 0.2
> >
> > The main idea is keep a unified database of modules and
> > create a good tool for hardware configurators.
>
> Why don't you just pull the PCI and USB module information out of the
> drivers themselves? All the information you need it in the
> MODULE_DEVICE_TABLE() macro. You don't get a pretty vendor string for
> most all of the USB devices that use a USB class spec, but that isn't
> necessary.
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.
next prev parent reply other threads:[~2001-08-31 23:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-30 22:40 Carlos E Gorges
2001-08-30 23:18 ` Greg KH
2001-08-31 22:58 ` jeff millar [this message]
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 ` [ANNOUNCE] Hardware detection tool 0.2 Greg KH
2001-08-31 23:46 ` 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='002801c13270$86592680$0201a8c0@home' \
--to=jeff@wa1hco.mv.com \
--cc=carlos@techlinux.com.br \
--cc=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®