public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephane Eranian <eranian@frankl.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Deterimining EFI device number within Linux?
Date: Wed, 28 Mar 2001 17:59:53 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005364@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005359@msgid-missing>

Matt,

On Tue, Mar 27, 2001 at 05:18:50PM -0600, Matt_Domsch@Dell.com wrote:
> Does anyone know how to determine the EFI Device Number (such as 0x80) for a
> disk known as /dev/sda, under Linux (ideally from user-space, but I'd take a
> kernel-space trick too)?  There's an equivalent problem in IA-32 which has
> no known solution.  I'm hoping there is for EFI<->Linux.

If you forget about the bios 0x80 stuff, EFI uses device paths as can be
seen from the EFI shell by typing map. The text on the righthand side is 
the device path. It is based on some PCI, ACPI stuff. There is no connection
with the Linux way of doing things.

For instance:
fs0  : VenHw(Unknown Device:80)/HD(Part1,Sig00000000)

If you forget about fs0, there is no a priori way to map
VenHw(Unknown Device:80)/HD(Part1,Sig00000000) to /dev/sda. You would have
to know how (the order) the devices get scanned by both EFI and Linux to make 
the connection. As David pointed out, your best chances are to reconstruct
the hardware path to the device (including partitions) and to somehow convert
this into the equivalent EFI device path.


-- 
-Stephane


      parent reply	other threads:[~2001-03-28 17:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-27 23:18 [Linux-ia64] Deterimining EFI device number within Linux? Matt_Domsch
2001-03-27 23:18 ` Matt_Domsch
2001-03-28 17:12 ` David Mosberger
2001-03-28 17:59 ` Stephane Eranian [this message]

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=marc-linux-ia64-105590693005364@msgid-missing \
    --to=eranian@frankl.hpl.hp.com \
    --cc=linux-ia64@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