From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) (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 DA88621A08D8A for ; Mon, 12 Jun 2017 18:26:38 -0700 (PDT) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jun 2017 18:27:52 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,335,1493708400"; d="scan'208";a="112364083" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by orsmga005.jf.intel.com with ESMTP; 12 Jun 2017 18:27:52 -0700 Received: from fmsmsx156.amr.corp.intel.com (10.18.116.74) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 12 Jun 2017 18:27:52 -0700 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by fmsmsx156.amr.corp.intel.com (10.18.116.74) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 12 Jun 2017 18:27:51 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.116]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.197]) with mapi id 14.03.0319.002; Tue, 13 Jun 2017 09:27:49 +0800 From: "Fu, Siyuan" To: Santhapur Naveen , "edk2-devel@lists.01.org" Thread-Topic: PXE boot option lacks IPv4 device path Thread-Index: AdLjLu88AvwtfSWpTEaD766hkcmkGwAAWytgACzxkQA= Date: Tue, 13 Jun 2017 01:27:48 +0000 Message-ID: References: <625A2455CC232F40B0F38F05ACED6D97C869106E@Venus2.in.megatrends.com> In-Reply-To: <625A2455CC232F40B0F38F05ACED6D97C869106E@Venus2.in.megatrends.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: PXE boot option lacks IPv4 device path 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: Tue, 13 Jun 2017 01:26:39 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Naveen Are you using the PXE driver in MdeModulePkg? Only the NetworkPkg PXE drive= r will create boot option with IPvX device path node. Best Regards, Siyuan -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Sant= hapur Naveen Sent: Monday, June 12, 2017 12:00 PM To: edk2-devel@lists.01.org Subject: Re: [edk2] PXE boot option lacks IPv4 device path This behavior is seen only in Simulator From: Santhapur Naveen Sent: Monday, June 12, 2017 9:27 AM To: edk2-devel@lists.01.org Subject: PXE boot option lacks IPv4 device path Hello all, I've built and run the Nt32Pkg source from here. I've enabled PXE boot support and I could see only= MAC device path (005056C00002, 0x1) present for all PXEv4 boot options som= ething like UEFI PXEv4 MAC(005056C000XX). But for HTTPv4, the device path is "MAC (005056C00002, 0x01= )/IPv4(0.0.0.0, 0x0, DHCP, 0.0.0.0, 0.0.0.0, 0.0.0.0)/Uri()" Why the PXE boot option doesn't have the IPv4 device path? Your comments are highly appreciated. Regards, Naveen _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel