search for: efi_simple_network_protocol

...one if necessary. It's also a question of how fast the firmware bothers to be. Considering our rate, this in theory shouldn't matter. <<< agreed >>> Oh how fun. UEFI Specifications version 2.0 states "An EFI_PXE_BASE_CODE_PROTOCOL will be layered on top of an EFI_SIMPLE_NETWORK_PROTOCOL protocol in order to perform packet level transactions." while version 2.1 states "An EFI_PXE_BASE_CODE_PROTOCOL will be layered on top of an EFI_MANAGED_NETWORK_PROTOCOL protocol in order to perform packet level transactions." >>> Could this be the reason why in the past P...

>>> > 1) There's not "any" SB protocol present (Elitebook 8460p/2560p) The only solution for these is to use our own stack (likely full TCP/IP like lwIP) and connect to the Net GUID (EFI_SIMPLE_NETWORK_PROTOCOL).? Does the handle for Pxebc contain a Net?? >>> It does contain a Net but there are 2 issues with SNP: 1) The interface is different than UDPv4/TCPv4 protocols; this imply lot of code. 2) SNP has its non-blocking transmit issues ; see "Flaws in the design" at https://wiki.lina...

...if you are trying to boot syslinux.efi from iPXE that > was not patched. I was using commit 87981bb from the branch 'qemu' at git.kraxel.org/ipxe. The last two log messages for this branch are: 87981bb [efi] make load file protocol optional ca65a1f efi_snp: improve compliance with the EFI_SIMPLE_NETWORK_PROTOCOL spec These are the patches Michael mentioned in his post. Did I miss other patches? > If you go back one message in that thread you'll find a link to another > thread explaining what's happening and what workarounds are available > here: http://sourceforge.net/p/edk2/mailman/m...

>>> I'm just debating what's the best algorithm here.? It would seem if the LoadeImage's DeviceHandle provides UDPv4Sb, use it as it's guaranteed to be the same interface.? Otherwise, we need a MNPSb (EFI_MANAGED_NETWORK_SERVICE_BINDING) that provides UDPv4Sb across the same interface.? Presumably it should also provide TCPv4Sb (rather than being on a separate

...ottaus at yahoo.com> wrote: > > What I've found: > (from older to newer hardware) > > 1) There's not "any" SB protocol present (Elitebook 8460p/2560p) The only solution for these is to use our own stack (likely full TCP/IP like lwIP) and connect to the Net GUID (EFI_SIMPLE_NETWORK_PROTOCOL). Does the handle for Pxebc contain a Net? I found out that my EFI shell on VMware VMs can also handle output redirection like: guid > fs0:\efi-guid.txt dh > fs0:\efi-dh.txt dh bd >> fs0:\efi-dh.txt fs0 being the EFI boot partition on the hard drive of the VM. > 2) SB protocols...

On Fri, Jul 10, 2015 at 5:00 AM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > Oh how fun. UEFI Specifications version 2.0 states "An > EFI_PXE_BASE_CODE_PROTOCOL will be layered on top of an > EFI_SIMPLE_NETWORK_PROTOCOL protocol in order to perform packet level > transactions." while version 2.1 states "An EFI_PXE_BASE_CODE_PROTOCOL > will be layered on top of an EFI_MANAGED_NETWORK_PROTOCOL protocol in > order to perform packet level transactions." >>>> > > Could this be...

...5:30 AM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > > 1) There's not "any" SB protocol present (Elitebook 8460p/2560p) > > The only solution for these is to use our own stack (likely full > TCP/IP like lwIP) and connect to the Net GUID (EFI_SIMPLE_NETWORK_PROTOCOL). > Does the handle for Pxebc contain a Net? >>>> > > It does contain a Net but there are 2 issues with SNP: > 1) The interface is different than UDPv4/TCPv4 protocols; this imply lot of code. Not as much as you may think. We already have lwIP implemented into lpxelinux.0...

...nux at zytor.com> wrote: > On Fri, Jul 10, 2015 at 5:00 AM, Patrick Masotta <masottaus at yahoo.com> > wrote: > > >>>> > > Oh how fun. UEFI Specifications version 2.0 states "An > > EFI_PXE_BASE_CODE_PROTOCOL will be layered on top of an > > EFI_SIMPLE_NETWORK_PROTOCOL protocol in order to perform packet level > > transactions." while version 2.1 states "An EFI_PXE_BASE_CODE_PROTOCOL > > will be layered on top of an EFI_MANAGED_NETWORK_PROTOCOL protocol in > > order to perform packet level transactions." > >>>> >...

Hello dear list, Using VMware I built a test setup of a server with dhcp, tftp and a http-server and several pxe-clients with EFI mode turned on. This setup worked, albeit with the exponential-like decay of IO rate I described earlier. The work-around of using HTTP works beautifully though. So it was time for the next step. Migrate this setup to our automated testing environment that runs