Displaying 4 results from an estimated 4 matches for "uefi_network_driv".
Did you mean:
uefi_network_driver
2015 Jul 09
3
EFI: PXE: "My IP is 0.0.0.0"
...ain 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.linaro.org/LEG/Engineering/Kernel/UEFI/UEFI_Network_Driver
>>>
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.
<<<
Yes, but I use empty virtual cl...
2015 Jul 10
0
EFI: PXE: "My IP is 0.0.0.0"
...this imply lot of code.
Not as much as you may think. We already have lwIP implemented into
lpxelinux.0. It's more a matter of using more glue.
> 2) SNP has its non-blocking transmit issues ; see "Flaws in the design" at
> https://wiki.linaro.org/LEG/Engineering/Kernel/UEFI/UEFI_Network_Driver
https://wiki.linaro.org/LEG/Engineering/Kernel/UEFI/UEFI_Network_Driver#Flaws_in_the_design
certainly gives some things to think about.
As a side note, I'd expect anything that used SNP should be able to
shut everything else off and have to implement enough of a TCP/IP
stack to be proper fo...
2015 Jul 10
3
EFI: PXE: "My IP is 0.0.0.0"
...imply lot of code.
Not as much as you
may think.? We already have lwIP implemented into lpxelinux.0.? It's more a matter of using more glue.
> 2) SNP has its non-blocking transmit issues ; see "Flaws in the design" at
> https://wiki.linaro.org/LEG/Engineering/Kernel/UEFI/UEFI_Network_Driver#Flaws_in_the_design
certainly gives some things to think about.
As a side note, I'd expect anything that used SNP should be 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 doe...
2015 Jul 06
2
EFI: PXE: "My IP is 0.0.0.0"
>>>
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