Hi,
I found an inconsistency between UEFI specifcation (v2.7) and EDK2 source. The
"RouteTableSize" defined in EFI_IP4_CONFIG2_INTERFACE_INFO is "Size of the
following RouteTable , in bytes. May be zero". The related definition can be
found in p.1693 of v2.7 specification.
However, the edk2 seems
t;;;
}
subclass "PXEClient" "PXEClient:Arch:00022" {
option dhcp6.bootfile-url
"tftp://[fc00:ba49:1625:fb0f::137]/boot/grub/arm64-efi/core.efi";;
}
subclass "PXEClient" "PXEClient:Arch:0" {
option dhcp6.bootfile-url
"tftp://[fc00:b
res I should take.
>
> Best Regards
> Lubo
>
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> Michael Chang
> Sent: Thursday, July 21, 2016 9:59 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] [PATCH] Fix IPv6 HT
The size of the ClassIdentifier is apparently wrong in the structure. In my
testing it caused the vendor class data to be displayed as bogus
"HTTPClient:Arch00016x:UNDI00300". After correcting the size the vendor class
data is "HTTPClient:Arch00016:UNDI003000" which looks good to me.
---
NetworkP
t; Thanks,
> Ye Ting
>
> -Original Message-----
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> Michael Chang
> Sent: Friday, May 20, 2016 12:57 PM
> To: edk2-devel@lists.01.org
> Subject: Re: [edk2] UEFI HTTP Boot Device Path and D
+0800, Michael Chang wrote:
> Background (And also Question):
> The PXE Base Code Protocol is no longer produced if selecting to boot from
> UEFI
> HTTP device from boot menu. Does anyone here know why or is it's just a
> problem
> of my environment (I'm using OVMF fro
does not exist") for locating TCB
for arriving packets ?
>
> Anyway, I think it's not easy to solve your problem only by using on current
> UEFI protocol. So let's understand the real requirement first, then we can
> try to figure out a way.
Hope my explainatio
is on the road) while
not stopping the other from working.
Thanks,
Michael
>
> Best Regards
> Siyuan
>
> > -Original Message-
> > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> > Michael Chang
> > Sent: Wednesday, May 4, 2016 6:23
would just discrupt any
TCP connection except the one established by EFI TCP protocol, which is not
make sense imho.
Thanks.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Michael Chang
---
NetworkPkg/TcpDxe/TcpInput.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletion
Background (And also Question):
The PXE Base Code Protocol is no longer produced if selecting to boot from UEFI
HTTP device from boot menu. Does anyone here know why or is it's just a problem
of my environment (I'm using OVMF from openSUSE) ?
That made the work to support it in grub2 more complic
10 matches
Mail list logo
