search for: pxebasecodeprotocol

Displaying 5 results from an estimated 5 matches for "pxebasecodeprotocol".

2015 Aug 13
3
[syslinux:master] efi/pxe: Reuse handle
...Reuse handle > > Store and reuse handle found with EFI_LOADED_IMAGE_PROTOCOL for > EFI_PXE_BASE_CODE_PROTOCOL and EFI_UDP4_SERVICE_BINDING_PROTOCOL > > This caused machines with multiple NICs to not reliably attach to the > correct NIC handle. > > gnu-efi LoadedImageProtocol PxeBaseCodeProtocol Udp4ServiceBindingProtocol > > Reported-By: Holger Baust <holger.baust at freenet.ag> > Reported-By: Michael Glasgow <glasgow at beer.net> > Reported-By: Da Shi Cao <dscao999 at gmail.com> > Signed-off-by: Gene Cumm <gene.cumm at gmail.com> > > --- >...
2015 Jul 31
5
EFI: ipxe + syslinux = Failed to read blocks: 0xC
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
2015 Aug 26
4
[PATCH 0/3] efi: A few warning fixes
From: Sylvain Gault <sylvain.gault at gmail.com> I don't know if I should merge those trivial warning fix into one commit. I can reformat it as requested. Those are a few warning fixes for the efi part. The code involved has mainly been introduced in recent commits. Sylvain Gault (3): efi: fix warnings about argument types efi: fix pointer-type mismatch assigment warning efi: fix
2015 Jul 31
0
EFI: ipxe + syslinux = Failed to read blocks: 0xC
...are trying to boot syslinux.efi from iPXE that was not patched. In my understanding iPXE patches some UEFI network services in order to provide a better user experience but this unfortunately breaks syslinux's usage of UEFI services where it thinks it's not booted from PXE (cannot find PxeBaseCodeProtocol) and tries to read from disk which fails with the above error. > discussing this problem. The user mjt (Michael Tokarev, also on this list) > found a branch of ipxe that contains two patches that should solve this > problem. See http://www.syslinux.org/archives/2015-June/023582.html fo...
2015 Jun 03
5
[PATCH 0/1] EFI PXE DHCP/proxyDHCP issues fix
...*bc; EFI_PXE_BASE_CODE_DHCPV4_PACKET* pkt_v4; unsigned int pkt_len = sizeof(EFI_PXE_BASE_CODE_PACKET); EFI_STATUS status; EFI_HANDLE *handles = NULL; UINTN nr_handles = 0; uint8_t hardlen; uint32_t ip; char dst[256]; status = LibLocateHandle(ByProtocol, &PxeBaseCodeProtocol, NULL, &nr_handles, &handles); if (status != EFI_SUCCESS) return; /* Probably want to use IPv4 protocol to decide which handle to use */ status = uefi_call_wrapper(BS->HandleProtocol, 3, handles[0], &PxeBaseCodeProtocol, (void **)&bc);...