public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: esr@thyrsus.com
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: ISA hardware discovery -- the elegant solution
Date: 14 Jan 2002 01:46:36 -0700	[thread overview]
Message-ID: <m1k7ulpbf7.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20020113205839.A4434@thyrsus.com>
In-Reply-To: <20020113205839.A4434@thyrsus.com>

"Eric S. Raymond" <esr@thyrsus.com> writes:

> I've been thinking about the hardware-discovery problem for ISA devices,
> and there may be an elegant solution.  It will take a number of small changes
> to the kernel sources, however.

An elegant solution is writing a program like kudzu and placing the
information it generates in a globally accessible place.  The problem
is that linux does really have a complete standard hardware database,
and until such a thing is built there are no short cuts, no easy methods
to get it.  And there probably never will be guaranteed unprivledged
user space access to the information.  The system administrator may
simply not want to let that information go.

The only thing that comes close to what you currently want is
devfs.

dmesg is for people.

As for ISA there is a reason even the enhance version that allows
software discovery is called Plug-and-Pray.


> My autoconfigurator's probe table now has a small number of tests than 
> do regexp matches against the dmesg log.  As is, this solution does not
> scale well, because each regexp has to be discovered by eyeball and then
> maintained in the table by hand.

ISA is not a software enumerable bus especially not for unprivledged
users.  And no amount of complaining will change that.  That is why we
have PNP ISA and PCI.

> But suppose the format of boot-time driver messages were standardized in a
> format that included their config symbol in a discoverable form?

If there was an ISA device in your example it might be interesting.

> With this change, generating a report on ISA hardware and other
> facilities configured in at boot time would be trivial.  This would
> make the autoconfigurator much more capable.  Best of all, the only
> change required to accomplish this would be safe edits of print format
> strings.

It sounds like what you want is an lsmod that lists compiled in
modules.

> I would be willing to generate a patch to implement this change.

Please don't until you understand the problem...

Eric

  parent reply	other threads:[~2002-01-14  8:49 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14  1:58 ISA hardware discovery -- the elegant solution Eric S. Raymond
2002-01-14  2:54 ` Larry McVoy
2002-01-14  8:46 ` Eric W. Biederman [this message]
2002-01-14  8:48   ` Eric S. Raymond
2002-01-14  9:17     ` H. Peter Anvin
2002-01-14 17:34     ` Eric W. Biederman
  -- strict thread matches above, loose matches on Subject: below --
2002-01-14  8:03 Zwane Mwaikambo
2002-01-14  9:44 ` Alan Cox
2002-01-14 14:00   ` Zwane Mwaikambo
     [not found] <fa.dardpev.1m1emjp@ifi.uio.no>
2002-01-14 10:14 ` Giacomo Catenazzi
2002-01-14 16:16   ` Eric S. Raymond
2002-01-14 16:38     ` Giacomo Catenazzi
2002-01-14 16:34       ` Eric S. Raymond
2002-01-14 17:48     ` Alan Cox
2002-01-14 17:55       ` Mr. James W. Laferriere
2002-01-14 18:08         ` Alan Cox
2002-01-14 17:59       ` Eric S. Raymond
2002-01-14 18:35         ` Alan Cox
2002-01-14 11:17 Michael Lazarou (ETL)
2002-01-14 16:11 ` Eric S. Raymond
2002-01-14 16:59   ` Eli Carter
2002-01-14 17:11     ` Wichert Akkerman
2002-01-14 18:33   ` Oliver Xymoron
2002-01-14 23:02     ` Tom Gilbert
2002-01-14 18:58   ` Andrew Pimlott
     [not found] <fa.r42lgsv.1b5e3p9@ifi.uio.no>
2002-01-14 12:30 ` Giacomo Catenazzi
2002-01-14 14:25 Michael Lazarou (ETL)
2002-01-14 14:47 ` Giacomo Catenazzi
2002-01-14 18:36 Stephen Shirley

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=m1k7ulpbf7.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=esr@thyrsus.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