public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Zimmer, Vincent" <vincent.zimmer@intel.com>
To: Heyi Guo <heyi.guo@linaro.org>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Tian, Feng" <feng.tian@intel.com>,
	"Wu, Jiaxin" <jiaxin.wu@intel.com>,
	"Fu, Siyuan" <siyuan.fu@intel.com>,
	"Zeng, Star" <star.zeng@intel.com>
Subject: Re: Which revision of PXE spec does EDK2 code conform to?
Date: Tue, 29 Nov 2016 13:08:06 +0000	[thread overview]
Message-ID: <76DE84138CBE89489874B70B432D8F9B91479D2A@ORSMSX105.amr.corp.intel.com> (raw)
In-Reply-To: <7491c75b-6f55-3da0-8983-55a72cd7ab49@linaro.org>

Yes.  For IPV4 TFTP-based PXE the wire protocol adheres to the PXE 2.1 specification with some errata that supercedes that frozen document found under section "E.4.20 PXE 2.1 specification wire protocol clarifications" of the UEFI 2.6 specification.   For IPV6 PXE-style TFTP boot the wire protocol is found wholly in the UEFI 2.6 specification.

Vincent

-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Heyi Guo
Sent: Tuesday, November 29, 2016 3:38 AM
To: edk2-devel@lists.01.org
Cc: Tian, Feng <feng.tian@intel.com>; Wu, Jiaxin <jiaxin.wu@intel.com>; Fu, Siyuan <siyuan.fu@intel.com>; Zeng, Star <star.zeng@intel.com>
Subject: [edk2] Which revision of PXE spec does EDK2 code conform to?

Hi folks,

Which revision of PXE spec does EDK2 code conform to? Is it PXE v2.1? Do PXE implementations in MdeModulePkg and NetworkPkg comform to the same revision?

Thanks and regards,

Heyi
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2016-11-29 13:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 11:38 Which revision of PXE spec does EDK2 code conform to? Heyi Guo
2016-11-29 13:08 ` Zimmer, Vincent [this message]
2016-12-13 12:20   ` Heyi Guo

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=76DE84138CBE89489874B70B432D8F9B91479D2A@ORSMSX105.amr.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