From: Matt_Domsch@Dell.com
To: mochel@osdl.org, greg@kroah.com
Cc: phillips@arcor.de, linux-kernel@vger.kernel.org
Subject: RE: [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling
Date: Tue, 10 Sep 2002 17:43:22 -0500 [thread overview]
Message-ID: <20BF5713E14D5B48AA289F72BD372D68C1E7ED@AUSXMPC122.aus.amer.dell.com> (raw)
I've updated the EDD code to use driverfs instead of /proc. It's now
exported as:
.
|-- edd
| |-- 80
| | `-- info
| |-- 81
| | `-- info
| |-- 82
| | `-- info
| |-- 83
| | `-- info
| |-- 84
| | `-- info
| `-- 85
| `-- info
where 80..85 are the BIOS device numbers, and info is a file that displays
the same information I was displaying before. Thanks Patrick for the
pointers, and once the top-level firmware/bios/whatever directory is made,
it can move there easily.
Patch available from http://domsch.com/linux/edd30/edd-driverfs-1.patch and
http://domsch.com/linux/edd30/edd-driverfs-1.patch.sign applies against
2.5.34 or BK-current, and is the whole of the feature, not incremental.
Also in BK at http://mdomsch.bkbits.net/linux-2.5-edd.
The next logical extension would be to make a symlink 'disk' in each
directory that points at the PCI bus:dev.fn/scsiX/a:b:c:d:disk file for the
appropriate disk. However, I'm in a quandry... There's no simple way to do
this.
For EDD to do the mapping itself, it needs to walk various lists of devices
(Scsi_Disks, IDE disks, ...) Those lists aren't currently exported.
EDD could do it itself brute-force, except that it knows all the information
*except* the scsiX host logical number, so it would still have to some sort
of lookup. That nice physical (and virtually identical logical) path got a
kernel-logical component added which requires a lookup. :-( The third
problem is that mapping needs to happen at device discovery time, not at EDD
load time, else scsi-add-single-device and/or modular IDE insertions later
won't pick it up.
So, I start thinking about making calls from the various disk type drivers
back to the EDD code to get the symlinks made. That touches more than I
wanted to this round, but is probably the best way to go, and what I'll
investigate. Per-arch dummy asm/edd.h dummy files with noop functions for
the calls into EDD that are only x86-applicable... yuck.
Thoughts?
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer, Architect
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next reply other threads:[~2002-09-10 22:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 22:43 Matt_Domsch [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-01 3:37 [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling Matt_Domsch
2002-09-30 4:32 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-11 19:09 Matt_Domsch
2002-09-12 18:00 ` Patrick Mochel
2002-09-12 18:48 ` Matt Domsch
2002-09-09 1:17 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-03 22:05 Matt Domsch
2002-09-03 23:29 ` Daniel Phillips
2002-09-04 4:35 ` Andre Hedrick
2002-09-04 16:02 ` 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=20BF5713E14D5B48AA289F72BD372D68C1E7ED@AUSXMPC122.aus.amer.dell.com \
--to=matt_domsch@dell.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=phillips@arcor.de \
/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).