From: "Eric Jin" <eric.jin@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"jabirm@gmail.com" <jabirm@gmail.com>,
Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>,
"Jin, Eric" <eric.jin@intel.com>
Subject: [edk2-devel] Missing protocols in IHV SCT compared to generic SCT
Date: Tue, 30 Apr 2019 02:21:04 +0000 [thread overview]
Message-ID: <DA72DC7456565B47808A57108259571F6379740F@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <CAPJUX+pmTJkCs9AiYT8SGqymbVggZg4WcxL1_rDgeCMEifN22g@mail.gmail.com>
[-- 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 --]
next prev parent reply other threads:[~2019-04-30 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` Eric Jin [this message]
2019-05-06 5:13 ` [edk2-devel] " jabir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DA72DC7456565B47808A57108259571F6379740F@SHSMSX103.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox