Displaying 4 results from an estimated 4 matches for "efi_tcp4_service_binding_protocol".
2016 Jun 13
2
Getting HTTP path-prefix to work with syslinux.efi
> > Is syslinux.efi supposed to be able to handle HTTP URLs?
>
> If the underlying firmware can. Try just specifying an HTTP URL in the
> config or on the command line instead of the path-prefix option.
Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP.
Somehow I was under the impression improvements from pxelinux variants
like lpxelinux were
2016 Jun 14
2
Getting HTTP path-prefix to work with syslinux.efi
...irmware A16) seem have a built-in EFI shell option, but in all three
cases I had success running the external EFI shell from
github.com/tianocore/edk2/tree/master/EdkShellBinPkg (naming it
/efi/boot/bootx64.efi on a FAT USB stick).
> I'm guessing a lack of TCPv4Sb (an alias for the
> EFI_TCP4_SERVICE_BINDING_PROTOCOL ).
You're onto something. All three systems do report TCPv4Sb identically
in their "guid" output,
TCPv4Sb : 00720665-67EB-4A99-BAF7-D3C33A1C7CC9
yet in the "dh -p Net" output, only the OptiPlex 9020 lists TCPv4Sb.
That is also the only one of the three systems for which...
2016 Jun 14
0
Getting HTTP path-prefix to work with syslinux.efi
...ves/2015-August/024005.html and
http://www.syslinux.org/archives/2015-August/024055.html
version > fs0:\efi-ver.txt
guid > fs0:\efi-guid.txt
or alias > fs0:\efi-alias.txt
dh > fs0:\efi-dh.txt
dh -p Net > fs0:\efi-dh-net.txt
I'm guessing a lack of TCPv4Sb (an alias for the
EFI_TCP4_SERVICE_BINDING_PROTOCOL ).
> Somehow I was under the impression improvements from pxelinux variants like
> lpxelinux were already wrapped into the EFI version.
>
> Is there an "l" version of syslinux.efi?
No.
> Or any way to get HTTP transfers
> with UEFI on a system whose underlying firmwar...
2016 Jun 15
0
Getting HTTP path-prefix to work with syslinux.efi
...nal EFI shell from
> github.com/tianocore/edk2/tree/master/EdkShellBinPkg (naming it
> /efi/boot/bootx64.efi on a FAT USB stick).
Examining a 9020 I have access to, I'm guessing that depends on what's
on the HDD.
>> I'm guessing a lack of TCPv4Sb (an alias for the
>> EFI_TCP4_SERVICE_BINDING_PROTOCOL ).
>
>
> You're onto something. All three systems do report TCPv4Sb identically in
> their "guid" output,
>
> TCPv4Sb : 00720665-67EB-4A99-BAF7-D3C33A1C7CC9
>
> yet in the "dh -p Net" output, only the OptiPlex 9020 lists TCPv4Sb. That is
> also the...