From: Greg KH <greg@kroah.com>
To: Giacomo Catenazzi <cate@dplanet.ch>
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: Tue, 8 Jan 2002 10:36:35 -0800 [thread overview]
Message-ID: <20020108183635.GG14410@kroah.com> (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>
In-Reply-To: <3C3AA7FE.2060304@dplanet.ch>
On Tue, Jan 08, 2002 at 09:04:14AM +0100, Giacomo Catenazzi wrote:
> modules.*map exist only on compiled kernel. And entry depends on
> architecture and on configuration.
I agree. That's why something like what David has proposed would be
more helpful here.
> But don't worry. I use the kernel source to find the
> MODULES_DEVICE_TABLE (with a partially automated script) to build the
> new tables.
Do you check for devices that are now handled by different drivers? For
example, the CDCEther and acm USB drivers have gone though a series of
different configuration changes, where one driver would claim devices
meant for the other. It is hopefully all fixes up now, but might have
confused your scripts.
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.)
thanks,
greg k-h
next prev parent reply other threads:[~2002-01-08 18:38 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 [this message]
2002-01-09 8:25 ` Giacomo Catenazzi
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=20020108183635.GG14410@kroah.com \
--to=greg@kroah.com \
--cc=cate@dplanet.ch \
--cc=esr@thyrsus.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