It lists all boot options referenced by BootOrder variable.
We will create a feature equivalent UI/Firmware Setup later.
-Original Message-
From: Justen, Jordan L
Sent: Monday, May 11, 2015 2:07 PM
To: Ni, Ruiyu; edk2-devel@lists.sourceforge.net
Subject: RE: [edk2] [Patch] Nt32Pkg: Enable
On 2015-05-09 21:18:40, Ni, Ruiyu wrote:
> From BDS side, there is no feature gap.
> From the UI/Firmware Setup side, the standalone UI/Firmware Setup
> (provided by MdeModulePkg/Application/BootManagerMenuApp) only lists
> all boot options.
Do you mean it lists all boot options in boot variables
On 11 May 2015 at 07:54, Zhang, Chao B wrote:
> Ard:
>Is this check-log OK for you.
> SecurityPkg: Update SecureBootConfigDxe to support ARM image
>
> Update SecureBootConfigDxe component to allow the enrollment of
> the digests of EFI executable that are built for ARM or AARCH6
Ard:
Is this check-log OK for you.
SecurityPkg: Update SecureBootConfigDxe to support ARM image
Update SecureBootConfigDxe component to allow the enrollment of
the digests of EFI executable that are built for ARM or AARCH64.
Contributed-under: TianoCore Contribution A
On 11 May 2015 at 03:21, Zhang, Chao B wrote:
> Ard :
> It looks good to me.
> Reviewed-by: Chao Zhang
>
Thank you Chao!
Would you mind committing it yourself? This is not part of a series,
and I don't have permissions.
Regards,
Ard.
>
>
>
>
> Thanks & Best regards
> Chao Zhang
>
>
> ---
Please don't top post.
On Mon, May 11, 2015 at 01:52:38AM +, lidonglin wrote:
> Hi all:
> Did you encounter this BSOD problem ? I try
> git://xenbits.xen.org/ovmf.git and other ovmf repos. I found
> installing win8 64bit os (memory > 4G) with OVMF on xen
> hypervisor al
2) Nasm build rules have been used for the other tool chain and platform. And,
we also agree to use nasm in EDKII. I don't think we can drop it now in the
default configuration.
3) I don't see those flags in build_rule.txt. I am curious how use them in
CLANG build.
Thanks
Liming
From: Chiu, Cha
Reviewed-by: Eric Dong
-Original Message-
From: Ruiyu Ni [mailto:ruiyu...@intel.com]
Sent: Monday, May 11, 2015 10:45 AM
To: edk2-devel@lists.sourceforge.net
Subject: [edk2] [Patch V2 0/2] Enable new BDS in Nt32 platform
This version of patches separate the PlatformBootManagerLib from t
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ruiyu Ni
CC: Eric Dong
---
Nt32Pkg/Nt32Pkg.dsc | 13 +++--
Nt32Pkg/Nt32Pkg.fdf | 8 +++-
2 files changed, 18 insertions(+), 3 deletions(-)
diff --git a/Nt32Pkg/Nt32Pkg.dsc b/Nt32Pkg/Nt32Pkg.dsc
index 1b7d329..b0
This library will co-work with UefiBootManagerLib and BdsDxe driver in
MdeModulePkg.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ruiyu Ni
CC: Eric Dong
---
Nt32Pkg/Library/PlatformBootManagerLib/PlatformBootManager.c | 220
Nt32Pkg/Library/
This version of patches separate the PlatformBootManagerLib from the DSC/FDF
change.
Ruiyu Ni (2):
Nt32Pkg: Add PlatformBootManagerLib to Nt32 platform.
Nt32Pkg: Enable new BDS in NT32 platform.
Nt32Pkg/Library/PlatformBootManagerLib/PlatformBootManager.c | 220
N
Chao:
I have some comments.
1) Seemly, EsrtVariable for FMP and NON-FMP ESRT Repository are interface. How
about define them into Guid header file in MdeModulePkg\Include\Guid directory.
2) EsrtImpl.h should include
3) Module UNI and Extra UNI file is missing.
4) Module description in INF fil
Chao:
I have some comments.
1) ESRT_MANAGEMENT protocol is EDKII implemented protocol, not UEFI/PI
protocol. We can't use EFI_ prefix for its definition. Please remove it.
2) Most APIs of ESRT_MANAGEMENT protocol have no return value description in
their function header. Please add them.
3) De
Hi all:
Did you encounter this BSOD problem ? I try
git://xenbits.xen.org/ovmf.git and other ovmf repos. I found installing win8
64bit os (memory > 4G) with OVMF on xen hypervisor always failed with BSOD. I
also tried to do some thing on kvm, there is no this problem.
I don't what's the
Ard :
It looks good to me.
Reviewed-by: Chao Zhang
Thanks & Best regards
Chao Zhang
-Original Message-
From: Ard Biesheuvel [mailto:ard.biesheu...@linaro.org]
Sent: Saturday, May 09, 2015 1:17 AM
To: Zhang, Chao B; edk2-devel@lists.sourceforge.net
Cc: ler...@redhat.com; roy.fr.
Patch looks good to me.
Reviewed-by: Yingke Liu
Dennis
From: Feng, Bob C
Sent: Thursday, May 07, 2015 5:15 PM
To: 'edk2-devel@lists.sourceforge.net'
Cc: ard.biesheu...@linaro.org; ard.biesheu...@linaro.org; Liu, Yingke D
Subject: [edk2] [patch] BaseTool : The PCD value in uninitialized data rang
> On May 10, 2015, at 4:20 PM, Andreas Galauner wrote:
>
> On 10.05.2015 15:32, Cohen, Eugene wrote:
>> I apologize since this was probably not the answer you were looking for.
>
> No worries, it's kind of what I expected. Hence the question about the
> virtual bus.
> What I didn't understand w
On 10.05.2015 15:32, Cohen, Eugene wrote:
> I apologize since this was probably not the answer you were looking for.
No worries, it's kind of what I expected. Hence the question about the
virtual bus.
What I didn't understand was the Driver Binding protocol just by looking
at the source. I guess I
> On May 9, 2015, at 10:30 PM, Jordan Justen wrote:
>
> On 2015-05-09 13:15:42, Ard Biesheuvel wrote:
>> According to the UEFIv2.5 spec section 6.2, the allocations returned
>> by the AllocatePool () boot service must be 8 byte aligned.
>>
>> So make our implementation conform to the spec, by r
Andy,
DXE drivers are not sufficient for this use case - this is what UEFI Driver
Binding is for. This has been an outstanding issue for ARM for a few years
now. We need to define a bus protocol like PCI_IO that handles memory-mapped
SoC peripherals like the two SDIO controllers. With a bus
20 matches
Mail list logo
