On 3/7/2018 2:01 PM, Guo Heyi wrote:
Thanks. Please let me know if any further changes are needed.
Regards,
Heyi
On Wed, Mar 07, 2018 at 12:30:59PM +0800, Ni, Ruiyu wrote:
On 3/6/2018 10:44 AM, Guo Heyi wrote:
Hi Ray,
Any comments for v5?
Heyi,
Some backward compatibility concerns were
On 03/14/18 00:28, Anatol Pomozov wrote:
> Hello
>
> I am implementing a simple UEFI bootloader. Most EFI functions that I
> tried work me - I can clear Console, print text, successfully read
> files from system partition, allocate memory pages.
>
> But if I try to read memory map and then call
Due to the fact that HeapGuard needs CpuArchProtocol to update page
attributes, the feature is normally enabled after CpuArchProtocol is
installed. Since there're some drivers are loaded before CpuArchProtocl,
they cannot make use HeapGuard feature to detect potential issues.
This patch fixes
On Wed, 14 Mar 2018 00:25:09 +,
Guo Heyi wrote:
>
> On Tue, Mar 13, 2018 at 09:33:33AM +, Marc Zyngier wrote:
> > On 13/03/18 00:31, Heyi Guo wrote:
> > > If timer interrupt is level sensitive, reloading timer compare
> > > register has a side effect of clearing GIC pending status, so a
Chen Chen:
Please update license header. Others are good to me.
Reviewed-by: Chao Zhang
-Original Message-
From: Chen, Chen A
Sent: Tuesday, March 13, 2018 3:37 PM
To: edk2-devel@lists.01.org
Cc: Chen, Chen A ; Ni, Ruiyu
Hello everyone,
I have an Intel Reference Board. I was trying to force BIOS to wait 1
second in SEC phase.
I inserted these assemble code (BIOS wait function) into very first of
ProtectedModeEntryPoint in Flat32.asm file:
MOV CX, 0FH
MOV DX, 4240H
MOV AH, 86H
INT 15H
On 03/13/18 22:22, Laszlo Ersek wrote:
> Repo: https://github.com/lersek/edk2.git
> Branch: qemu_bootorder_connect
>
> Adding tens or hundreds of bootable devices to a QEMU VM config slows
> the OVMF and ArmVirtQemu boots to a crawl, several people have reported
> in the past.
>
> There are at
On 14 March 2018 at 12:24, Leif Lindholm wrote:
> On Thu, Jan 04, 2018 at 07:24:20PM +, Ard Biesheuvel wrote:
>> On 4 January 2018 at 18:55, Girish Pathak wrote:
>> > Hi Ard,
>> >
>> >> -Original Message-
>> >> From: edk2-devel
The series is good to me.
Reviewed-by: Hao Wu
Best Regards,
Hao Wu
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Star
> Zeng
> Sent: Wednesday, March 14, 2018 5:34 PM
> To: edk2-devel@lists.01.org
> Cc: Ni, Ruiyu; Wu,
Mike,
Evaluating block size is a good idea!
The block size of the target USB device is 2048 in my platform.
I modify the UsbMassBoot.c with evaluating block size and it works.
I will send the patch later.
Thanks,
Ming
On 2018/3/13 9:38, Kinney, Michael D wrote:
> Star,
>
> Maybe we should
de8373fa07f87ca735139bb86c51e2c29fb1d956 could not handle two cases.
1. For the case that the USB3 debug port instance and DMA buffers are
from PEI HOB with IOMMU enabled, it was to reallocate the DMA buffers
by AllocateAddress with the memory type accessible by SMM environment.
But reallocating
Refine some formats/comments and remove some unused prototypes.
Cc: Ruiyu Ni
Cc: Hao Wu
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Star Zeng
---
.../DebugCommunicationLibUsb3Common.c | 16
Utilities written in Python may depend on external (preinstalled) Python
packages; for example, Ecc depends on "antlr_python_runtime-3.0.1". Such
packages need not be installed system-wide, as long as they are reachable
through PYTHONPATH. Therefore we shouldn't overwrite the user's PYTHONPATH
On 14 March 2018 at 07:57, Ni, Ruiyu wrote:
> On 3/7/2018 2:01 PM, Guo Heyi wrote:
>>
>> Thanks. Please let me know if any further changes are needed.
>>
>> Regards,
>>
>> Heyi
>>
>> On Wed, Mar 07, 2018 at 12:30:59PM +0800, Ni, Ruiyu wrote:
>>>
>>> On 3/6/2018 10:44 AM, Guo
On Wed, Mar 14, 2018 at 12:35:03PM +, Ard Biesheuvel wrote:
> >> I guess Leif and I are in disagreement here. In particular, I think
> >> his comment
> >>
> >> """
> >> ASSERT (FALSE)? (You already know Status is an EFI_ERROR, and a
> >> console message saying ASSERT (Status) is not getting
This reverts commit de8373fa07f87ca735139bb86c51e2c29fb1d956.
Cc: Ruiyu Ni
Cc: Hao Wu
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Star Zeng
---
.../DebugCommunicationLibUsb3Common.c | 222
Fix GCC build failures below.
variable 'EvtTrb' set but not used [-Werror=unused-but-set-variable]
variable 'Index' set but not used [-Werror=unused-but-set-variable]
The build failure could only be caught with -D SOURCE_DEBUG_USE_USB3
build flag.
ad6040ec9b5bbc462762331f9738b8e42c0b9c80 needs
This reverts commit ad6040ec9b5bbc462762331f9738b8e42c0b9c80.
Cc: Ruiyu Ni
Cc: Hao Wu
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Star Zeng
---
The patch series is also at
https://github.com/lzeng14/edk2 DebugCommUsb3AfterIOMMUV2 branch.
Based on the feedbacks from Ray and Hao.
It is V2 of
https://lists.01.org/pipermail/edk2-devel/2018-March/022586.html.
It has no essential difference with V1 about the final code, but
re-arranges the
This reverts commit 6ef394ffe29bbc67038fc16ed540bfe6eed10e16.
Cc: Ruiyu Ni
Cc: Hao Wu
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Star Zeng
---
On 13 March 2018 at 21:22, Laszlo Ersek wrote:
> Repo: https://github.com/lersek/edk2.git
> Branch: qemu_bootorder_connect
>
> Adding tens or hundreds of bootable devices to a QEMU VM config slows
> the OVMF and ArmVirtQemu boots to a crawl, several people have reported
> in
On 3/14/2018 5:33 PM, Star Zeng wrote:
The patch series is also at
https://github.com/lzeng14/edk2 DebugCommUsb3AfterIOMMUV2 branch.
Based on the feedbacks from Ray and Hao.
It is V2 of
https://lists.01.org/pipermail/edk2-devel/2018-March/022586.html.
It has no essential difference with V1
On 1 March 2018 at 06:57, Heyi Guo wrote:
> Use ZeroMem to initialize all fields in temporary
> PCI_ROOT_BRIDGE_APERTURE variables to zero. This is not mandatory but
> helpful for future extension: when we add new fields to
> PCI_ROOT_BRIDGE_APERTURE and the default value of
Hi Arvind,
On Sat, Mar 10, 2018 at 11:11:58AM -0500, Arvind Prasanna wrote:
> It is possible to source edksetup.sh from another script. If the
> calling/sourcing script has any positional parameters set, those are
> incorrectly accounted for in edksetup.sh while sourcing it resulting in
> the the
On Thu, Jan 04, 2018 at 07:24:20PM +, Ard Biesheuvel wrote:
> On 4 January 2018 at 18:55, Girish Pathak wrote:
> > Hi Ard,
> >
> >> -Original Message-
> >> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> >> Ard Biesheuvel
> >> Sent: 23
On 14 March 2018 at 07:45, Marc Zyngier wrote:
> On Wed, 14 Mar 2018 00:25:09 +,
> Guo Heyi wrote:
>>
>> On Tue, Mar 13, 2018 at 09:33:33AM +, Marc Zyngier wrote:
>> > On 13/03/18 00:31, Heyi Guo wrote:
>> > > If timer interrupt is level sensitive, reloading timer
There's a bit operation error found in 32-bit platform. I'll send a v2 patch
later.
Regards,
Jian
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Jian J
> Wang
> Sent: Wednesday, March 14, 2018 4:31 PM
> To: edk2-devel@lists.01.org
> Cc:
Mike:
Now, %pragma macho subsections_via_symbols can't be enabled. So, will nasm
generate the bigger image size than .S assembly on macho? If yes, I agree nasm
is not same to .S. .S may be kept for a while. But, .asm is not necessary. We
can remove .asm first.
Thanks
Liming
> -Original
On 3/15/2018 10:27 AM, Jian J Wang wrote:
v2 changes:
Fix a logic hole in bits operation on address on 64K boundary with
just 64-bit length (SetBits(), ClearBits(), GetBits()).
Due to the fact that HeapGuard needs CpuArchProtocol to update page
attributes, the feature is normally
On 3/15/2018 12:00 PM, Heyi Guo wrote:
PCI address translation is necessary for some non-x86 platforms. On
such platforms, address value (denoted as "device address" or "address
in PCI view") set to PCI BAR registers in configuration space might be
different from the address which is used by CPU
On 3/15/2018 10:57 AM, Guo Heyi wrote:
Hi Ray,
Sorry I never tried Ecc tool before, for there is few documents about it. When I
tried running python BaseTools/Source/Python/Ecc/Ecc.py -t -s ,
it showed me with error message:
ImportError: No module named Common.LongFilePathOs
Then I found
v6:
- Patch 1, 2: implement 3 comments from Laszlo.
- Patch 4: implement 3 comments from Ray.
Patch v5 inherits the code from RFC v4; we don't restart the version number for
RFC to PATCH change.
v5:
- Patch 4/6: Modify the code according to the comments from Ray.
- Patch 1/6 and 2/6 are totally
Thanks catching this. New patch has sent out.
Regards,
Jian
> -Original Message-
> From: Ni, Ruiyu
> Sent: Thursday, March 15, 2018 11:47 AM
> To: Wang, Jian J ; edk2-devel@lists.01.org
> Cc: Yao, Jiewen ; Dong, Eric ;
>
If given address is on 64K boundary and the requested bit number is 64,
all SetBits(), ClearBits() and GetBits() will encounter ASSERT problem
in trying to do a 64 bits of shift, which is not allowed by LShift() and
RShift(). This patch tries to fix this issue by turning bits operation
into whole
> v3:
>Split the fixes into three patch files.
> v2:
>Fix a logic hole in bits operation on address on 64K boundary with
>just 64-bit length (SetBits(), ClearBits(), GetBits()).
This patch series fills up an empty window period of HeapGuard feature
before CpuArchProtocol installed,
If given address is on 64K boundary and the requested bit number is 64,
all SetBits(), ClearBits() and GetBits() will encounter ASSERT problem
in trying to do a 64 bits of shift, which is not allowed by LShift() and
RShift(). This patch tries to fix this issue by turning bits operation
into whole
On Thu, Mar 15, 2018 at 01:27:59PM +0800, Ni, Ruiyu wrote:
> On 3/15/2018 12:00 PM, Heyi Guo wrote:
> >v6:
> >- Patch 1, 2: implement 3 comments from Laszlo.
> >- Patch 4: implement 3 comments from Ray.
> >
> >Patch v5 inherits the code from RFC v4; we don't restart the version number
> >for
>
Current code uses string length as BufferSize input to UnicodeSPrint,
it is wrong and makes the pop up string trimmed. The BufferSize input
to UnicodeSPrint should be the size, in bytes, of the output buffer.
This is to use sizeof (mPopUpString) as the BufferSize input to
UnicodeSPrint, it also
Use ZeroMem() to initialize (or re-initialize) all fields in temporary
PCI_ROOT_BRIDGE_APERTURE variables to zero. This is not mandatory but
is helpful for future extension: when we add new fields to
PCI_ROOT_BRIDGE_APERTURE and the default value of these fields can
safely be zero, this code will
PCI address translation is necessary for some non-x86 platforms. On
such platforms, address value (denoted as "device address" or "address
in PCI view") set to PCI BAR registers in configuration space might be
different from the address which is used by CPU to access the
registers in memory BAR or
Add Translation field to PCI_ROOT_BRIDGE_APERTURE. Translation is used
to represent the difference between device address and host address,
if they are not the same on some platforms.
In UEFI 2.7, "Address Translation Offset" is "Offset to apply to the
Starting address to convert it to a PCI
Use ZeroMem() to initialize (or re-initialize) all fields in temporary
PCI_ROOT_BRIDGE_APERTURE variables to zero. This is not mandatory but
helpful for future extension: when we add new fields to
PCI_ROOT_BRIDGE_APERTURE and the default value of these fields can
safely be zero, this code will not
According to UEFI spec 2.7, PciRootBridgeIo->Configuration() should
return host address (CPU view ddress) rather than device address
(PCI view address), so in function GetMmioAddressTranslationOffset we
need to convert the range to device address before comparing.
And device address = host
According to UEFI spec 2.7, PciIo->GetBarAttributes should return host
address (CPU view ddress) rather than device address (PCI view
address), and
device address = host address + address translation offset,
so we subtract translation from device address before returning.
Contributed-under:
> On Mar 14, 2018, at 6:56 PM, Gao, Liming wrote:
>
> Mike:
> Now, %pragma macho subsections_via_symbols can't be enabled. So, will nasm
> generate the bigger image size than .S assembly on macho?
Yes.
Thanks,
Andrew Fish
> If yes, I agree nasm is not same to .S.
On 3/15/2018 12:00 PM, Heyi Guo wrote:
v6:
- Patch 1, 2: implement 3 comments from Laszlo.
- Patch 4: implement 3 comments from Ray.
Patch v5 inherits the code from RFC v4; we don't restart the version number for
RFC to PATCH change.
v5:
- Patch 4/6: Modify the code according to the comments
On 3/15/2018 1:03 PM, Jian J Wang wrote:
v3:
Split the fixes into three patch files.
v2:
Fix a logic hole in bits operation on address on 64K boundary with
just 64-bit length (SetBits(), ClearBits(), GetBits()).
This patch series fills up an empty window period of HeapGuard
> v2 changes:
>Fix a logic hole in bits operation on address on 64K boundary with
>just 64-bit length (SetBits(), ClearBits(), GetBits()).
Due to the fact that HeapGuard needs CpuArchProtocol to update page
attributes, the feature is normally enabled after CpuArchProtocol is
installed.
Hi Ray,
Sorry I never tried Ecc tool before, for there is few documents about it. When I
tried running python BaseTools/Source/Python/Ecc/Ecc.py -t -s ,
it showed me with error message:
ImportError: No module named Common.LongFilePathOs
Then I found there was an executable named "Ecc" in
What does that mean??
Sorry for asking beginner questions but was just wondering. Trying to
shrink the size of the Duet image.
Thank you
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
Here is NULL DebugLib and ReportStatusCodeLib instance. They are dummy
implementation. They will not take the image size, and remove the debug message
and ASSERT code from the image. So, they can help to save the image size.
MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull.inf
On 3/1/2018 2:57 PM, Heyi Guo wrote:
Patch v5 inherits the code from RFC v4; we don't restart the version number for
RFC to PATCH change.
v5:
- Patch 4/6: Modify the code according to the comments from Ray.
- Patch 1/6 and 2/6 are totally new. They add initialization for all fields of
Reviewed-by: david wei
Thanks,
David Wei
Intel SSG/STO/UEFI BIOS
-Original Message-
From: Kinney, Michael D
Sent: Tuesday, March 13, 2018 3:30 AM
To: edk2-devel@lists.01.org
Cc: Kinney, Michael D ;
change to the style we document as in use
Cc: Yonghong Zhu
Cc: Liming Gao
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Jaben Carsey
---
BaseTools/Source/Python/AutoGen/AutoGen.py | 138
use __new__ and __init__ to create/manage/initialize objects in standard flow.
Cc: Yonghong Zhu
Cc: Liming Gao
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Jaben Carsey
---
update the object factory and child classes to use standard functions
update the file to use is None instead of == None
Jaben Carsey (2):
BaseTools: Autogen - modify to use standard parent/child class
relationships
BaseTools: AutoGen should use is None not == None
This patch introduces a branch for implementing Dynamic Tables
Framework. The description is in the Readme.md file.
Please create a branch called 'dynamictables' in edk2-staging.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Sami Mujawar
Reviewed-by: Kelly Steele
Thanks,
Kelly
> -Original Message-
> From: Kinney, Michael D
> Sent: March 12, 2018 12:30
> To: edk2-devel@lists.01.org
> Cc: Sean Brogan ; Zhu, Yonghong
> ; Gao, Liming
On Thu, Feb 15, 2018 at 01:31:50PM +, achin.gu...@arm.com wrote:
> From: Achin Gupta
>
> This patch adds maintainers, reviewer and directory for the
> StandaloneMmPkg. This package will host an implementation of Standalone
> Management Mode as specified in the Platform
On 14 March 2018 at 19:34, Evan Lloyd wrote:
> Hi Ard.
> We still have a minor problem in that the spec disqualifies EFI_MEMORY_XP for
> AARCH64.
> Do you have any thoughts on this?
> How should we proceed here? I assume the specification statement was a
> considered
This patch introduces a branch for implementing Dynamic Tables
Framework. The description is in the Readme.md file.
Please create a branch called 'devel-dynamictables' in edk2-platforms.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Sami Mujawar
Hi Ard.
We still have a minor problem in that the spec disqualifies EFI_MEMORY_XP for
AARCH64.
Do you have any thoughts on this?
How should we proceed here? I assume the specification statement was a
considered decision.
Do we need to get it changed, or is EFI_MEMORY_XP unnecessary?
Regards,
62 matches
Mail list logo