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 <patr...@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.g...@gmx.de>
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
