From: "Eric S. Raymond" <esr@thyrsus.com>
To: Greg KH <greg@kroah.com>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
cate@debian.org
Subject: Re: Hardware Inventory [was: Re: ISA slot detection on PCI systems?]
Date: Mon, 7 Jan 2002 13:58:42 -0500 [thread overview]
Message-ID: <20020107135842.A20420@thyrsus.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>
In-Reply-To: <20020107185813.GL7378@kroah.com>; from greg@kroah.com on Mon, Jan 07, 2002 at 10:58:13AM -0800
Greg KH <greg@kroah.com>:
> On Mon, Jan 07, 2002 at 10:50:01AM -0800, Greg KH wrote:
> >
> > And the /sbin/hotplug program knows about _all_ devices that the
> > currently compiled kernel can handle due to the MODULE_DEVICE_TABLE tags
> > in the drivers.
>
> Along these lines, I am very disappointed in looking at the
> autoconfigure stuff in CML2. It should be taking all of the device and
> driver matching information from the kernel itself, as it is already
> specified there.
I'm taking my rules file from Giacomo Catenazzi, who developed it
originally for a shellscript he wrote. I don't know how he generates
the hardware probes; for all I know, he's got code groveling through
the module device tables.
I've been meaning to ask you about this, Giacomo. Where *did* all
those probes come from?
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
Don't think of it as `gun control', think of it as `victim
disarmament'. If we make enough laws, we can all be criminals.
next prev parent reply other threads:[~2002-01-07 19:13 UTC|newest]
Thread overview: 35+ 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 [this message]
2002-01-08 8:04 ` [kbuild-devel] " Giacomo Catenazzi
2002-01-08 18:36 ` Greg KH
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
-- strict thread matches above, loose matches on Subject: below --
2002-01-07 20:13 David Brownell
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=20020107135842.A20420@thyrsus.com \
--to=esr@thyrsus.com \
--cc=cate@debian.org \
--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