From: Patrick Mochel <mochel@osdl.org>
To: Matt Domsch <Matt_Domsch@Dell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling
Date: Mon, 30 Sep 2002 18:55:51 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0209301844310.18550-100000@cherise.pdx.osdl.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0209271606001.16331-100000@humbolt.us.dell.com>
> |-- bus
> | `-- system
> | |-- devices
> | | |-- int13_dev80 -> ../../../root/bios/int13_dev80
> | | |-- int13_dev81 -> ../../../root/bios/int13_dev81
> | `-- drivers
> | |-- edd
> `-- root
> |-- bios
> | |-- int13_dev80
> | | |-- host_bus
> | | |-- info
> | | |-- interface
> | | |-- name
> | | `-- power
> | |-- int13_dev81
> | | |-- host_bus
> | | |-- info
> | | |-- interface
> | | |-- name
> | | `-- power
> | |-- name
> | `-- power
>
>
> (Yes, the system bus isn't the right place for them to go, but it must
> go on some bus, and eventually it will get moved to a better place.)
[ Sorry, I didn't get this out earlier, but you're just too damn fast with
your resubmissions.. ;)]
Don't use struct device for the firmware objects. They're not really
devices; they're another type of entity that has some sort of magic
ia32 voodoo relationship with real devices.
I recently converted ACPI to abandon the notion that the namespace objects
were real devices. In doing so, I gave them their own top-level directory
in driverfs. Don't do this. That's only a temporary solution until I
create a 'firmware' or 'platform' directory for all of you people to live.
> The 'info' file contains the full set of information returned by BIOS
> with extra error reporting. This exists for vendor BIOS debugging purposes.
>
> The 'host-bus' file contains the PCI (or ISA, HyperTransport, ...)
> identifying information, as BIOS knows it.
>
> The 'interface' file contains the SCSI (or IDE, USB, ...) identifying
> information, as BIOS knows it.
>
>
> $ cat int13_dev80/host_bus
> PCI 02:01.0 channel: 0
How about a symlink to the bus's directory? Or the PCI device that is the
controller?
> $ cat int13_dev80/interface
> SCSI id: 0 lun: 0
And, a symlink to the device itself? I liked it better the way you had it
before :)
> $ cat int13_dev80/info
> 80 30 01 00 .0..
> 1e 00 09 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 3a b9 8b 08 00 00 00 00 00 02 ff ff ff ff be dd :...............
> 2c 00 00 00 50 43 49 00 53 43 53 49 00 00 00 00 ,...PCI.SCSI....
> 02 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 00 00 00 00 00 00 00 00 00 28 .........(
> version: 3.0
> Extensions:
> Fixed disk access
> Info Flags:
> dma_boundry_error_transparent
> write_verify
> num_default_cylinders: 0
> num_default_heads: 0
> sectors_per_track: 0
> number_of_sectors: 88bb93a
> PCI 02:01.0 channel: 0
> SCSI id: 0 lun: 0
Ugh. Drop the ascii-fying hexdump for one. I'd also strongly encourage you
to split the data in 'info' to separate files.
-pat
next prev parent reply other threads:[~2002-10-01 1:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20BF5713E14D5B48AA289F72BD372D6821CE34@AUSXMPC122.aus.amer.dell.com>
2002-09-27 21:30 ` [RFC][PATCH] x86 BIOS Enhanced Disk Device (EDD) polling 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 [this message]
2002-10-01 3:37 Matt_Domsch
-- strict thread matches above, loose matches on Subject: below --
2002-09-30 4:32 Matt_Domsch
2002-09-11 19:09 Matt_Domsch
2002-09-12 18:00 ` Patrick Mochel
2002-09-12 18:48 ` Matt Domsch
2002-09-10 22:43 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=Pine.LNX.4.44.0209301844310.18550-100000@cherise.pdx.osdl.net \
--to=mochel@osdl.org \
--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).