From: Daniel Phillips <phillips@arcor.de>
To: Matt Domsch <Matt_Domsch@Dell.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling
Date: Wed, 4 Sep 2002 01:29:37 +0200 [thread overview]
Message-ID: <E17mN73-0005mq-00@starship> (raw)
In-Reply-To: <Pine.LNX.4.44.0209031616580.30474-100000@humbolt.us.dell.com>
On Wednesday 04 September 2002 00:05, Matt Domsch wrote:
>
> [...]
>
> EDD works by providing the bus (PCI, PCI-X, ISA, InfiniBand, PCI
> Express, or HyperTransport) location (e.g. PCI 02:01.0) and interface
> (ATAPI, ATA, SCSI, USB, 1394, FibreChannel, I2O, RAID, SATA) location
> (e.g. SCSI ID 5 LUN 0) information for each BIOS int13 device. The
> patch below creates CONFIG_EDD, that when defined, makes the calls to
> retrieve and store this information. It then exports it (yes, another
> /proc, glad to change it to driverfs or whatever else when that makes
> sense) in /proc/edd/{bios-device-number}, as such:
>
> [...]
>
>
> Feedback appreciated.
How about providing an example of how you'd export the root via driverfs,
with a view to educating those of us who are still don't have much of a
clue how driverfs fits in with big picture?
--
Daniel
next prev parent reply other threads:[~2002-09-03 23:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 22:05 [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling Matt Domsch
2002-09-03 23:29 ` Daniel Phillips [this message]
2002-09-04 4:35 ` Andre Hedrick
2002-09-04 16:02 ` Matt Domsch
2002-09-04 0:54 Matt_Domsch
2002-09-04 1:09 ` Daniel Phillips
2002-09-04 4:17 ` Greg KH
2002-09-08 0:39 ` Patrick Mochel
2002-09-09 1:17 Matt_Domsch
2002-09-10 22:43 Matt_Domsch
2002-09-11 19:09 Matt_Domsch
2002-09-12 18:00 ` Patrick Mochel
2002-09-12 18:48 ` Matt Domsch
[not found] <20BF5713E14D5B48AA289F72BD372D6821CE34@AUSXMPC122.aus.amer.dell.com>
2002-09-27 21:30 ` Matt Domsch
2002-09-27 22:33 ` Greg KH
2002-09-29 16:11 ` Dave Jones
2002-09-29 16:18 ` Zwane Mwaikambo
2002-09-29 16:44 ` Alan Cox
2002-09-29 18:20 ` Kai Germaschewski
2002-09-29 18:27 ` Russell King
2002-09-29 18:52 ` Dave Jones
2002-10-01 1:55 ` Patrick Mochel
2002-09-30 4:32 Matt_Domsch
2002-10-01 3:37 Matt_Domsch
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=E17mN73-0005mq-00@starship \
--to=phillips@arcor.de \
--cc=Matt_Domsch@Dell.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;
as well as URLs for NNTP newsgroup(s).