search for: efi_udp4_protocol

...rom the "random" pool). The questions would be 1) What's the spec? and 2) How closely do the three or more implementations we've observed follow the spec? UEFI_2.4_0.pdf (page references are print-labeled page numbers not PDF page numbers; function context also provided) p1377 (EFI_UDP4_PROTOCOL.Configure()) "With different parameters in UdpConfigData, Configure() can be used to bind this instance to specified port." covers the manual case. p1376 (EFI_UDP4_PROTOCOL.GetModeData()) "StationPort" "The port number to which this EFI UDPv4 Protocol instance is bound. If...

On Thu, Nov 28, 2013 at 9:47 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Nov 28, 2013 at 9:34 PM, Celelibi <celelibi at gmail.com> wrote: >> Without an assigned source port, Transmit function assign a random new >> source port to the packet being sent. It thus have to be set before >> calling Transmit if the source port have already been decided.

...top of an EFI_MANAGED_NETWORK_PROTOCOL protocol in order to perform packet level transactions) _UdpFunctionTable _UdpOpen() _UdpClose() _UdpRead() _UdpWrite() _UdpGetInformation() _UdpSetInformation() on the other hand syslinux.efi uses EFI_UDP4_SERVICE_BINDING_PROTOCOL/EFI_UDP4_PROTOCOL instead. About PXEbc Peter has recently said: > The problem with the pxebc is that it only supports one concurrent TFTP > connection, and Syslinux expects to be able to keep multiple files open > at the same time. > http://www.syslinux.org/archives/2015-August/024025.html I wonder why...

On Wed, Sep 23, 2015 at 4:24 PM, Patrick Masotta <masottaus at yahoo.com> 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