From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 2/2] efi: device path for nvme
Date: Sat, 5 Oct 2019 00:32:48 +0200 [thread overview]
Message-ID: <460c19c6-4d2c-b153-7461-e15b4ab8879e@gmx.de> (raw)
In-Reply-To: <20191003142417.GA50522@nox.fritz.box>
On 10/3/19 4:24 PM, Patrick Wildt wrote:
> This allows our EFI API to create a device path node for NVMe
> devices. It adds the necessary device path struct, uses the
> nvme namespace accessor to retrieve the id and eui64, and also
> provides support for the device path text protocol.
>
> Signed-off-by: Patrick Wildt <patrick@blueri.se>
> ---
I have tested with an NVMe drive mounted on a MACCHIATObin and saw
consistent device paths and GUIDs in U-Boot, UEFI Shell and Debian:
In U-Boot:
=> efidebug devices
Device Device Path
================ ====================
000000007fb90380
/VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/NVMe(0x1,00-25-38-b5-81-e6-05-65)
In UEFI Shell (started from U-Boot):
BLK1: Alias(s):
/VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/NVMe(0x1,00-25-38-b5-81-e6-05-65)
In Debian:
$ smartctl -a /dev/nvme0n1
Namespace 1 IEEE EUI-64: 002538 b581e60565
The first bytes match the brand of the drive:
http://standards-oui.ieee.org/oui.txt:
002538 Samsung Electronics Co., Ltd., Memory Division
Tested-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
next prev parent reply other threads:[~2019-10-04 22:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 21:11 [U-Boot] [PATCH] efi: device path for nvme Patrick Wildt
2019-10-03 3:06 ` Bin Meng
2019-10-03 6:48 ` Heinrich Schuchardt
2019-10-03 9:19 ` Patrick Wildt
2019-10-03 9:21 ` [U-Boot] [PATCH v2] " Patrick Wildt
2019-10-03 9:38 ` Bin Meng
2019-10-03 9:56 ` [U-Boot] [PATCH] nvme: add accessor to namespace id and eui64 Patrick Wildt
2019-10-03 10:25 ` Bin Meng
2019-10-03 10:33 ` Patrick Wildt
2019-10-03 10:36 ` Bin Meng
2019-10-03 11:01 ` [U-Boot] [PATCH 1/2] " Patrick Wildt
2019-10-03 11:13 ` Bin Meng
2019-10-03 11:48 ` [U-Boot] [PATCH v2 " Patrick Wildt
2019-10-03 11:52 ` Bin Meng
2019-10-03 11:57 ` [U-Boot] [PATCH v2 2/2] efi: device path for nvme Patrick Wildt
2019-10-03 11:02 ` [U-Boot] [PATCH " Patrick Wildt
2019-10-03 13:12 ` Heinrich Schuchardt
2019-10-03 13:32 ` Patrick Wildt
2019-10-03 14:24 ` [U-Boot] [PATCH v3 " Patrick Wildt
2019-10-04 22:32 ` Heinrich Schuchardt [this message]
2019-10-03 9:57 ` [U-Boot] [PATCH] " Patrick Wildt
2019-10-03 10:29 ` Bin Meng
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=460c19c6-4d2c-b153-7461-e15b4ab8879e@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=u-boot@lists.denx.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