public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Carlos E Gorges <carlos@techlinux.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Hardware detection tool 0.2
Date: Thu, 30 Aug 2001 16:18:09 -0700	[thread overview]
Message-ID: <20010830161809.A19258@kroah.com> (raw)
In-Reply-To: <01083019402502.01265@skydive.techlinux>
In-Reply-To: <01083019402502.01265@skydive.techlinux>; from carlos@techlinux.com.br on Thu, Aug 30, 2001 at 07:40:25PM -0300

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.

All you are caring about is what device is supported by what module,
right?  That can be easily determined by the info in the modules.usbmap
and modules.pcimap files in the /lib/modules/<kernel_version>/
directory.

Keeping tables like these will be a tough thing to do, that's why the
linux-hotplug project relies on the drivers themselves to do the work.

thanks,

greg k-h

  reply	other threads:[~2001-08-30 23:20 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 [this message]
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     ` [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=20010830161809.A19258@kroah.com \
    --to=greg@kroah.com \
    --cc=carlos@techlinux.com.br \
    --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