On 2023-09-19 13:03, Marcin Juszkiewicz wrote:
W dniu 18.09.2023 o 13:35, Leif Lindholm pisze:
On Mon, Sep 18, 2023 at 13:03:12 +0200, Marcin Juszkiewicz wrote:
There are some changes in progress which make BL1 bigger than 0x8000
which EDK2 uses.
TF-A defines BL1 size to be 0x12000 one. So let follow it.
Signed-off-by: Marcin Juszkiewicz <marcin.juszkiew...@linaro.org>
This fixes a TF-A bug that you uncovered this morning, and I think
that's worth pointing out in the commit message.
However,
Reviewed-by: Leif Lindholm <quic_llind...@quicinc.com>
*But* this is a breaking change SoI want to hold off on merging
this until the TF-A bugfix has been merged, so we can update the
edk2-non-osi binaries at the same time, and minimise the amount of
pain.
Note for the interested:
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/23417
TL;DR: the fip base and bl1 size don't line up. The bl1 size was
already set to sufficient size, but after RME support in TF-A, bl1
size grows beyond start of fip.
TF-A part is now merged.
Excellent!
Could you roll up a new set of binaries for edk2-non-osi?
Then I can merge them at the same time and leave only a minor gap of
brokenness.
/
Leif
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108838): https://edk2.groups.io/g/devel/message/108838
Mute This Topic: https://groups.io/mt/101430708/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe:
https://edk2.groups.io/g/devel/leave/9847357/21656/1706620634/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
