Bug#1118651: cpp-15-aarch64-linux-gnu: Build failure of TF-A for rk3328/rk3399 since TF-A commit 6c2e5bf68955

--efdd75a6fbe9a5e59a37aea0a339240b1190fa6d113881d67efb0548bc85
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8

On Fri Jun 5, 2026 at 4:10 PM CEST, Lennart Sorensen wrote:
> On Fri, Jun 05, 2026 at 10:30:01AM +0200, Diederik de Haas wrote:
>> Thanks a lot for your input :-)
>>=20
>> It is VERY likely my bisect operation was done only wrt RK3328.
>
> I haven't found any commit (by trying some random ones for the past coupl=
e
> of years) that built.  Of course I suspect it is the linker not aggreeing
> with something in the ld.S script, but I have no experience with those.
> It looks like it isn't placing .text in the location the ld.S has
> *(.text*), but rather defaults to putting it at 0 which is where the
> reserved area is placed too for the isr_vectors.

New proposal in the upstream TF-A repo:
https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/53010
"fix(build): fix misapplication of errata A53 843419"

I have confirmed this fixes the build issue wrt RK3328.
The issue I mentioned in #46 with RK3399 is still present though.

--efdd75a6fbe9a5e59a37aea0a339240b1190fa6d113881d67efb0548bc85
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCamyAeQAKCRDXblvOeH7b
bte3AP4l26hn1ljV4sEtf4Ne8Lfg89WVBUsVigDDStbMk5ZsZAD+JAsU0tYwtMIP
6IzPwikcZsXWHqPgIz2CrIgl0MDAIAo=
=qodI
-----END PGP SIGNATURE-----

--efdd75a6fbe9a5e59a37aea0a339240b1190fa6d113881d67efb0548bc85--