search for: avoidusing

...ot;; that could be becauseHP just does not need to test their UDP4 Binding Services because bootmgfw.efi does not use that, then they might very well have a non-reported FW bug there. But how to know if it is a problem in our side or their side? who knows.. but also "who cares" is we can avoidusing EFI UDP4 Binding Services... That's why I think we should redesign the conf strategy avoiding the requirement of simultaneous TFTP transfers and stick to PXEbc like bootmgfw.efi does. On that case if we got a bugthe chances are it is just "our" fault. Best,Patrick

>>>>>I do not understand.Are we parsing a configuration file and potentially >>starting new TFTP transfers while downloading it? How can we do this on >>a single thread?We cannot stop/resume a TFTP transfer then I cannot >>imagine how to detect an INCLUDE during TFTP transfer N to launch TFTP >>transfer N+1 if TFTP transfer N is not finished yet, all in a