public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Gene Heskett <gene.heskett@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Querying the bios from booted linux kernel?
Date: Fri, 04 Jan 2008 18:45:56 -0800	[thread overview]
Message-ID: <477EEF64.6030105@zytor.com> (raw)
In-Reply-To: <20080105021449.2af7a429@lxorguk.ukuu.org.uk>

Alan Cox wrote:
>> Unfortunately, it is not trivial to produce a mapping from EDD data to 
>> real-life disks.  Your best bet is if the disks have an MBR signature, 
> 
> Untrue for all but the very earliest EDD. True for our kernel support
> which wants improving some day
> 
>> in which case the EDD code will capture those; you can then correlate 
>> them to real disks.
> 
> EDD 1 provides the I/O base of each BIOS device so you can cross corelate
> at least each IDE device with the BIOS identifier. EDD 3 provides paths
> in multiple forms including PCI identifiers which serve the same purpose.
> 
> Unfortunately our EDD boot code doesn't capture the right bits in all
> these cases.

That's true for IDE, definitely, but for other drive technologies the 
information can be ether inadequate or downright misleading... 
especially when dealing with complex disk topologies.  Worse, as one 
could expect, the information provided is downright wrong in many cases.

To make matters worse, the EDD standard doesn't have a maintainer, so 
new technologies aren't assigned new identifier.

What you'd want is a way to query the disk serial number, but EDD 
doesn't provide that (there is the "packet interface", but it doesn't 
seem to be widely implemented.)

	-hpa

  reply	other threads:[~2008-01-05  2:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-05  0:13 Querying the bios from booted linux kernel? Gene Heskett
2008-01-05  0:47 ` H. Peter Anvin
2008-01-05  2:14   ` Alan Cox
2008-01-05  2:45     ` H. Peter Anvin [this message]
2008-01-05  4:18 ` Matt Domsch
2008-01-05 19:47   ` H. Peter Anvin

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=477EEF64.6030105@zytor.com \
    --to=hpa@zytor.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gene.heskett@gmail.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