Hi, What SCT v1.3 states for HII Config Access Protocol seems not in align with UEFI spec? For example, for extract config, when Progress or Result or Request is NULL, SCT is expecting EFI Invalid Parameter; similarly for Route Config, when progress is NULL, SCT expects EFI_INVALID_PARAMETER. UEFI spec doesn’t seem mention anything for these cases.
Should driver adhere to what SCT expects? Or is this fixed in newer SCT or will this be addressed in future? Please advise! Thanks, Daniel _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
