Re: [edk2] Cross compiling EDK2 for Aarch64

Hi Yehuda, On Thu, Oct 08, 2015 at 08:24:07AM +, Yehuda Yitschak wrote: > I am new to the EDK2 projects and for starters I am trying to cross > compile the project for aarch64 on an x86_64 host > > I looked around in Linaro website and Tiano-core website but > couldn't find any instruction

[edk2] [PATCH] MdeModulePkg PiDxeS3BootScriptLib: Use PcdSet64S to instead of PcdSet64

PcdSet## has no error status returned, then the caller has no idea about whether the set operation is successful or not. PcdSet##S were added to return error status and PcdSet## APIs were put in ifndef DISABLE_NEW_DEPRECATED_INTERFACES condition. To adopt PcdSet##S and further code development

Re: [edk2] [PATCH] MdeModulePkg PiDxeS3BootScriptLib: Use PcdSet64S to instead of PcdSet64

Looks good. -Original Message- From: Zeng, Star Sent: Thursday, October 08, 2015 3:40 PM To: edk2-devel@lists.01.org Cc: Yao, Jiewen; Gao, Liming Subject: [PATCH] MdeModulePkg PiDxeS3BootScriptLib: Use PcdSet64S to instead of PcdSet64 PcdSet## has no error status returned, then the

[edk2] Cross compiling EDK2 for Aarch64

Hello everyone I am new to the EDK2 projects and for starters I am trying to cross compile the project for aarch64 on an x86_64 host I looked around in Linaro website and Tiano-core website but couldn't find any instruction on how to _cross_ compile I tried to follow the instruction here:

Re: [edk2] [PATCH 7/7] UefiCpuPkg: Add missing UefiCpuPkgTokenSpace include

On 10/07/15 23:11, Kinney, Michael D wrote: > Laszlo, > > Good question. > > It is a good practice to have the .h file for each GUID. The .h file > contains the extern for the global variable associated with the GUID along > with data structures associated with the GUID. > > For PCD token

Re: [edk2] Cross compiling EDK2 for Aarch64

On Thu, Oct 08, 2015 at 10:04:24AM +, Yehuda Yitschak wrote: > > > but when I try to compile using the "build" command the build script > > > uses the x86 compiler and naturally it fails > > > > Any particular reason why you skipped past the first half of the page to > > follow the

Re: [edk2] [PATCH v3] Pkg-Module: Integrate new RngLib into RngDxe

LONG, Qin, Do you know if the 10uS delay required in RdRandGetSeed128()? Thanks, Mike >-Original Message- >From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Long, >Qin >Sent: Wednesday, October 07, 2015 8:44 PM >To: Justen, Jordan L; Thomas Palmer;

Re: [edk2] Support for UBI volumes and UBIFS?

Hi Feng, I have an embedded Linux system that currently uses eMMC storage and I am looking at modifying it to use a simple raw NAND-Flash controller instead. The current system stores BIOS in the eMMC boot-partition. The eMMC user-partition has a GPT with partitions defined for EFI (Fat32),

Re: [edk2] [PATCH 7/7] UefiCpuPkg: Add missing UefiCpuPkgTokenSpace include

> On Oct 8, 2015, at 4:22 AM, Laszlo Ersek wrote: > > On 10/07/15 23:11, Kinney, Michael D wrote: >> Laszlo, >> >> Good question. >> >> It is a good practice to have the .h file for each GUID. The .h file >> contains the extern for the global variable associated with

Re: [edk2] [PATCH v3 3/5] ArmPkg/ArmLib MMU: add functions to set/clear RO and XN bits on regions

On Tue, Oct 06, 2015 at 01:48:19PM +0100, Ard Biesheuvel wrote: > Use the refactored UpdateRegionMapping () to traverse the translation > tables, splitting block entries along the way if required, and apply > a mask + or on each to set or clear the PXN/UXN/XN or RO bits. > > For now, the 32-bit

Re: [edk2] [PATCH 7/7] UefiCpuPkg: Add missing UefiCpuPkgTokenSpace include

Andrew, Yes. The use of the Ex forms of the PCD Protocol/PPI APIs are required when modules are built separately. The Ex forms of the PCD Protocol/PPI APIs are used even if the module source does not use the Ex APIs from the PcdLib if the PCDs are listed in a DynamicEx section of a DSC file.

[edk2] [PATCH 1/3] MdePkg: Create GetRandomNumber128 in RngLib

Declare GetRandomNumber128 in RngLib.h. Create GetRandomNumber128 in BaseRngLib, which is simply calling GetRandomNumber64 twice A GetRandomNumber128 function allows platforms with 128bit HWRNGs to save on IO overhead that comes from having to prime the HWRNG device before each read operation.

[edk2] [PATCH 2/3] SecurityPkg: Integrate new RngLib into RngDxe

Use the new RngLib to provide the IA32/X64 random data for RngDxe. Remove x86 specific functions from RdRand files. Simplify RngDxe by using WriteUnaligned64 for all platforms. Use GetRandomNumber128 in RngDxe to leverage 128 bit support provided by some HW RNG devices Contributed-under:

Re: [edk2] Cross compiling EDK2 for Aarch64

On 10/08/15 10:24, Yehuda Yitschak wrote: > Hello everyone > > I am new to the EDK2 projects and for starters I am trying to cross compile > the project for aarch64 on an x86_64 host > > I looked around in Linaro website and Tiano-core website but couldn't find > any instruction on how to

Re: [edk2] Cross compiling EDK2 for Aarch64

Obviously I forgot one command (because it need not be reissued every time): On 10/08/15 21:17, Laszlo Ersek wrote: > On 10/08/15 10:24, Yehuda Yitschak wrote: >> Hello everyone >> >> I am new to the EDK2 projects and for starters I am trying to cross compile >> the project for aarch64 on an

Re: [edk2] [PATCH] BaseTools/Scripts: Add PatchCheck.py script

On 10/08/15 04:53, Jordan Justen wrote: > This script can be used to check some expected rules for EDK II > patches. It only works on git formatted patches. > > It checks both the commit message and the lines that are added in the > patch diff. > > In the commit message it verifies line lengths,

Re: [edk2] [PATCH] MdeModulePkg PiDxeS3BootScriptLib: Use PcdSet64S to instead of PcdSet64

> On Oct 8, 2015, at 3:11 PM, Laszlo Ersek wrote: > > On 10/08/15 09:39, Star Zeng wrote: >> PcdSet## has no error status returned, then the caller has no idea about >> whether the set operation is successful or not. >> PcdSet##S were added to return error status and

Re: [edk2] [PATCH] MdeModulePkg PiDxeS3BootScriptLib: Use PcdSet64S to instead of PcdSet64

On 10/08/15 09:39, Star Zeng wrote: > PcdSet## has no error status returned, then the caller has no idea about > whether the set operation is successful or not. > PcdSet##S were added to return error status and PcdSet## APIs were put in > ifndef DISABLE_NEW_DEPRECATED_INTERFACES condition. > To

Re: [edk2] Driver Health Protocol, UI interaction and Intel DQ77MK vs. OVMF

On 10/8/15 9:04 PM, Ni, Ruiyu wrote: OVMF used the old IntelFrameworkModulePkg/BDS. The new MdeModulePkg/BDS automatically invokes the reparation upon boot. I did a draft patch (http://article.gmane.org/gmane.comp.bios.edk2.devel/759) but do not have time to edit it to follow the review

Re: [edk2] [PATCH 6/7] UefiCpiPkg: Add PiSmmCpuDxeSmm module

On 10/08/15 23:22, Kinney, Michael D wrote: > Hi Laszlo, > > A couple responses below. Thanks much (again!); I think I can rework CpuS3DataDxe based on your advice: > > Mike > >> -Original Message- >> From: Laszlo Ersek [mailto:ler...@redhat.com] >> Sent: Thursday, October 08, 2015

Re: [edk2] [PATCH] MdeModulePkg PiDxeS3BootScriptLib: Use PcdSet64S to instead of PcdSet64

On 2015/10/9 6:33, Andrew Fish wrote: On Oct 8, 2015, at 3:11 PM, Laszlo Ersek wrote: On 10/08/15 09:39, Star Zeng wrote: PcdSet## has no error status returned, then the caller has no idea about whether the set operation is successful or not. PcdSet##S were added to

Re: [edk2] [PATCH 08/58] OvmfPkg: PlatformPei: account for TSEG size with PcdSmmSmramRequire set

Hi Jordan, On 09/07/15 02:27, Jordan Justen wrote: > Patches 7 & 8 Reviewed-by: Jordan Justen Thanks! I addressed the comments I received thus far (I'm just not posting v2 yet). Ultimately I'll rebase this series to Mike's new, central PiSmmCpuDxeSmm module (see it

Re: [edk2] [PATCH v2 00/16] unify GCC command line options

Of all the gin joints in all the towns in all the world, Bill Paul had to walk into mine at 10:30:26 on Monday 24 August 2015 and say: > Of all the gin joints in all the towns in all the world, Ard Biesheuvel had > to > > walk into mine at 10:22:59 on Monday 24 August 2015 and say: > > On 24