ARM platforms have no restriction on when a system firmware update
capsule can be applied, and so it is not necessary to call
ProcessCapsules() twice. So let's drop the first invocation that
occurs before EndOfDxe, and rewrite the second call so that all
capsule updates will be applied when the
This is the delta of code required to implement PersistAcrossReset on ARM
systems, and to wire up the capsule handling routines in a way that makes
the new progress reporting code do something meaningful on such platforms.
Changes since v2:
- move cache handling from CapsulePei to
When capsule updates are staged for processing after a warm reboot,
they are copied into memory with the MMU and caches enabled. When
the capsule PEI gets around to coalescing the capsule, the MMU and
caches may still be disabled, and so on architectures where uncached
accesses are incoherent with
If the first call to UpdateImageProgress() fails, there is no point
in passing a pointer to it to Fmp->SetImage(), since it is highly
unlikely to succeed on any subsequent calls.
This permits the FMP implementation to fall back to an alternate means
of providing feedback to the user, e.g., via
Implement ResetSystemLib's EnterS3WithImmediateWake() routine using
a jump back to the PEI entry point with interrupts and MMU+caches
disabled. This is only possible at boot time, when we are sure that
the current CPU is the only one up and running. Also, it depends on
the platform whether the PEI
Reviewed-by: Yonghong Zhu
Best Regards,
Zhu Yonghong
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Jaben
Carsey
Sent: Friday, May 18, 2018 8:07 AM
To: edk2-devel@lists.01.org
Subject: [edk2] [PATCH v1 0/2] BaseTools: cleanup for speed
the
On 12 June 2018 at 11:01, Ard Biesheuvel wrote:
> On 12 June 2018 at 02:54, Kinney, Michael D
> wrote:
>> Ard,
>>
>> What about memory init when the memory HOBs are
>> created. Could you flush all the ranges of
>> initialized memory by HOB as the HOBs are created?
>>
>> PEI and DXE can not use
On Tue, Jun 12, 2018 at 01:23:28PM +0200, Ard Biesheuvel wrote:
> ARM platforms have no restriction on when a system firmware update
> capsule can be applied, and so it is not necessary to call
> ProcessCapsules() twice. So let's drop the first invocation that
> occurs before EndOfDxe, and rewrite
On 12 June 2018 at 02:54, Kinney, Michael D wrote:
> Ard,
>
> What about memory init when the memory HOBs are
> created. Could you flush all the ranges of
> initialized memory by HOB as the HOBs are created?
>
> PEI and DXE can not use memory not described by
> the HOBs. More memory can be
I am thinking that could platform BDS parse CAPSULE HOB and call
ProcessCapsuleImage by itself in its willing phase with flexibility for the
case?
Thanks,
Star
-Original Message-
From: Yao, Jiewen
Sent: Monday, June 11, 2018 11:12 PM
To: Ard Biesheuvel
Cc: Kinney, Michael D ;
On 06/12/18 06:32, Wang, Jian J wrote:
> Hi Laszlo,
>
> Thank you very much for such thorough review. I'd like to explain a bit in
> advance.
>
> Putting aside the specific coding issues in my patch, one thing is clear that
> SMM mode
> has its own page table. CpuDxe should not touch it even
Hi,
This is the efi driver for qemu ramfb, a simple boot framebuffer. Qemu
patches just have been posted to qemu-devel.
v2: tons of codestyle fixes, some control flow tweaks.
cheers,
Gerd
Gerd Hoffmann (4):
OvmfPkg: add QEMU_RAMFB_GUID
OvmfPkg: add QemuRamfbDxe
OvmfPkg: add
Add GUID header file for the QemuRamfbDxe driver.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Gerd Hoffmann
---
OvmfPkg/Include/Guid/QemuRamfb.h | 25 +
OvmfPkg/OvmfPkg.dec | 1 +
2 files changed, 26 insertions(+)
create mode
Add a driver for the qemu ramfb display device.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Gerd Hoffmann
---
OvmfPkg/QemuRamfbDxe/QemuRamfb.c | 396 ++
OvmfPkg/OvmfPkgIa32.dsc | 1 +
OvmfPkg/OvmfPkgIa32.fdf
Add QemuRamfbDxe to dsc and fdf files for ArmVirt package.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Gerd Hoffmann
---
ArmVirtPkg/ArmVirtQemu.dsc | 2 ++
ArmVirtPkg/ArmVirtQemuFvMain.fdf.inc | 1 +
ArmVirtPkg/ArmVirtQemuKernel.dsc | 2 ++
3 files
Add QemuRamfbDxe device path to the list of platform console devices,
so ConSplitter will pick up the device even though it isn't a PCI GPU.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Gerd Hoffmann
---
.../Library/PlatformBootManagerLib/PlatformData.c | 51
Reviewed-by: Dandan Bi
Thanks,
Dandan
-Original Message-
From: Ni, Ruiyu
Sent: Monday, June 11, 2018 10:37 AM
To: edk2-devel@lists.01.org
Cc: Bi, Dandan
Subject: [PATCH] MdeModulePkg/AtaAtapiPassThru: Fix VS2010/VS2012 build failure
The patch doesn't have functionality impact. It is
Hi,
> - What happens in the UEFI shell if you do recursive connect/disconnect
> cycles for all handles in the system? (Preferably initiated from serial.)
Seems to work fine (tried "disconnect -a" and "connect").
> - What happens if you locate the parent handle (with the VenHw node)
> and/or
On 06/12/18 05:36, Zeng, Star wrote:
> Sorry, fix typo.
>
> DXE > (SMM communcation) > InSmm = TRUE > SMM driver dispatcher/SMM handler >
> InSmm = FALSE > (exit SMM communication) > DXE
Thank you Star, I'll have to remember this!
Laszlo
> -Original Message-
> From: Zeng, Star
>
Reviewed-by: Ruiyu Ni
Thanks/Ray
> -Original Message-
> From: Bi, Dandan
> Sent: Monday, June 11, 2018 4:32 PM
> To: edk2-devel@lists.01.org
> Cc: Gao, Liming ; Ni, Ruiyu ;
> Carsey, Jaben
> Subject: [patch V2 2/3] ShellPkg/Dp: Initialize summary date when run DP
>
> Issue:
> When run
On 12 June 2018 at 03:40, Gao, Liming wrote:
> Reviewed-by: Liming Gao
>
Thanks
Pushed as c25d3905523a
>> -Original Message-
>> From: Ard Biesheuvel [mailto:ard.biesheu...@linaro.org]
>> Sent: Tuesday, June 12, 2018 12:29 AM
>> To: edk2-devel@lists.01.org
>> Cc: ler...@redhat.com;
Hi,
> > + {
> > +.HorizontalResolution = 640,
> > +.VerticalResolution= 480,
> > + },{
> > +.HorizontalResolution = 800,
> > +.VerticalResolution= 600,
> > + },{
> > +.HorizontalResolution = 1024,
> > +.VerticalResolution= 768,
> > + }
> > +};
>
>
On 12 June 2018 at 14:25, Leif Lindholm wrote:
> On Tue, Jun 12, 2018 at 01:23:28PM +0200, Ard Biesheuvel wrote:
>> ARM platforms have no restriction on when a system firmware update
>> capsule can be applied, and so it is not necessary to call
>> ProcessCapsules() twice. So let's drop the first
Annotate module entry points with EFI_ENTRYPOINT so we can classify
the resulting symbol as global explicitly at link time.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
EmulatorPkg/Sec/Sec.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Annotate module entry points with EFI_ENTRYPOINT so we can classify
the resulting symbol as global explicitly at link time.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
MdePkg/Include/Library/DxeCoreEntryPoint.h | 1 +
Ard
Do you think we also need update QueryCapsuleCapabilities() to return
UNSUPPORTED for CAPSULE_FLAGS_PERSIST_ACROSS_RESET?
Thank you
Yao Jiewen
> -Original Message-
> From: Ard Biesheuvel [mailto:ard.biesheu...@linaro.org]
> Sent: Tuesday, June 12, 2018 4:23 AM
> To:
Annotate module entry points with EFI_ENTRYPOINT so we can classify
the resulting symbol as global explicitly at link time.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
Nt32Pkg/Sec/SecMain.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Annotate module entry points with EFI_ENTRYPOINT so we can classify
the resulting symbol as global explicitly at link time.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
UefiCpuPkg/Library/PlatformSecLibNull/PlatformSecLibNull.c | 1 +
1 file changed,
When LTO is in effect, overriding the symbol visibility to 'hidden'
using a GCC pragma used to result in module entry points being discarded,
and along with them all other code in the binary.
Now that we annotated all module entry points explicitly as having
'default' visibility, this is no
On 06/12/18 11:31, Gerd Hoffmann wrote:
> Add GUID header file for the QemuRamfbDxe driver.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Gerd Hoffmann
> ---
> OvmfPkg/Include/Guid/QemuRamfb.h | 25 +
> OvmfPkg/OvmfPkg.dec | 1
Ard,
The UEFI Spec allows UpdateCapsule() to return EFI_UNSUPPORTED.
So after ExitBootServices() UpdateCapsule() can return EFI_UNSUPPORTED for any
capsule that has the CAPSULE_FLAGS_PERSIST_ACROSS_RESET flag set.
Mike
> -Original Message-
> From: Ard Biesheuvel
On Fri, Jun 08, 2018 at 05:33:59PM +0200, Marcin Wojtas wrote:
> From: jinghua
>
> ArmadaSoCDescLib is a per SoC family library, which provides SoC
> description, like register base of some hardware module controller,
> COMPHY/I2C/NETWORK etc., which right now is hardcoded in MvHwDescLib.h.
>
Annotate module entry points with EFI_ENTRYPOINT so we can classify
the resulting symbol as global explicitly at link time.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
IntelFrameworkPkg/Library/DxeSmmDriverEntryPoint/DriverEntryPoint.c | 1 +
1 file
Annotate module entry points with EFI_ENTRYPOINT so we can classify
the resulting symbol as global explicitly at link time.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
DuetPkg/DxeIpl/DxeInit.c | 1 +
DuetPkg/EfiLdr/EfiLoader.c | 1 +
2 files
Annotate module entry points with EFI_ENTRYPOINT so we can classify
the resulting symbol as global explicitly at link time.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
EmbeddedPkg/TemplateSec/TemplateSec.c | 1 +
1 file changed, 1 insertion(+)
diff
The GCC toolchain uses PIE mode when building code for X64, because it
is the most efficient in size: it uses relative references where
possible, but still uses 64-bit quantities for absolute symbol
references, which is optimal for executables that need to be converted
to PE/COFF using GenFw.
Add a macro EFI_ENTRYPOINT that we will use to decorate functions that
serve as the entry points for EFI modules. This is necessary to work
around a limitation in GCC, which may prune such routines from the
ELF binary if they are defined with hidden visibility, even if they
are explicitly
Annotate module entry points with EFI_ENTRYPOINT so we can classify
the resulting symbol as global explicitly at link time.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
Annotate module entry points with EFI_ENTRYPOINT so we can classify
the resulting symbol as global explicitly at link time.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Ard Biesheuvel
---
MdeModulePkg/Universal/CapsulePei/X64/X64Entry.c | 1 +
1 file changed, 1
On 12 June 2018 at 17:23, Yao, Jiewen wrote:
> Ard
> Do you think we also need update QueryCapsuleCapabilities() to return
> UNSUPPORTED for CAPSULE_FLAGS_PERSIST_ACROSS_RESET?
>
Yes, but only at runtime. I can update the patch if you like.
>> -Original Message-
>> From: Ard Biesheuvel
On Fri, Jun 08, 2018 at 05:34:00PM +0200, Marcin Wojtas wrote:
> This patch adds a new library class that will be helpful
> to describe a per-board information, which will be
> processed by BoardDesc protocol.
>
> Together with ArmadaSoCDescLib data it will be a flexible
> solution allowing to
On 06/12/18 11:31, Gerd Hoffmann wrote:
> Add QemuRamfbDxe device path to the list of platform console devices,
> so ConSplitter will pick up the device even though it isn't a PCI GPU.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Gerd Hoffmann
> ---
>
On 06/12/18 11:31, Gerd Hoffmann wrote:
> Add QemuRamfbDxe to dsc and fdf files for ArmVirt package.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Gerd Hoffmann
> ---
> ArmVirtPkg/ArmVirtQemu.dsc | 2 ++
> ArmVirtPkg/ArmVirtQemuFvMain.fdf.inc | 1 +
>
On Fri, Jun 08, 2018 at 05:34:02PM +0200, Marcin Wojtas wrote:
> From: jinghua
>
> This patch introduces a producer of MARVELL_BOARD_DESC_PROTOCOL, which
> gets SoC description from ArmadaSoCDescLib, then based on dsc file,
> provide only enabled hardware module controllers for the consumers,
>
On Fri, Jun 08, 2018 at 05:34:12PM +0200, Marcin Wojtas wrote:
> ComPhy Library used to get Armada7k8k AHCI/SDMMC/XHCI controller
> description from hardcoded values stored in the header file
> MvHwDescLib.h. As a result it is very hard to support other
> Armada SoC families with this library.
>
Hi Ard, Zenith,
Thank you both explained the complete knowledge about ELF GOT, LTO, PIC/PIE,
machine code mode and GCC visibility #pragma. It is pretty good to read them
all in one picture. And I believe copying these explain to a edk2 wiki page in
GitHub could be very useful for other edk2
No. Most PEI runs in flash, are not loaded into RAM. So, I suggest to locate
FvInfoPpi and get PEI FV image data. You can calculate CRC32 value of PEI FV
image.
From: Guy Raviv [mailto:guyrav...@gmail.com]
Sent: Tuesday, June 12, 2018 1:37 PM
To: Gao, Liming
Cc: edk2-devel@lists.01.org
Reviewed-by: Yonghong Zhu
Best Regards,
Zhu Yonghong
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Yonghong
Zhu
Sent: Tuesday, June 12, 2018 9:01 AM
To: edk2-devel@lists.01.org
Cc: Feng, YunhuaX ; Gao, Liming
Subject: [edk2] [Patch]
Do a clean up to remove the unneeded code.
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Yonghong Zhu
---
BaseTools/Source/Python/Workspace/MetaFileParser.py | 17 -
1 file changed, 17 deletions(-)
diff --git
On Fri, Jun 08, 2018 at 05:34:23PM +0200, Marcin Wojtas wrote:
> Finally, after switching to new MV_BOARD_DESC solution
> in all drivers, stop using MvHwDescLib.h by its last user
> and safely remove this header.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Marcin
On Thu, Jun 07, 2018 at 05:08:18PM +0200, Ard Biesheuvel wrote:
> In order to allow for more flexibility when updating parts of the
> firmware via capsule update, expand the description of the code FV
> to cover the entire 4 MB region at the base of the NOR flash.
>
> Contributed-under: TianoCore
So, I've made all the comments I was going to be making on this set.
Patches 3,5-7,13,20-21 are fine as long as you drop pre-existing
Signed-off-by and Reviewed-by, so if you get rid of those you can add
Reviewed-by: Leif Lindholm
when reposting.
(If any patch apart from the above didn't
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
On Fri, Jun 08, 2018 at 05:34:22PM +0200, Marcin Wojtas wrote:
> MvI2cDxe driver used to get Armada7k8k controller description
> from hardcoded values stored in the header file MvHwDescLib.h.
> As a result it is very hard to support other
> Armada SoC families with this driver.
>
> This patch
On Thu, Jun 07, 2018 at 01:32:03PM +0200, Ard Biesheuvel wrote:
> Replace the home cooked progress indication with calls into the new
> (*Progress)() argument to PerformFlashWriteWithProgress(), which
> allows the flash access routine to report progress via a platform
> provided callback.
>
>
On Thu, Jun 07, 2018 at 05:08:17PM +0200, Ard Biesheuvel wrote:
> In commit 913fdda9f4b9 ("Silicon/SynQuacerPlatformFlashAccessLib: don't
> dereference FVB header fields"), we dropped all accesses to FVB header
> field, which was necessary because the flash partition may not in fact
> contain such
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
Removing rules for Ipf sources file:
* Remove the source file which path with "ipf" and also listed in
[Sources.IPF] section of INF file.
* Remove the source file which listed in [Components.IPF] section
of DSC file and not listed in any other [Components] section.
* Remove the embedded Ipf
> v2:
> a. add more specific explanations in commit message
> b. add more comments in code
> c. remove redundant logic in code
> d. fix logic hole in code
> e. replace meanless constant macro with meaning ones
> f. remove irrelated changes
This patch series try to fix an issue caused
CpuDxe driver is updated to be able to access DXE page table in SMM mode,
which means Heap Guard can get correct memory paging attributes in what
environment. It's not necessary to exclude SMM from detecting Heap Guard
feature support.
Cc: Star Zeng
Cc: Eric Dong
Cc: Jiewen Yao
Cc: Ruiyu Ni
> v2:
> a. add more specific explanations in commit message
> b. add more comments in code
> c. remove redundant logic in IsInSmm()
> d. fix a logic hole in GetCurrentPagingContext()
> e. replace meanless constant macro with meaning ones
The MdePkg/Library/SmmMemoryAllocationLib, used
On 2018-06-12 20:43:03, chenc2 wrote:
> Removing rules for Ipf sources file:
> * Remove the source file which path with "ipf" and also listed in
> [Sources.IPF] section of INF file.
> * Remove the source file which listed in [Components.IPF] section
> of DSC file and not listed in any other
Reviewed-by: Liming Gao
>-Original Message-
>From: Chen, Chen A
>Sent: Wednesday, June 13, 2018 11:44 AM
>To: edk2-devel@lists.01.org
>Cc: Chen, Chen A ; Gao, Liming
>; Kinney, Michael D
>Subject: [PATCH 18/37] IntelFrameworkPkg: Removing ipf from edk2.
>
>Removing rules for Ipf sources
Reviewed-by: Liming Gao
>-Original Message-
>From: Chen, Chen A
>Sent: Wednesday, June 13, 2018 11:44 AM
>To: edk2-devel@lists.01.org
>Cc: Chen, Chen A ; Gao, Liming
>; Kinney, Michael D
>Subject: [PATCH 17/37] IntelFrameworkModulePkg: Removing ipf from edk2.
>
>Removing rules for Ipf
> Absolute symbol references such as?
> References to fixed (constant)
> addresses?
Pointers stored in the .data section. For example, if you have an array of
const char*.
> Why is that approach optimal? As few
> relocations records are required as
> possible?
small pic model is optimal for
On Fri, Jun 08, 2018 at 05:34:10PM +0200, Marcin Wojtas wrote:
> Introduce new callback that can provide information
> about NonDiscoverableDevices to the relevant drivers and libraries.
>
> Extend ArmadaBoardDescLib with new structures (MV_BOARD_AHCI_DESC/
>
On Fri, Jun 08, 2018 at 05:34:13PM +0200, Marcin Wojtas wrote:
> This patch introduces new library callback (ArmadaSoCDescComPhyGet ()),
> which dynamically allocates and fills MV_SOC_COMPHY_DESC structure with
> the SoC description of ComPhy SerDes controllers.
>
> Contributed-under: TianoCore
On Fri, Jun 08, 2018 at 05:34:14PM +0200, Marcin Wojtas wrote:
> Introduce new callback that can provide information
> about COMPHY controllers to the ComPhyLib.
>
> Extend ArmadaBoardDescLib with new structure MV_BOARD_COMPHY_DESC,
> for holding board specific data. In further steps it can
> be
On Fri, Jun 08, 2018 at 05:34:16PM +0200, Marcin Wojtas wrote:
> This patch introduces new library callback (ArmadaSoCDescMdioGet ()),
> which dynamically allocates and fills MV_SOC_MDIO_DESC structure with
> the SoC description of Mdio controllers.
>
> Contributed-under: TianoCore Contribution
On Fri, Jun 08, 2018 at 05:34:20PM +0200, Marcin Wojtas wrote:
> This patch introduces new library callback (ArmadaSoCDescI2cGet ()),
> which dynamically allocates and fills MV_SOC_I2C_DESC structure with
> the SoC description of I2c controllers.
>
> Contributed-under: TianoCore Contribution
On Fri, Jun 08, 2018 at 05:34:17PM +0200, Marcin Wojtas wrote:
> Introduce new callback that can provide information
> about MDIO controllers to the Mdio driver.
>
> Extend ArmadaBoardDescLib with new structure MV_BOARD_MDIO_DESC,
> for holding board specific data.
>
> Contributed-under:
1 - 100 of 128 matches
Mail list logo
