Changing subject line to include [edk2-test]

+ Supreeth

Hi Jabir,

In history, after the EFI_HII_CONFIG_ACCESS_PROTOCOL, EFI_FIRMWARE_MANAGEMENT_PROTOCOL defined in UEFI Spec, the test is developed and validated with the fake driver or contributed by UEFI member, but the true device is not seen in market.

To answer your question - The porting work from generic SCT to IHV is easy and I think there is no limitation/issue to enable them for IHV SCT. Do you have bandwidth to enable the two tests mentioned by you?

Best Regards

Eric

From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of jabir
Sent: Thursday, April 25, 2019 1:34 PM
To: devel@edk2.groups.io
Subject: [edk2-devel] Missing protocols in IHV SCT compared to generic SCT

Hi,

There are few applicable protocols which are missing for selection in IHV SCT e.g. EFI_HII_CONFIG_ACCESS_PROTOCOL, EFI_FIRMWARE_MANAGEMENT_PROTOCOL when compared to generic SCT. 

These protocols can be ported to IHV SCT..

Can anybody help me to understand if there is any limitation/issues for enabling these protocols for IHV SCT? 

Thanks,

Jabir