search for: image_devicehandl

...://github.com/ppatpat/syslinux/ > > a) a missing return; on an error condition at efi/pxe.c\net_parse_dhcp() > b) you close a protocol before creating its child at efi/main.c\efi_create_binding() Rewrote the commit messages and it's in at commit ID 5186539 > 2.2) I think "image_DeviceHandle" instead of "pxe_DeviceHandle" produces a code easier to follow; > specially when we end up using that handle to create a TCP4 or UDP4 child... Not all handles are devices but all usable devices have handles. The image_handle is a type EFI_LOADED_IMAGE_PROTOCOL, not a device. p...

...not have attached the Service Binding Protocol UDPv4Sb (in this case under the handle 172 instead). The HP 2570p is not really an old PC (~2013) then I can think if we continue using the "same handle" method we will have problems PXE booting lot of UEFI PCs. I think when we receive the image_DeviceHandle we must save it but also parse the associated DevicePath saving the MAC address too. When looking for Pxebc Protocol we can use the image_DeviceHandle, next when ServiceBinding we need to detect all the available SB handles of the required type, parse their DevicePath and take the one with a matc...

...P-stack (IPv4 or IPv6). <<< Yes it is the handle of the device (NIC) that loaded syslinux plus IP stack (as you said) but also all the attached Service Binding Protocols, PXE Protocol, and some more. All of them sharing the same device handle. >>> > 2.2) > I think "image_DeviceHandle" instead of > "pxe_DeviceHandle" produces a code easier to follow; > specially when we end up using > that handle to create a TCP4 or UDP4 child... Not all handles are devices but all usable devices have handles.? The image_handle is a type EFI_LOADED_IMAGE_PROTOCOL, no...

On Thu, Jun 25, 2015 at 7:28 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Jun 25, 2015 at 11:54 AM, Patrick Masotta <masottaus at yahoo.com> wrote: > >> Yes I know what you mean; >> "I think" the handle of the running image (our code) has a "path" telling us where >> was laded from. That would solve this thing. > > I just

...the Service Binding Protocol UDPv4Sb (in this case under the handle 172 instead). > > The HP 2570p is not really an old PC (~2013) then I can think if we continue using the "same handle" method we will have > problems PXE booting lot of UEFI PCs. > I think when we receive the image_DeviceHandle we must save it but also parse the associated DevicePath saving the MAC address too. > When looking for Pxebc Protocol we can use the image_DeviceHandle, next when ServiceBinding we need to detect > all the available SB handles of the required type, parse their DevicePath and take the one wi...

...back to MAC-based searching, saving all 3 handles, the image handle, Pxebc handle, and ServiceBinding handle.? Presumably the UDP and TCP handles _should_ be the same... -- -Gene <<< OK now it works. Everything is done within efi_create_binding(EFI_GUID *bguid, EFI_GUID *pguid) from image_DeviceHandle I get the right DevPath handle, I parse it and I get the MAC address. Next I LibLocateHandle(ByProtocol, bguid, NULL, &nr_handles, &handles) what gives me all the handles that include the Service Binding Protocol "bguid". For each of this handles I get the DevPath handle and I pa...

...ur last commit 2.1) I think I found a couple of issues check them corrected at https://github.com/ppatpat/syslinux/ a) a missing return; on an error condition at efi/pxe.c\net_parse_dhcp() b) you close a protocol before creating its child at efi/main.c\efi_create_binding() 2.2) I think "image_DeviceHandle" instead of "pxe_DeviceHandle" produces a code easier to follow; specially when we end up using that handle to create a TCP4 or UDP4 child... Best, Patrick

...all 3 handles, the image handle, Pxebc handle, and ServiceBinding handle. > Presumably the UDP and TCP handles _should_ be the same... > -- > -Gene > <<< > > OK now it works. > Everything is done within efi_create_binding(EFI_GUID *bguid, EFI_GUID *pguid) > from image_DeviceHandle I get the right DevPath handle, I parse it and I get the MAC address. > Next I LibLocateHandle(ByProtocol, bguid, NULL, &nr_handles, &handles) > what gives me all the handles that include the Service Binding Protocol "bguid". > For each of this handles I get the DevPath...