search for: loadeimag

>>> 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 handle)....

>>> Lovely, the ServiceBindings are on a handle that resembles the NIC while the Pxebc is IP-type specific.? Looks like we should try to do a ServiceBinding based on Pxebc but fall 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

...ain 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 are loaded under a different that LoadeImage's DeviceHandle, > while Pxebc is loaded under the LoadeImage's DeviceHandle. (Elitebook 8470p/2570p) a) Hunt for a Sb. b) use Net > 3) SB protocols and Pxebc are loaded under the LoadeImage's DeviceHandle (VMware Workstation 10). a) use Sb on Pxebc handle b) use Net > Abou...

...gt;> fs0:\efi-dh.txt fs0 being the EFI boot partition on the hard drive of the VM. <<< Yes, but I use empty virtual clients when testing Syslinux PXE then I prefer redirecting console commands to a USB pendrive >>> > 2) SB protocols are loaded under a different that LoadeImage's DeviceHandle, > while Pxebc is loaded under the LoadeImage's DeviceHandle. (Elitebook 8470p/2570p) a) Hunt for a Sb. b) use Net <<< I do a hunt for either UDPv4Sb or TCPv4Sb >>> > 3) SB protocols and Pxebc are loaded under the LoadeImage's DeviceHand...

...e able to shut everything else off and have to implement enough of a TCP/IP stack to be proper for its uses (ie no need to implement TCP or respond to TCP if it doesn't use TCP yet should respond to ARP requests). > >>> > > 2) SB protocols are loaded under a different that LoadeImage's DeviceHandle, > > while Pxebc is loaded under the LoadeImage's DeviceHandle. (Elitebook 8470p/2570p) > > a) Hunt for a Sb. > b) use Net > <<< > > I do a hunt for either UDPv4Sb or TCPv4Sb Just summarizing choices. >>>> > > 3) SB pr...

...The bguid handle with the right MAC is used for binding. > > So far it works in the problematic HP 2570p but also in a Vmware 10 client with double NIC. > I'll test a bit more and I'll upload the code. 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 handle). Addi...