MESSAGING_DEVICE_PATH Intel NVMe Vendor defined

MESSAGING_DEVICE_PATH Intel NVMe Vendor defined

[David F.]

Hello,

Testing a system with NVMe Intel SSD drive doesn't give a meaningful
description in the shell or converting the device path to text in
general using the EDK2 (you only get a "?").   It appears it's because
the MESSAGING_DEVICE_PATH for this Intel NVMe is vendor defined.
Where do you find the information for vendor defined paths?   Adding
these to the EDK2 as they are created would be nice to get friendly
descriptions.

Thanks.

Re: MESSAGING_DEVICE_PATH Intel NVMe Vendor defined

[Wu, Hao A]

Hi David,

The UEFI spec defines the format of an NVMe device node, I think the
driver (maybe on the NVME option rom) that produces the device path for
the NVME device should get updated to follow the spec.

For those vendor defined paths, I think the DevicePathLib will only dump
the hex of device node content. There is no method to extract the
information from them since they are not documented in the UEFI spec.

Best Regards,
Hao Wu

> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of David
> F.
> Sent: Saturday, June 24, 2017 1:56 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] MESSAGING_DEVICE_PATH Intel NVMe Vendor defined
> 
> Hello,
> 
> Testing a system with NVMe Intel SSD drive doesn't give a meaningful
> description in the shell or converting the device path to text in
> general using the EDK2 (you only get a "?").   It appears it's because
> the MESSAGING_DEVICE_PATH for this Intel NVMe is vendor defined.
> Where do you find the information for vendor defined paths?   Adding
> these to the EDK2 as they are created would be nice to get friendly
> descriptions.
> 
> Thanks.
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel