From: "Fu, Siyuan" <siyuan.fu@intel.com>
To: Santhapur Naveen <naveens@amiindia.co.in>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: PXE boot option lacks IPv4 device path
Date: Tue, 13 Jun 2017 01:27:48 +0000 [thread overview]
Message-ID: <B1FF2E9001CE9041BD10B825821D5BC58B33BCA3@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <625A2455CC232F40B0F38F05ACED6D97C869106E@Venus2.in.megatrends.com>
Hi, Naveen
Are you using the PXE driver in MdeModulePkg? Only the NetworkPkg PXE driver 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 Santhapur 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<https://github.com/tianocore/edk2>. I've enabled PXE boot support and I could see only MAC device path (005056C00002, 0x1) present for all PXEv4 boot options something 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
next prev parent reply other threads:[~2017-06-13 1:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 4:00 PXE boot option lacks IPv4 device path Santhapur Naveen
2017-06-13 1:27 ` Fu, Siyuan [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-12 3:57 Santhapur Naveen
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=B1FF2E9001CE9041BD10B825821D5BC58B33BCA3@SHSMSX103.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