[Bug 3145] UEFI-SCT: handling of unsupported EFI_SIMPLE_NETWORK_PROTOCOL.ReceiveFilters()


bugzilla-daemon@...
 

https://bugzilla.tianocore.org/show_bug.cgi?id=3145

--- Comment #4 from Sunny Wang <Sunny.Wang@arm.com> ---
Hi Heinrich,

"this function is not supported by the network interface" may not mean that SCT
should allow the function to return EFI_UNSUPPORTED.

SNP.Start, SNP.Stop, and other SNP functions also have "this function is not
supported by the network interface" in its sections in the UEFI spec, but I
think some of them are required for UEFI network boot (like PXE, HTTP boot) or
other functionality that is required during boot, so it looks like we should
not allow the firmware to return EFI_UNSUPPORTED for them.

Or do you see any description saying a specific SNP function or the whole SNP
is optional in the UEFI spec? I couldn't find it by roughly checking the spec.
If you can't find it either, it looks like making sense to show failure for the
SNP.ReceiveFilters that returns EFI_UNSUPPORTED and we may need to revert
commit 3d98de052fcd for consistency.

If we want to allow EFI_SIMPLE_NETWORK_PROTOCOL.ReceiveFilters() to return
EFI_UNSUPPORTED, we may need to update the UEFI specification. For the SCT
users, they can use the sequence file (.seq) to skip testing specific functions
if they think the function is not needed (fine to return EFI_UNSUPPORTED).


Best Regards,
Sunny

--
You are receiving this mail because:
You are on the CC list for the bug.