From: Heinrich Schuchardt Date: Sat, 5 Oct 2019 00:32:48 +0200 Subject: [U-Boot] [PATCH v3 2/2] efi: device path for nvme In-Reply-To: <20191003142417.GA50522@nox.fritz.box> References: <20191002211131.GA44383@nox.fritz.box> <5756478a-a091-be62-1f84-1b5efa59f9fd@gmx.de> <20191003092127.GD47163@nox.fritz.box> <20191003095617.GA48482@nox.fritz.box> <20191003103336.GA49768@nox.fritz.box> <20191003110216.GC49768@nox.fritz.box> <2e625188-b53e-cf19-e25e-9b6cdc7122e7@gmx.de> <20191003142417.GA50522@nox.fritz.box> Message-ID: <460c19c6-4d2c-b153-7461-e15b4ab8879e@gmx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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 > --- 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