From: Dave Jones <davej@suse.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: "Eric S. Raymond" <esr@thyrsus.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Calling EISA experts
Date: Thu, 17 Jan 2002 12:48:49 +0100 [thread overview]
Message-ID: <20020117124849.F22171@suse.de> (raw)
In-Reply-To: <20020117015456.A628@thyrsus.com> <20020117121723.B22171@suse.de> <3C46B718.26F52BD5@mandrakesoft.com>
In-Reply-To: <3C46B718.26F52BD5@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Thu, Jan 17, 2002 at 06:35:52AM -0500
On Thu, Jan 17, 2002 at 06:35:52AM -0500, Jeff Garzik wrote:
> > > Does anything in /proc or elswhere reliably register the presence of EISA?
> > Not afaik. I'm tempted to hack support for it into driverfs.
> The EISA_bus global variable indicates presence...
*nod*, though you can almost guarantee this isn't what Eric wants.
I'm assuming he wants something a'la /proc/pci
Hacking the EISA code to register a driver in driverfs should be
fairly trivial. I'll wait and see what Pat does with the
busdriver reworking that he's up to right now before doing anything
on this though.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-01-17 11:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 6:54 Calling EISA experts Eric S. Raymond
2002-01-17 8:54 ` Marc ZYNGIER
2002-01-17 10:19 ` Alan Olsen
2002-01-17 9:46 ` Chris Wedgwood
2002-01-17 11:17 ` Dave Jones
2002-01-17 11:35 ` Jeff Garzik
2002-01-17 11:48 ` Dave Jones [this message]
2002-01-17 13:50 ` Eric S. Raymond
2002-01-21 11:49 ` Paul Gortmaker
2002-01-21 13:08 ` Jeff Garzik
2002-01-22 5:52 ` Eric S. Raymond
2002-01-22 6:39 ` William Stearns
2002-01-22 18:57 ` Eric S. Raymond
2002-01-22 19:59 ` Dave Jones
2002-01-17 17:30 ` Dennis Boylan
2002-01-18 7:02 ` Jeremy Jackson
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=20020117124849.F22171@suse.de \
--to=davej@suse.de \
--cc=esr@thyrsus.com \
--cc=jgarzik@mandrakesoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.