* Missing protocols in IHV SCT compared to generic SCT [not found] <CAPJUX+paPrD_fsXsbpoUZUcNN2ePA_5H6JvAh4xNOUXPKBKRXw@mail.gmail.com> @ 2019-04-25 5:34 ` jabirm 2019-04-30 2:21 ` [edk2-devel] " Eric Jin 0 siblings, 1 reply; 3+ messages in thread From: jabirm @ 2019-04-25 5:34 UTC (permalink / raw) To: devel [-- Attachment #1: Type: text/plain, Size: 351 bytes --] 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 [-- Attachment #2: Type: text/html, Size: 591 bytes --] ^ permalink raw reply [flat|nested] 3+ messages in thread
* [edk2-devel] Missing protocols in IHV SCT compared to generic SCT 2019-04-25 5:34 ` Missing protocols in IHV SCT compared to generic SCT jabirm @ 2019-04-30 2:21 ` Eric Jin 2019-05-06 5:13 ` jabir 0 siblings, 1 reply; 3+ messages in thread From: Eric Jin @ 2019-04-30 2:21 UTC (permalink / raw) To: devel@edk2.groups.io, jabirm@gmail.com, Supreeth Venkatesh, Jin, Eric [-- Attachment #1: Type: text/plain, Size: 1126 bytes --] 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 [-- Attachment #2: Type: text/html, Size: 4504 bytes --] ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [edk2-devel] Missing protocols in IHV SCT compared to generic SCT 2019-04-30 2:21 ` [edk2-devel] " Eric Jin @ 2019-05-06 5:13 ` jabir 0 siblings, 0 replies; 3+ messages in thread From: jabir @ 2019-05-06 5:13 UTC (permalink / raw) To: Eric Jin, devel [-- Attachment #1: Type: text/plain, Size: 69 bytes --] Thank You Eric, We will work on patch submission. Regards Jabir [-- Attachment #2: Type: text/html, Size: 81 bytes --] ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-05-06 5:13 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CAPJUX+paPrD_fsXsbpoUZUcNN2ePA_5H6JvAh4xNOUXPKBKRXw@mail.gmail.com>
2019-04-25 5:34 ` Missing protocols in IHV SCT compared to generic SCT jabirm
2019-04-30 2:21 ` [edk2-devel] " Eric Jin
2019-05-06 5:13 ` jabir
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox