public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Giacomo Catenazzi <cate@dplanet.ch>
To: Greg KH <greg@kroah.com>
Cc: esr@thyrsus.com, kbuild-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [kbuild-devel] Re: Hardware Inventory [was: Re: ISA slot detection on PCI systems?]
Date: Wed, 09 Jan 2002 09:25:17 +0100	[thread overview]
Message-ID: <3C3BFE6D.1000602@dplanet.ch> (raw)
In-Reply-To: <Pine.LNX.4.33.0201070955480.867-100000@segfault.osdlab.org> <Pine.LNX.4.33.0201071908580.16327-100000@Appserv.suse.de> <20020107185001.GK7378@kroah.com> <20020107185813.GL7378@kroah.com> <3C3AA7FE.2060304@dplanet.ch> <20020108183635.GG14410@k

Greg KH wrote:
> 
> What about devices that are supported by more than one driver?  How do
> you handle that?  (see the USB keyspan_pda and keyspan drivers for an
> example.)

I check the devices supported by multiple drivers, and normally
I comment both probes (This is why I have so much probes commented.
These drivers are marked in my db '## 2x').
Sometime I arbitrary choice a device.
I.e. in FS 'autofs4' is prefered to 'autofs'.
In the case of USB, two driver 'register' the uhci cards.
I prefer USB_UHCI_ALT to USB_UHCI (arbitrary choice).

I would like comments and correction to these choices.
(The kernel is to big to know all, and the sources are not
usefull in some cases)


BTW the database is available to all. If somebody need it
I can confirm that the database is complete (for MODULES_TABLE
items).
The database have these informations:
- type (pci, usb, pnp,...)
- device ID (ev. with class) or class ID, or interface ID or function ID, or both
- configuration variable
- source (the kernel file where the device is defined)
(for non autoprobe use, you should discard the ev. first '#', CONFIG = "_" means 'always',
in pci the "!" before the source means from MODULES_TABLE, the other pci are detected by other
methods (no so accurate)



	giacomo


  parent reply	other threads:[~2002-01-09  8:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-04 11:32 Hardware Inventory [was: Re: ISA slot detection on PCI systems?] Martin Knoblauch
2002-01-04 22:17 ` Dave Jones
2002-01-05 17:00   ` Paul Jakma
2002-01-05 17:14     ` Dave Jones
2002-01-07 18:05       ` Patrick Mochel
2002-01-07 18:11         ` Dave Jones
2002-01-07 18:50           ` Greg KH
2002-01-07 18:58             ` Greg KH
2002-01-07 18:58               ` Eric S. Raymond
2002-01-08  8:04               ` [kbuild-devel] " Giacomo Catenazzi
2002-01-08 18:36                 ` Greg KH
2002-01-09  8:25                 ` Giacomo Catenazzi [this message]
2002-01-07 18:58             ` Dave Jones
2002-01-07 19:06               ` Greg KH
2002-01-07 19:19                 ` Dave Jones
2002-01-07 19:45                   ` Alexander Viro
2002-01-08 14:00                   ` Alan Cox
2002-01-08 14:00                     ` Erik Andersen
2002-01-07 19:19             ` Patrick Mochel
2002-01-07 19:29               ` Greg KH
2002-01-07 20:36                 ` David Brownell
2002-01-07 22:03                   ` Greg KH
2002-01-07 22:28                     ` David Brownell
2002-01-07 23:59                       ` Greg KH
2002-01-08  8:36                       ` Kevin Easton
2002-01-11 21:52                         ` David Brownell
2002-01-07 23:25       ` Kai Germaschewski
2002-01-07 17:55     ` Patrick Mochel
2002-01-07 19:04       ` Richard Gooch
2002-01-07 19:26         ` Dave Jones
2002-01-07 19:41           ` Alexander Viro
2002-01-07 19:58           ` Paul Jakma
2002-01-07 19:33         ` Patrick Mochel
2002-01-07 20:16           ` Andrew Morton

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=3C3BFE6D.1000602@dplanet.ch \
    --to=cate@dplanet.ch \
    --cc=esr@thyrsus.com \
    --cc=greg@kroah.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --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