HI Ruiyu,
Thanks for your detailed information. We can try to move to
MdeModulePkg/PciHostBridgeDxe later.
At 2016-03-16 10:41:38, "Ni, Ruiyu" wrote:
MdeModulePkg/PciHostBridgeDxe is a superset of PcAtChipsetPkg/PciHostBridgeDxe.
It requires a platform/silicon library instance PciHos
Reviewed-by: Liming Gao
> -Original Message-
> From: Cinnamon Shia [mailto:cinnamon.s...@hpe.com]
> Sent: Wednesday, March 16, 2016 10:45 AM
> To: edk2-devel@lists.01.org
> Cc: Ni, Ruiyu; Gao, Liming; el...@hpe.com; Cinnamon Shia
> Subject: [PATCH] Nt32Pkg: Switch the DebugLibReportStatus
NMAKE is limited to command-line length of 4096 characters. Due to the
large number of /I directives specified on command line (one per include
directory), the path length of WORKSPACE is multiplied by the number of
/I directives and can exceed the limit.
This patch:
1. Add new build option -l, --c
Switch the DebugLibReportStatusCode from IntelFrameworkPkg to MdeModulePkg.
The functionality and the code between them are almost the same.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Cinnamon Shia
---
Nt32Pkg/Nt32Pkg.dsc | 2 +-
1 file changed, 1 insertion(+), 1 dele
MdeModulePkg/PciHostBridgeDxe is a superset of PcAtChipsetPkg/PciHostBridgeDxe.
It requires a platform/silicon library instance PciHostBridgeLib which provides
the information
related to the how many root bridges the platform contains, and which range of
MMIO/IO
resources for each root bridge.
It
Reviewed-by: Eric Dong
> -Original Message-
> From: Bi, Dandan
> Sent: Tuesday, March 15, 2016 10:19 AM
> To: edk2-devel@lists.01.org
> Cc: Gao, Liming; Dong, Eric
> Subject: [patch] MdeModulePkg/DriverSampleDxe: Uninstall the ConfigAccess
> protocol
>
> In DriverSampleInit, has install
Reviewed-by: Zhang, Lubo
-Original Message-
From: Fu, Siyuan
Sent: Tuesday, March 15, 2016 9:41 AM
To: edk2-devel@lists.01.org
Cc: Gary Lin ; Laszlo Ersek ; Wu, Jiaxin
; Zhang, Lubo
Subject: [Patch] NetworkPkg: Fix the driver model issue in HTTP Boot driver.
The HTTP Boot driver have
Hi Ruiyu,
What's the diffience between PcAtChipsetPkg/PciHostBridgeDxe and
MdeModulePkg/PciHostBridgeDxe ?
We are now using PcAtChipsetPkg/PciHostBridgeDxe . We can move to
MdeModulePkg/PciHostBridgeDxe if the new driver also works. It will be helpful
we can know more detail informati
Reviewed-by: Eric Dong
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Andrew
> Fish
> Sent: Wednesday, March 16, 2016 2:06 AM
> To: edk2-devel
> Subject: [edk2] [MdeModulePkg] Do we support redefinition of typedefs?
>
> Xcode clang seems un
Regarding the subject, how about "PATCH v3" rather than "Patch V3"?
Reviewed-by: Jordan Justen
Pushed as db27e9f3d8f007bf26bcb8907ecab5b5f1fb8f24.
On 2016-03-15 01:10:40, Ruiyu Ni wrote:
> Current implementation only supports legacy region of 440 chip.
> When QEMU is launched in Q35 mode using
Reviewed-by: Jaben Carsey
> -Original Message-
> From: jim_dai...@dell.com [mailto:jim_dai...@dell.com]
> Sent: Tuesday, March 15, 2016 2:09 PM
> To: edk2-devel@lists.01.org
> Cc: Carsey, Jaben ; Qiu, Shumin
>
> Subject: [PATCH] ShellPkg:
> Importance: High
>
> ShellPkg: Launch shell wh
ShellPkg: Launch shell when startup.nsh is in the same directory
If there is a startup.nsh file in the same directory as the shell that
is being launched, the shell will abort. This change fixes that issue.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jim Dailey
---
Sh
> On Mar 15, 2016, at 11:26 AM, Alcantara, Paulo
> wrote:
>
> EDK II C Coding Standards spec seems to not recommend redefinition of
> typedefs. Since it's not supported by C89 and C99, I'd rather avoid it.
>
Paulo,
I agree with you. I just wanted to double check as it seems most compilers a
EDK II C Coding Standards spec seems to not recommend redefinition of typedefs.
Since it's not supported by C89 and C99, I'd rather avoid it.
Paulo
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Andrew
Fish
Sent: terça-feira, 15 de março de 201
The regular expression driver is mixing types it defines with edk2 types. The
regular expression types are less portable in regards to assumptions about the
sign of char. Matching the types removes a compiler warning on Xcode clang.
/Users/andrewfish/work/src/edk2/MdeModulePkg/Universal/Regular
Xcode clang seems unhappy with both FileExplorerLib.h and
Protocol/FileExplorer.h both defining CHOOSE_HANDLER
/Users/andrewfish/work/src/edk2/MdeModulePkg/Include/Library/FileExplorerLib.h:30:10:
error: redefinition of typedef 'CHOOSE_HANDLER' is a C11 feature
[-Werror,-Wtypedef-redefinition]
David,
Thanks for the suggestion. Today the git dev process requires a rebase.
Given that this operation is transferring content from one community
maintained feature branch in edk2-staging into edk2/master, I agree the
option to use 'git pull' should be available. Not sure it should be
requir
On 15/03/2016 16:48, Ni, Ruiyu wrote:
> I don't think CSM matters and the bin I am using cannot be
> distributed. Does the qemu build steps matters? I ran configure
> --target-list=x86_64-softmmu. I traced the code and found the code
> hung when SMM is relocating. The code was waiting for mRebase
I don't think CSM matters and the bin I am using cannot be distributed.
Does the qemu build steps matters?
I ran configure --target-list=x86_64-softmmu. I traced the code and found the
code hung when SMM is relocating. The code was waiting for mRebased flag be set.
Thanks,
Ray
> 在 2016年3月15日，下午
On 15/03/2016 12:59, Ni, Ruiyu wrote:
>> > I'm not sure. The above command line works for me after building OVMF
>> > like this:
>> >
>> >build -p OvmfPkg/OvmfPkgIa32X64.dsc -a IA32 -a X64 -b DEBUG -t GCC49 -n
>> > 4
>> >
>> > I'm using commit 89a8115 ("BaseTools: Support recent versions
Hi Evan,
Thanks - I really appreciate you taking the time to summarise the
situation.
On Tue, Mar 15, 2016 at 01:14:39PM +, Evan Lloyd wrote:
> I recently submitted some patches with fixes and improvements
> derived from our work on the Juno platform.
> Laszlo very politely queried my "sign o
This patch makes Shell support -nonesting invocation option. This option
specifies that EFI_SHELL_PROTOCOL.Execute API nesting of a new Shell
instance is optional and dependent on the 'nonesting' Shell environment
variable.
Difference with previous patch:
Do not use "negative" functions names.
Co
I recently submitted some patches with fixes and improvements derived from our
work on the Juno platform.
Laszlo very politely queried my "sign off" of the patches which bore Sami's
name as author and gracefully suggested the proper "S-o-b" style.
Others have since queried my consequent strategy
Thanks,
Ray
> 在 2016年3月15日，下午5:33，Paolo Bonzini 写道：
>
>
>
>> On 15/03/2016 10:10, Ni, Ruiyu wrote:
>> Paolo, Laszlo,
>> As I mentioned in previous mail, the EAX I got from CpuSaveState
>> is different from what I set before entering SMM.
>> Because the failure was seen in a QEMU launched in
On Tue, 2016-03-15 at 00:16 +, Kinney, Michael D wrote:
>
>
> Can you provide some revised text you would like to see in step 6.
>
> I agree that we need to use the tools in ways that help make this easy,
> prevent
> errors, and preserve history. Given that step 6 describes promoting a
>
Reviewed-by: Eric Dong
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Sheng,
> Cecil (HPS SW)
> Sent: Tuesday, March 15, 2016 10:39 AM
> To: edk2-devel@lists.01.org
> Cc: Tian, Feng; Zeng, Star
> Subject: Re: [edk2] [PATCH] MdeModulePkg: Fi
On 15/03/2016 10:10, Ni, Ruiyu wrote:
> Paolo, Laszlo,
> As I mentioned in previous mail, the EAX I got from CpuSaveState
> is different from what I set before entering SMM.
> Because the failure was seen in a QEMU launched in Windows
> using the following command:
> qemu-system-x86_64.exe \
>
Paolo, Laszlo,
As I mentioned in previous mail, the EAX I got from CpuSaveState
is different from what I set before entering SMM.
Because the failure was seen in a QEMU launched in Windows
using the following command:
qemu-system-x86_64.exe \
-machine q35,smm=on,accel=tcg \
-smp 1 \
-drive if
Forgot to mention the diff between v3 and v2.
v3 uses PcdOvmfHostBridgePciDevId as Jordan suggested.
v2 just updates the comments.
Regards,
Ray
>-Original Message-
>From: Ni, Ruiyu
>Sent: Tuesday, March 15, 2016 4:11 PM
>To: edk2-devel@lists.01.org
>Cc: Ni, Ruiyu ; Justen, Jordan L
>;
Current implementation only supports legacy region of 440 chip.
When QEMU is launched in Q35 mode using CSM enabled OVMF image,
LegacyBios driver fails to start due to the legacy region
[0xC, 0xF] cannot be written.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Rui
All,
I am going to remove the PciHostBridgeDxe driver from PcAtChipsetPkg.
This driver is not used by any platform as far as I know.
Any concerns?
Regards,
Ray
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk
31 matches
Mail list logo
