From: "Eric S. Raymond" <esr@thyrsus.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: ISA hardware discovery -- the elegant solution
Date: Mon, 14 Jan 2002 03:48:31 -0500 [thread overview]
Message-ID: <20020114034831.A5780@thyrsus.com> (raw)
In-Reply-To: <20020113205839.A4434@thyrsus.com> <m1k7ulpbf7.fsf@frodo.biederman.org>
In-Reply-To: <m1k7ulpbf7.fsf@frodo.biederman.org>; from ebiederm@xmission.com on Mon, Jan 14, 2002 at 01:46:36AM -0700
Eric W. Biederman <ebiederm@xmission.com>:
> 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 the kernel itself has to know how to probe and initialize these devices
at boot time, correct? That information is implicitly exported via
/var/log/dmesg -- I'm simply suggesting that it be a little more explicit.
> > 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.
Some of the on-board devices on my Tyan Thunder are ISA.
> > 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.
Would that be feasible without root privileges in order to read kmem?
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
[The disarming of citizens] has a double effect, it palsies the hand
and brutalizes the mind: a habitual disuse of physical forces totally
destroys the moral [force]; and men lose at once the power of
protecting themselves, and of discerning the cause of their
oppression.
-- Joel Barlow, "Advice to the Privileged Orders", 1792-93
next prev parent reply other threads:[~2002-01-14 9:03 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
2002-01-14 8:48 ` Eric S. Raymond [this message]
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=20020114034831.A5780@thyrsus.com \
--to=esr@thyrsus.com \
--cc=ebiederm@xmission.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