Update the tools_def.template to add NOOPT support with GCC tool chains.
Cc: Liming Gao
Cc: Laszlo Ersek
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Yonghong Zhu
---
BaseTools/Conf/tools_def.template |
Ersek:
I try O2 option. Compared to Ofast, there is a little different. I think it
is acceptable. I will use O2 option. And, this warning message also exists
without O2 enable. It is not introduced by this patch.
Tool Compression time
From: Ruiyu Ni
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Chen A Chen
Cc: Jaben Carsey
Cc: Ruiyu Ni
---
ShellPkg/Library/UefiShellLevel3CommandsLib/Alias.c | 1 -
From: Ruiyu Ni
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Chen A Chen
Cc: Jaben Carsey
Cc: Ruiyu Ni
---
.../Library/UefiShellBcfgCommandLib/UefiShellBcfgCommandLib.c| 9
From: Ruiyu Ni
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Chen A Chen
Cc: Jaben Carsey
Cc: Ruiyu Ni
---
ShellPkg/Application/Shell/ConsoleLogger.c | 10 --
From: Ruiyu Ni
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Chen A Chen
Cc: Jaben Carsey
Cc: Ruiyu Ni
---
ShellPkg/Library/UefiShellLevel2CommandsLib/Cp.c | 4
From: Ruiyu Ni
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Chen A Chen
Cc: Jaben Carsey
Cc: Ruiyu Ni
---
ShellPkg/Library/UefiShellNetwork1CommandsLib/Ping.c | 14 --
From: Ruiyu Ni
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Chen A Chen
Cc: Jaben Carsey
Cc: Ruiyu Ni
---
ShellPkg/Library/UefiShellLib/UefiShellLib.c | 14 --
From: Ruiyu Ni
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Chen A Chen
Cc: Jaben Carsey
Cc: Ruiyu Ni
---
ShellPkg/Library/UefiShellLevel1CommandsLib/For.c | 5
On 09/30/16 08:56, Gao, Liming wrote:
> Ersek:
>
> I try O2 option. Compared to Ofast, there is a little different. I
> think it is acceptable. I will use O2 option. And, this warning message
> also exists without O2 enable. It is not introduced by this patch.
>
>
>
> Tool
Bruce,
On 09/30/16 09:44, Yonghong Zhu wrote:
> Update the tools_def.template to add NOOPT support with GCC tool chains.
>
> Cc: Liming Gao
> Cc: Laszlo Ersek
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Yonghong Zhu
Many Shell internal functions have EFIAPI modifier.
But it's not necessary. The patch serials remove the unnecessary
EFIAPI.
Ruiyu Ni (11):
ShellPkg/Shell: Remove unnecessary EFIAPI
ShellPkg/UefiShellDebug1CommandsLib: Remove unnecessary EFIAPI
ShellPkg/UefiShellDriver1CommandsLib: Remove
From: Ruiyu Ni
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Chen A Chen
Cc: Jaben Carsey
Cc: Ruiyu Ni
---
ShellPkg/Library/UefiHandleParsingLib/UefiHandleParsingLib.c | 6 --
From: Ruiyu Ni
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Chen A Chen
Cc: Jaben Carsey
Cc: Ruiyu Ni
---
ShellPkg/Library/UefiShellCommandLib/ConsistMapping.c | 3 ---
This library is used to authenticate a UEFI defined FMP Capsule.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
Contributed-under: TianoCore
This CapsuleApp can help perform capsule update in UEFI shell environment.
It can also dump capsule information, capsule status variable, ESRT and FMP.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
This library is used to authenticate a UEFI defined FMP Capsule.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
Contributed-under: TianoCore
==Below is V2 description==
The V2 series patch incorporated the feedback for V1.
There are 3 major updates.
1) BDS is update to display a warning message if TEST key
is used to sign recovery image or capsule image.
So a production BIOS should always use its own production singing
key for the
This library is used to parse the INI configuration file.
The INI configuration file is used in EDKII capsule image to describe
the capsule information.
Detail format is documented in header file.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Add EDKII system FMP capsule header file.
This describes the EDKII system FMP capsule format.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
This library is used to abstract the action for EDKII system FMP capsule,
such as extracting a component from capsule, or authenticate the capsule.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
1) Add capsule related GUID.
EdkiiSystemFmpCapsule
2) Add capsule related library.
EdkiiSystemCapsuleLib
FmpAuthenticationLib
IniParsingLib
PlatformFlashAccessLib.c
3) Add capsule related status code PCD.
PcdStatusCodeSubClassCapsule
PcdCapsuleStatusCodeProcessCapsulesBegin
ProcessCapsules() API can be used by platform BDS to process all capsules.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
Contributed-under:
Hi,
I have been using EFI_IP4_CONFIG2_PROTOCOL, setdata function for setting
the policy as* Ip4Config2PolicyDhcp*, to start the Auto configuration. Now
by default the instance Policy is set as *Ip4Config2PolicyStatic, * during
Initialization of the instance( in Ip4Config2Impl.c). Now when I am
Add SystemFirmwareDescriptor for capsule update.
The PEIM extracts SystemFirmwareDescriptor info from FFS and reports it via PCD.
Cc: David Wei
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc:
Add SystemFirmwareUpdateConfig as capsule configuration file.
Cc: David Wei
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
Add capsule and recovery support module in platform dsc and fdf.
Cc: David Wei
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
Previous FlashDeviceLib only supports DxeRuntime and Smm.
It cannot be linked with SystemBiosUpdateDxe driver.
So we separate DxeRuntime related code into a standalone file,
and create FlashDeviceLibDxe.inf.
Cc: David Wei
Cc: Feng Tian
Cc: Star Zeng
Add PlatformFlashAccessLib for capsule update.
Cc: David Wei
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
Add capsule and recovery boot path handling in platform BDS.
Add check if the platform is using default test key for recovery or update.
Cc: David Wei
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: David Wei
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
Contributed-under: TianoCore Contribution Agreement 1.0
Add DSC/FDF to generate capsule image.
It is separated from normal DSC/FDF, because the FDF file need use
the result of final build.
Cc: David Wei
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc:
If OPENSSL_PATH is set, the build process generates capsule.
Cc: David Wei
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
Hi
Here is V2 serial.
I forgot to mention:
1) This series is also pushed to g...@github.com:jyao1/edk2.git.
2) Below is test I did for IniParsingLib.
2.1) Unit test:
{ EFI_SUCCESS, "[a]\nb=c\n" },
{ EFI_SUCCESS, "[_]\n_=0\n" },
{ EFI_SUCCESS,
Add capsule related component to check build.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
Contributed-under: TianoCore Contribution Agreement
This library is used to abstract the action for EDKII system FMP capsule,
such as extracting a component from capsule, or authenticate the capsule.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
SystemFirmwareUpdate supports update system firmware via UEFI FMP capsule.
SystemFirmwareReportDxe.inf can be included in system BIOS. It is a lightweight
FMP protocol implementation and it only reports FMP information, so that
ESRT table can report the system firmware information. It does not
Add ProcessCapsules() interface for DxeCapsuleLibNull.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
Contributed-under: TianoCore Contribution
This instance handles Microsoft UX capsule, UEFI defined device FMP capsule,
and EDKII system FMP capsule.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
This is a NULL class for FmpAuthenticationLib. It provides PKCS7 based
FMP authentication.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
This library is used to abstract microcode flash region access.
This library is consumed by a microcode capsule update module.
Cc: Jeff Fan
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
MicrocodeUpdate supports update Microcode region via UEFI FMP capsule.
MicrocodeUpdate SetImage() will perform the Microcode version,
ProcessorSignature/ProcessorFlag, and try to load microcode.
If and only if the Microcode is loaded successfully, and new Microcode
will be updated to system flash
Add NULL instance to pass build.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
Contributed-under: TianoCore Contribution Agreement 1.0
RecoveryModuleLoadPei supports recovery system firmware via UEFI FMP capsule.
RecoveryModuleLoadPei produces EFI_PEI_RECOVERY_MODULE_PPI. It is invoked
by DxeIpl in recovery boot mode.
LoadRecoveryCapsule() will scan all possible
gEfiPeiDeviceRecoveryModulePpiGuid and get EDKII system FMP
This library is used to parse the INI configuration file.
The INI configuration file is used in EDKII capsule image to describe
the capsule information.
Detail format is documented in header file.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
This is a NULL class for FmpAuthenticationLib. It provides Rsa2048Sha256
based FMP authentication.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
The previous ESRT driver unconditionally treat FMP to be
ESRT_FW_TYPE_DEVICEFIRMWARE.
EDKII System Capsule reuses FMP, but it is ESRT_FW_TYPE_SYSTEMFIRMWARE.
Add check to ImageTypeId check to see if it is ESRT_FW_TYPE_SYSTEMFIRMWARE.
Cc: Feng Tian
Cc: Star Zeng
We add this binary data file for TestRoot.cer.
So that a platform may include this default file in FDF,
to check if the platform is using default test key,
or different production key.
Cc: Yonghong Zhu
Cc: Liming Gao
Cc: Michael D Kinney
Add NULL ProcessCapsules() interface for DxeCapsuleLib.
IntelFrameworkModulePkg is under maintenance phase.
We stop adding new feature there.
Just add NULL function to make it pass build.
Cc: Jeff Fan
Cc: Feng Tian
Cc: Star Zeng
Cc:
This library is used to abstract platform flash access.
This library is consumed by a capsule update module.
It may cover SystemFirmware region and/or non-SystemFirmware region.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
This PCD is similar to PcdRsa2048Sha256PublicKeyBuffer.
It provides trusted cert for PKCS7 verification.
It can be used for Recovery and Capsule Update images.
We added warning message for both PcdPkcs7CertBuffer and
PcdRsa2048Sha256PublicKeyBuffer. The default value is only for
test purpose.
1) Add Microcode capsule related GUID.
gMicrocodeFmpImageTypeIdGuid
2) Add Microcode capsule related library.
MicrocodeFlashAccessLib
Cc: Jeff Fan
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Add NULL instance to pass build.
Cc: Jeff Fan
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
Contributed-under: TianoCore
It defined ImageTypeId for Microcode.
Cc: Jeff Fan
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
Contributed-under:
Add FmpAuthentication*Lib to check build.
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
Contributed-under: TianoCore Contribution Agreement 1.0
Add Microcode capsule related component to check build.
Cc: Jeff Fan
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Cc: Chao Zhang
We will add PKCS7 and RSA2048SHA256 test key file to FDF,
to check if the platform is using default test key,
or different production key.
Cc: Michael D Kinney
Cc: Kelly Steele
Cc: Feng Tian
Cc: Star Zeng
This MicrocodeCapsuleApp can help generate Microcode FMP capsule.
It can also dump Microcode capsule information.
Cc: Jeff Fan
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Cc: Liming Gao
Add DSC/FDF to generate capsule image.
It is separated from normal DSC/FDF, because the FDF file need use
the result of final build.
Cc: Michael D Kinney
Cc: Kelly Steele
Cc: Feng Tian
Cc: Star Zeng
Add SystemFirmwareUpdateConfig as capsule configuration file.
Cc: Michael D Kinney
Cc: Kelly Steele
Cc: Feng Tian
Cc: Star Zeng
Cc: Liming Gao
Cc: Chao Zhang
Add capsule and recovery boot path handling in platform BDS.
Add check if the platform is using default test key for recovery or update.
Cc: Michael D Kinney
Cc: Kelly Steele
Cc: Feng Tian
Cc: Star Zeng
Add SystemFirmwareDescriptor for capsule update.
The PEIM extracts SystemFirmwareDescriptor info from FFS and reports it via PCD.
Cc: Michael D Kinney
Cc: Kelly Steele
Cc: Feng Tian
Cc: Star Zeng
Cc:
Cc: Michael D Kinney
Cc: Kelly Steele
Cc: Feng Tian
Cc: Star Zeng
Cc: Liming Gao
Cc: Chao Zhang
Contributed-under: TianoCore Contribution Agreement 1.0
Add capsule and recovery support module in platform dsc and fdf.
Cc: Michael D Kinney
Cc: Kelly Steele
Cc: Feng Tian
Cc: Star Zeng
Cc: Liming Gao
Cc: Chao Zhang
The QuarkPlatform will use MdeModulePkg/RecoveryModuleLoadPei for recovery.
There is no need to produce recovery PPI in platform module.
Cc: Michael D Kinney
Cc: Kelly Steele
Cc: Feng Tian
Cc: Star Zeng
We will add PKCS7 and RSA2048SHA256 test key file to FDF,
to check if the platform is using default test key,
or different production key.
Cc: David Wei
Cc: Feng Tian
Cc: Star Zeng
Cc: Michael D Kinney
Eugene --
Since SMM drivers today are actually DXE drivers during the initialization
phase, are you going to (a) have your library check InSmm? or (b) only work
with pure SMM stand-alone drivers?
Thanks,
Tim
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org]
Just remove confusion.
Thanks,
Ray
> 在 2016年9月30日,下午11:13,Carsey, Jaben 写道:
>
> I have no objection.
>
> Can you explain the benefit or just remove confusion?
>
> Reviewed-by: Jaben Carsey
>
>> -Original Message-
>> From: edk2-devel
On 09/30/16 18:36, Cohen, Eugene wrote:
> Laszlo,
>
>> As far as I know:
>> - the DXE and SMM protocol databases are distinct,
>> - the same protocol GUID may or may not be installed (on one or more)
>> handle(s) in either,
>> - even if a protocol GUID exists uniquely in exactly one of those
Tim,
My focus at the moment is on standalone SMM drivers, but in order to support
the dual-mode DXE_SMM_DRIVER modules we could have another instance that does
the InSmm check at runtime.
Eugene
> -Original Message-
> From: Tim Lewis [mailto:tim.le...@insyde.com]
> Sent: Friday,
On 2016-09-29 07:12:43, Liming Gao wrote:
> After enable optimization, C tool build time is reduced by ~50%. Please see
> below example to use LzmaCompress to compress OVMF DXEFV.
>
> Tool Compression time Decompression time
> LzmaCompress (GCC O0)3.476s
Updated IgdOpregion.h to align with latest specification
https://01.org/sites/default/files/documentation/skl_opregion_rev0p5.pdf
1) Updated Mailbox structures to align with latest spec
2) Added Mailbox 5 structure
3) Added defines for Signature and Mailbox support
Cc: Jiewen Yao
Eugene --
Since the standalone file type isn't yet in the EDK2 code, the build system
will not be able to make this distinction in the library's INF file.
Tim
-Original Message-
From: Cohen, Eugene [mailto:eug...@hp.com]
Sent: Friday, September 30, 2016 9:51 AM
To: Tim Lewis
Tim,
Agreed - When BaseTools gets the standalone support I expect us to be able to
differentiate library instances.
I wanted to gather feedback now while we prototype on a branch.
Eugene
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf
> Of
Laszlo,
> As far as I know:
> - the DXE and SMM protocol databases are distinct,
> - the same protocol GUID may or may not be installed (on one or more)
> handle(s) in either,
> - even if a protocol GUID exists uniquely in exactly one of those databases,
> the locator function would have to
> I believe I understood this. However, in the entry point function of an
> SMM driver, it is permitted to look for, and invoke member functions
> of,
> both SMM and DXE protocols [1]. If the library instance that is
> supposed
> to be linked into SMM drivers is tied to the SMM protocol database
>
Mike Rothman,
Can we get LoadOptions and LoadOptionsSize clarified in the UEFI Spec? This
seems like a simple clarification and I would argue its needed. The UEFI Shell
is not the only producer of this protocol. BDS launches things (like the UEFI
Shell itself) and the shell already consumes
Request for Comments...
Both UEFI/DXE and SMM support the protocol / handle database concept. Some
protocol definitions are able used in both environments with different
implementations behind them.
We'd like to create a library that could be used in either DXE or SMM making
use of protocol
On 09/30/16 16:13, Cohen, Eugene wrote:
> Request for Comments...
>
> Both UEFI/DXE and SMM support the protocol / handle database concept.
> Some protocol definitions are able used in both environments with
> different implementations behind them.
>
> We'd like to create a library that could be
I have no objection.
Can you explain the benefit or just remove confusion?
Reviewed-by: Jaben Carsey
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> Ruiyu Ni
> Sent: Friday, September 30, 2016 1:18 AM
> To:
80 matches
Mail list logo