On 22 January 2015 at 14:33, Olivier Martin olivier.martin@arm.com wrote:
I guess the reason why I initially did this 'hack' (mark the DRAM occupied by the FD as non-present) is because the DXE (or something else) was copying over the FD during the dispatching of the UEFI drivers. You might not see this issue with your implementation of MemoryInitPeiLib because UEFI drivers will be loaded way above the FD file. But the risk might still exist - except if the DXE core now takes care of this case.
So which part of the FD file would we still be using at DXE time? And couldn't we use ConvertPages() to turn it into boot services code instead of removing it entirely?
-----Original Message----- From: linaro-uefi-bounces@lists.linaro.org [mailto:linaro-uefi- bounces@lists.linaro.org] On Behalf Of Ard Biesheuvel Sent: 19 January 2015 17:34 To: Varad Gautam Cc: Linaro UEFI Mailman List Subject: Re: [Linaro-uefi] [RFC] arm: efi: handle zImage relocation
On 19 January 2015 at 17:28, Varad Gautam varadgautam@gmail.com wrote:
On 01/19/15 at 05:21 PM Ard Biesheuvel ard.biesheuvel@linaro.org
wrote:
The current implementation fails in `handle_kernel_image()` when
UEFI
finds a discontinuity in the memory map during
`allocate_pages()`[1].
This patch
Footnote?
January/000645.html
The current ARM port in Tianocore does not deal very well with a flash device in RAM. It assumes you are shadowing from flash if it detects that PrePi is running from RAM.
I hit something similar here https://git.linaro.org/people/ard.biesheuvel/uefi- next.git/commit/470ecd1480880a80bbb29077a22a3e640d9633f7
So how do you load the UEFI image?
Linaro-uefi mailing list Linaro-uefi@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-uefi