This driver links to PciHostBridgeLib provided by platform/silicon to
produce PciRootBridgeIo and PciHostBridgeResourceAllocation protocol.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ruiyu Ni
Cc: Jeff Fan
Cc: Feng Tian
PciHostBridgeDxe driver needs PciHostBridgeLib implemented by platform
to provide the root bridge related information and may call into
PciHostBridgeLib when resource conflicts happen.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ruiyu Ni
Cc: Feng
This PciSegmentLib instance only supports Segment 0 access.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ruiyu Ni
Cc: Michael D Kinney
Cc: Liming Gao
---
On 13 January 2016 at 11:18, Laszlo Ersek wrote:
> On 01/12/16 16:24, Shannon Zhao wrote:
>> When booting VM through UEFI, UEFI takes ownership of the RTC hardware.
>> To DTB UEFI could call libfdt api to disable the RTC device node, but to
>> ACPI it couldn't do that.
On 01/13/16 11:20, Ard Biesheuvel wrote:
> On 13 January 2016 at 11:18, Laszlo Ersek wrote:
>> On 01/12/16 16:24, Shannon Zhao wrote:
>>> When booting VM through UEFI, UEFI takes ownership of the RTC hardware.
>>> To DTB UEFI could call libfdt api to disable the RTC device
On 01/12/16 16:30, Peter Maydell wrote:
> On 12 January 2016 at 15:24, Shannon Zhao wrote:
>> When booting VM through UEFI, UEFI takes ownership of the RTC hardware.
>> To DTB UEFI could call libfdt api to disable the RTC device node, but to
>> ACPI it couldn't do that.
On 01/12/16 16:24, Shannon Zhao wrote:
> When booting VM through UEFI, UEFI takes ownership of the RTC hardware.
> To DTB UEFI could call libfdt api to disable the RTC device node, but to
> ACPI it couldn't do that. Therefore, we don't generate the RTC ACPI
> device in QEMU when using UEFI.
>
>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ruiyu Ni
Cc: Jeff Fan
Cc: Feng Tian
---
.../PciHostBridgeLibNull/PciHostBridgeLibNull.c| 104 +
The serial of patches look good to me.
Reviewed-by: Ye Ting
-Original Message-
From: Wu, Jiaxin
Sent: Monday, January 11, 2016 4:44 PM
To: edk2-devel@lists.01.org
Cc: Ye, Ting; Fu, Siyuan
Subject: [Patch 0/2] Fix IpSec SPD and SAD mapping issue when SPD updated
The
Adding Josh
On 01/06/16 13:28, Laszlo Ersek wrote:
> On 01/06/16 01:55, Fu, Siyuan wrote:
>> Hi, Laszlo
>>
>> You suggestion make sense, I will separate the patch into 2 commits
>> when check in it.
>
> Thanks.
>
>> For the second question, this patch only make the TX buffer recycle
>>
On Wed, Jan 13, 2016 at 01:43:38PM +0100, Laszlo Ersek wrote:
> I just noticed that the most recent release of BITS provides a
> standalone HTTP client!
>
> http://biosbits.org/news/bits-2070/
>
> Josh, a couple of points:
>
> - edk2 doesn't provide EFI_IP4_CONFIG_PROTOCOL any longer; it
ExtractConfig is called several times, it's not sufficient to update Secure
Boot STR_SECURE_BOOT_STATE_CONTENT, STR_CUR_SECURE_BOOT_MODE_CONTENT string in
ExtractConfig. Remove them to 4 places
1. SecureBootConfigDxe driver entry
2. Enroll PK
3. Delete PK
4. Change SecureBootMode
Reviewed-by: Qin Long
Best Regards & Thanks,
LONG, Qin
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> Zhang, Chao B
> Sent: Thursday, January 14, 2016 9:01 AM
> To: edk2-de...@ml01.01.org
> Cc: Fu, Siyuan; Zhang, Chao
It's good to me.
Reviewed-by: Fu Siyuan
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Zhang,
Chao B
Sent: Thursday, January 14, 2016 9:01 AM
To: edk2-de...@ml01.01.org
Cc: Fu, Siyuan ; Zhang, Chao B
Change KEY_TRANS_SECURE_BOOT_MODE value, as it conflicts with
OPTION_DEL_KEK_QUESTION_ID.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Chao Zhang
---
.../SecureBootConfigDxe/SecureBootConfigNvData.h | 4 ++--
1 file
On 01/13/16 17:16, Andrew Jones wrote:
> On Wed, Jan 13, 2016 at 10:54:17PM +0800, Shannon Zhao wrote:
>> When booting the VM with UEFI, UEFI takes ownership of the RTC hardware.
>> While UEFI can use libfdt to disable the RTC device node in the DTB that
>> it passes to the OS, it cannot modify
On Mi, 2016-01-13 at 13:43 +0100, Laszlo Ersek wrote:
> Gerd, can you please add -D HTTP_BOOT_ENABLE to the OVMF (IA32 / X64)
> build commands edk2.git.spec?
Done, build kicked.
cheers,
Gerd
___
edk2-devel mailing list
edk2-devel@lists.01.org
Check if the FV name is in the FV dictionary before using it which fixes
a crash during build report generation when FVs are specified by path
in the FDF.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Eugene Cohen
---
Dear Basetools maintainer,
We have an FDF file where we're creating an encapsulated FV where the FV
contents come from the filesystem instead of from a named FDF section. The FD
processing works fine in this case but the build report generator tool crashes.
Here's an example of how we
On 01/13/16 15:54, Shannon Zhao wrote:
> When booting the VM with UEFI, UEFI takes ownership of the RTC hardware.
> While UEFI can use libfdt to disable the RTC device node in the DTB that
> it passes to the OS, it cannot modify AML. Therefore, we won't generate
> the RTC ACPI device at all when
On 13 January 2016 at 15:54, Shannon Zhao wrote:
> When booting the VM with UEFI, UEFI takes ownership of the RTC hardware.
> While UEFI can use libfdt to disable the RTC device node in the DTB that
> it passes to the OS, it cannot modify AML. Therefore, we won't generate
21 matches
Mail list logo