Displaying 6 results from an estimated 6 matches for "tftppgetimageregular".
2015 Sep 23
4
Problem with 90MB Initrd
...ng better than we do about TFTP transfers.
> They:
> 1) do not rely on Service Binding Protocols then old EFI firmware PCs do not complain.
> 2) I think they do better when handling EFI Events and Timers.
>
> The key to see how they do what they do is this bootmgfw.efi function:
> TftppGetImageRegular
> but the task is time consuming; efi environment functions are only referenced by an index
> on a pointer table then knowing what functions they are really calling is not very easy
> to see.
My current inclination is that there's a bug in Syslinux's TFTP+UDP
implementation. If i...
2015 Sep 22
2
Problem with 90MB Initrd
On 09/21/2015 06:20 AM, Patrick Masotta via Syslinux wrote:
>
> BTW if you take a minute and read the first report
> https://communities.vmware.com/message/2536774
> You'll realize that VMWare TFTP "surprisingly" does not present slow TFTP transfers
> when they are driven by MS "bootmgfw.efi"; instead the problem is only shown when
> transfers are driven
2015 Sep 30
1
Problem with 90MB Initrd
...They:
>>> 1) do not rely on Service Binding Protocols then old EFI firmware
>PCs do not complain.
>>> 2) I think they do better when handling EFI Events and Timers.
>>>
>>> The key to see how they do what they do is this bootmgfw.efi
>function:
>>> TftppGetImageRegular
>>> but the task is time consuming; efi environment functions are only
>referenced by an index
>>> on a pointer table then knowing what functions they are really
>calling is not very easy
>>> to see.
>>
>> My current inclination is that there's a bug...
2015 Sep 23
0
Problem with 90MB Initrd
...fw.efi" is doing something better than we do about TFTP transfers.
They:
1) do not rely on Service Binding Protocols then old EFI firmware PCs do not complain.
2) I think they do better when handling EFI Events and Timers.
The key to see how they do what they do is this bootmgfw.efi function:
TftppGetImageRegular
but the task is time consuming; efi environment functions are only referenced by an index
on a pointer table then knowing what functions they are really calling is not very easy
to see.
Best,
Patrick
2015 Sep 30
0
Problem with 90MB Initrd
...ut TFTP transfers.
>> They:
>> 1) do not rely on Service Binding Protocols then old EFI firmware PCs do not complain.
>> 2) I think they do better when handling EFI Events and Timers.
>>
>> The key to see how they do what they do is this bootmgfw.efi function:
>> TftppGetImageRegular
>> but the task is time consuming; efi environment functions are only referenced by an index
>> on a pointer table then knowing what functions they are really calling is not very easy
>> to see.
>
> My current inclination is that there's a bug in Syslinux's TFTP+UDP...
2015 Sep 26
0
Problem with 90MB Initrd
...ng better than we do about TFTP transfers.
> They:
> 1) do not rely on Service Binding Protocols then old EFI firmware PCs do not complain.
> 2) I think they do better when handling EFI Events and Timers.
>
> The key to see how they do what they do is this bootmgfw.efi function:
> TftppGetImageRegular
> but the task is time consuming; efi environment functions are only referenced by an index
> on a pointer table then knowing what functions they are really calling is not very easy
> to see.
My current inclination is that there's a bug in Syslinux's TFTP+UDP
implementation. If it...