iPXE identifies the device it was pxe booted from by searching parents of the LoadedImage which support SNP and NII and uses the address of the installed NII and SNP as a discriminant to see if a devi

I am going to commit the cardinal sin of online dev support. ‘Never mind, found the problem’

Hi, I have a bit of an esoteric problem. When I configure the software iscsi intiator that is part of EDK2 platform network stack, the platform network stack with install iBFT table into the ACPI tabl

I skimmed the my emails and my eyes registered 'Ard Biesheuvel' and 'death' and my brain went 'but but but I've seen him just yesterday!'. Hope you are happy. T

Hi Mike, Thank you, that is great news! Cheers, Tom

Contributed-under: TianoCore Contribution Agreement 1.1 Signed-off-by: Tomas Pilar <tpilar@...> --- .../Source/Python/Capsule/GenerateCapsule.py | 25 ++++++++++++++++--- 1 file changed, 22

Hi, I assume you had a look at the DHCP RFC: https://tools.ietf.org/html/rfc2131. We have an automated test inhouse for testing PXE client implementations and the current UEFI upstream does not pass t

Hi Mike, This all looks really good, I didn't envisage this way to design it (swapping contexts on demand) but it's much simpler than what I had in mind. I should be able to integrate this easily with

Hi Mike, Sorry to say I have not yet filed a BZ. Would you like me to, or are you happy doing it? Cheers, Tom

Hi, I am currently pondering the most elegant way to implement capsule update for our devices that would work in the presence of multiple devices in the host. Capsule allows embedding a driver that is

Thanks, this is some good food for thought. I certainly appreciate the progress we've made since the old EFI days. Tom

Hi Siyuan, Thanks for the insights, hopefully removing the moderator will fix my current issue and I'll have a look at how to do the recycling better. Cheers, Tom

On some platforms (tftp clients), if the Snp.Receive() returns EFI_NOT_READY they do not poll the NIC until the next MnpSystemPoll(). Hence the delay before returning EFI_NOT_READY in case the packet

Hi Siyuan, I had to do some tweaks due to the fact that people in the wild want to PXE boot whole WDS installations which are upwards of 300MB. I have an internal set of queues where the NIC receives

Yeah, that makes sense I suppose. The end result is however that the network device is 'opened' as soon as ConnectController() is called rather than when someone wants to do networking. This seems wro

Ah, but I would expect the BDS to call ConnectController() on the NIC, but I would not expect the network stack to be started unless the device is actually chosen for PXE booting. In other words, the

Hmm, Mnp->Configure() will eventually call MnpStartSnp(). A grep for Mnp->Configure shows that: * ArpDxe performs this on DriverBinding.Start() * Ip6Dxe performs this on DriverBinding.Start() Ipv4 and

This was my assumption a well. I did not consider that another third party driver could be the cause of this. That's good to know, I was going to have a browse through the edk2 network stack but this

Hi, Does the mailing list support plaintext attachments? Cheers, Tom

Hi Laszlo, Unfortunately I do not have access to the platform firmware itself (I maintain an IHV network driver that's shipped in OptionROMs) and I don't believe a generic stack capture is available i