From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id C80FF2095D20B for ; Sun, 25 Jun 2017 19:53:04 -0700 (PDT) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jun 2017 19:54:33 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,393,1493708400"; d="scan'208";a="1164580444" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by fmsmga001.fm.intel.com with ESMTP; 25 Jun 2017 19:54:32 -0700 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.319.2; Sun, 25 Jun 2017 19:54:32 -0700 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.151]) by SHSMSX103.ccr.corp.intel.com ([169.254.4.116]) with mapi id 14.03.0319.002; Mon, 26 Jun 2017 10:54:31 +0800 From: "Wu, Hao A" To: David F. , "edk2-devel@lists.01.org" Thread-Topic: [edk2] MESSAGING_DEVICE_PATH Intel NVMe Vendor defined Thread-Index: AQHS7EoI+RL8xgtiP0C/alqkXot4f6I2cfqQ Date: Mon, 26 Jun 2017 02:54:30 +0000 Message-ID: References: In-Reply-To: Accept-Language: zh-CN, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: MESSAGING_DEVICE_PATH Intel NVMe Vendor defined X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jun 2017 02:53:05 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 Da= vid > F. > Sent: Saturday, June 24, 2017 1:56 AM > To: edk2-devel@lists.01.org > Subject: [edk2] MESSAGING_DEVICE_PATH Intel NVMe Vendor defined >=20 > Hello, >=20 > 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. >=20 > Thanks. > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel