Re: [edk2-devel] iSCSI and iBFT

["Tomas Pilar (tpilar)" <tpilar@solarflare.com>]

I was mostly puzzled by the double step. First find a parent device to LoadedImage that support NII. Rather than using that device we will scan all devices to see if any of them has the same NII protocol and if so we use that one. I am not sure there is any advantage compared to just using the original parent device?

In either way, the device path search using NII is fairly ingenious!

On 22/05/2019 23:26, Michael Brown wrote:
> On 22/05/2019 11:40, Tomas Pilar (tpilar) wrote:
>> Yeah, I just AllocateCopyPool the static struct on heap for each device. I can honestly see how one would assume that a protocol instance would never be installed on more than one handle, same as I assumed that using a statically allocated struct containing nothing but boilerplate info would also be fine.
>>
>> The whole NII and UNDI drivers vs. SNP drivers compatibility across OEMs/IBVs and IHVs is a painful trash fire and this is just the last problem in a very long line of annoyances. </rant>
>
> Thanks for writing up the end result.  I can't immediately see any more viable way for iPXE to determine the NII corresponding to the user's concept of "the NIC from which I booted", but I'm open to suggestions.
>
> Thanks again,
>
> Michael
>
> 
>