public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Wu, Hao A" <hao.a.wu@intel.com>
To: David F. <df7729@gmail.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: MESSAGING_DEVICE_PATH Intel NVMe Vendor defined
Date: Mon, 26 Jun 2017 02:54:30 +0000	[thread overview]
Message-ID: <B80AF82E9BFB8E4FBD8C89DA810C6A0931CC5553@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CAGRSmLvPbO9C9ox+SQT+_VUMpyB=mOmNYeUOeqJ2VEHsx-euVw@mail.gmail.com>

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


      reply	other threads:[~2017-06-26  2:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 17:56 MESSAGING_DEVICE_PATH Intel NVMe Vendor defined David F.
2017-06-26  2:54 ` Wu, Hao A [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-list 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=B80AF82E9BFB8E4FBD8C89DA810C6A0931CC5553@SHSMSX104.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /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