Update arm-trusted-firmware to 2.9

  • Done
  • quality assurance status badge
Details
2 participants
  • Efraim Flashner
  • Vagrant Cascadian
Owner
unassigned
Submitted by
Vagrant Cascadian
Severity
normal
V
V
Vagrant Cascadian wrote on 18 Jun 2023 05:47
(address . guix-patches@gnu.org)
87wn01a0t6.fsf@wireframe
The attached patch updates arm-trusted-firmware to 2.9.

I was able to rebuild all the dependent u-boot-* packages!

Unfortunately, arm-trusted-firmware-imx8mq no longer builds, ending with
the error:

aarch64-linux-gnu-ld.bfd: /tmp/guix-build-arm-trusted-firmware-imx8mq-2.9.drv-0/source/build/imx8mq/release/bl31/bl31.elf section `.xlat_table' will not fit in region `RAM'
aarch64-linux-gnu-ld.bfd: BL31 image has exceeded its limit.
aarch64-linux-gnu-ld.bfd: region `RAM' overflowed by 20480 bytes

Upstream has essentially abandoned this target due to tight size
contraints for imx8mq, though there is a maintained vendor fork based
off of some older version, so either we need to freeze this at 2.8 or
use the vendor fork or maybe drop it entirely. I do not believe
arm-trusted-firmware-imx8mq is used by any other guix packages...

... thoughts?


live well,
vagrant
From 3e41d1cf2753757b45b81d75cd406c6fe0c5232b Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagrant@debian.org>
Date: Sat, 17 Jun 2023 20:14:17 -0700
Subject: [PATCH] gnu: arm-trusted-firmware: Update to 2.9.

* gnu/packages/firmware.scm (make-arm-trusted-firmware): Update to 2.9.
---
gnu/packages/firmware.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Toggle diff (26 lines)
diff --git a/gnu/packages/firmware.scm b/gnu/packages/firmware.scm
index c7ca81c35a..04c9c7b580 100644
--- a/gnu/packages/firmware.scm
+++ b/gnu/packages/firmware.scm
@@ -1025,7 +1025,7 @@ (define* (make-arm-trusted-firmware platform
(gnu-triplet->nix-system triplet))))))
(package
(name (string-append "arm-trusted-firmware-" platform))
- (version "2.8")
+ (version "2.9")
(source
(origin
(method git-fetch)
@@ -1036,7 +1036,7 @@ (define* (make-arm-trusted-firmware platform
(file-name (git-file-name "arm-trusted-firmware" version))
(sha256
(base32
- "0grq3fgxi9xhcljnhwlxjvdghyz15gaq50raw41xy4lm8rkmnzp3"))
+ "16fjbn1zck0d8b554h8lk1svqqn0zlawvrlkjxry9l71s9h4vd0p"))
(snippet
#~(begin
(use-modules (guix build utils))

base-commit: 428b810ca23fa1c1c565da15c0e95273f6487384
--
2.39.2
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCZI5+ZQAKCRDcUY/If5cW
qlf6AP9nk9zUddn5IQZoT41ZSadtD5GpOUTSZtp98vT3xIo8QAEA41JHm4GjSShv
RKYuBMxeug7I/2OdntPoYlpNb1SHYAE=
=FcHt
-----END PGP SIGNATURE-----

E
E
Efraim Flashner wrote on 18 Jun 2023 08:59
(name . Vagrant Cascadian)(address . vagrant@debian.org)
ZI6rYPe3QHFeQFRH@3900XT
On Sat, Jun 17, 2023 at 08:47:49PM -0700, Vagrant Cascadian wrote:
Toggle quote (19 lines)
> The attached patch updates arm-trusted-firmware to 2.9.
>
> I was able to rebuild all the dependent u-boot-* packages!
>
> Unfortunately, arm-trusted-firmware-imx8mq no longer builds, ending with
> the error:
>
> aarch64-linux-gnu-ld.bfd: /tmp/guix-build-arm-trusted-firmware-imx8mq-2.9.drv-0/source/build/imx8mq/release/bl31/bl31.elf section `.xlat_table' will not fit in region `RAM'
> aarch64-linux-gnu-ld.bfd: BL31 image has exceeded its limit.
> aarch64-linux-gnu-ld.bfd: region `RAM' overflowed by 20480 bytes
>
> Upstream has essentially abandoned this target due to tight size
> contraints for imx8mq, though there is a maintained vendor fork based
> off of some older version, so either we need to freeze this at 2.8 or
> use the vendor fork or maybe drop it entirely. I do not believe
> arm-trusted-firmware-imx8mq is used by any other guix packages...
>
> ... thoughts?

I tried adjusting the flags to -Oz (not recognized) or -Os and it still
didn't fit. What device(s) use the imx8mq? Is that the chip in the
Librem 5?

I've added some people who might be interested in the chip. I suppose at
first glance I'd prefer using the vendor fork (assuming there's some
form of ongoing maintenance) over keeping the older version.

--
Efraim Flashner <efraim@flashner.co.il> ????? ?????
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAmSOq10ACgkQQarn3Mo9
g1Hd7w//b6l6mfboKbafm+7BuDGEMeZPqkE+wt8hU1Ms+z232/xsrwzz5V/Evbfn
CZu9zxp0OHFsaeaBkcrEMhbi9NZvXP+QthSM/YI+dOTeUTaM6jWz64c6NfvD00vX
Q07P/XiuZorDkNdTbrNz0c/qJFdn/+u/u1hemAladwckHq1M5aOMsK18HFeTn9yB
ZdM6bRuFFfOCpIWmsJCLT9OUSno+t3Bj2QDLnMtxrYDW94hipd0Fsm8okINOChVY
Z7lwRAI5CrRU1i7uwa3nRPfDwlE6niPXtCfMlbAxXJwSzi+AOH8+XqwMl894kS4H
um9W3E6dc/I066otlnoy0W36nHOOb6AljtKMeZR6BCHOxCZarYIVcSdWsf4ikB4P
f9iBwWHThbnhoIA+ycVzutDIV77OwheVy7XRR8DUBm79LXsVcQb/otcdnuSSARne
kfBm1W2ABgnuRpDuUMmmKFA1C6Rzm/+O4RI1tCV4DZV7YIVftOk9JLYhHSF7clcn
SzkcJrEywLveqML6hL+SYU76w0IC7z6PS7pwo/IZBxIyCL90u/walSIj363F7gWG
6djowlMdpgqyBnZMJy5BvcWdqHvQV5CEmZXzKz8z0wPdfhkZfSuQdFpF70G0U+MA
E4t+p2/E86fPcJ3jhKNXgc469oOGAaW4J0tDtL/Qq8AQE5hilxU=
=MIuW
-----END PGP SIGNATURE-----


V
V
Vagrant Cascadian wrote on 18 Jun 2023 09:47
(name . Efraim Flashner)(address . efraim@flashner.co.il)
87r0q99pqh.fsf@wireframe
On 2023-06-18, Efraim Flashner wrote:
Toggle quote (5 lines)
> On Sat, Jun 17, 2023 at 08:47:49PM -0700, Vagrant Cascadian wrote:
>> The attached patch updates arm-trusted-firmware to 2.9.
>>
>> I was able to rebuild all the dependent u-boot-* packages!

Notably, I forgot to mention that I have not boot tested any of them
yet...


Toggle quote (19 lines)
>> Unfortunately, arm-trusted-firmware-imx8mq no longer builds, ending with
>> the error:
>>
>> aarch64-linux-gnu-ld.bfd: /tmp/guix-build-arm-trusted-firmware-imx8mq-2.9.drv-0/source/build/imx8mq/release/bl31/bl31.elf section `.xlat_table' will not fit in region `RAM'
>> aarch64-linux-gnu-ld.bfd: BL31 image has exceeded its limit.
>> aarch64-linux-gnu-ld.bfd: region `RAM' overflowed by 20480 bytes
>>
>> Upstream has essentially abandoned this target due to tight size
>> contraints for imx8mq, though there is a maintained vendor fork based
>> off of some older version, so either we need to freeze this at 2.8 or
>> use the vendor fork or maybe drop it entirely. I do not believe
>> arm-trusted-firmware-imx8mq is used by any other guix packages...
>>
>> ... thoughts?
>
> I tried adjusting the flags to -Oz (not recognized) or -Os and it still
> didn't fit. What device(s) use the imx8mq? Is that the chip in the
> Librem 5?

Librem 5 and MNT Reform are probably the most interesting platforms I am
aware of.


Toggle quote (4 lines)
> I've added some people who might be interested in the chip. I suppose at
> first glance I'd prefer using the vendor fork (assuming there's some
> form of ongoing maintenance) over keeping the older version.

Although imx8mq (at least the platforms I am aware of) all still require
blobs to initialize the DDR, so will likely never fully land in guix
proper (at least at the boot firmware level)... which is why I maybe
learn towards dropping it entirely.


live well,
vagrant
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCZI62dwAKCRDcUY/If5cW
qq4YAP9apGdJs1uPgAB0mCQCJun7BhiMBc/A+3oTWJU6XYDkkgEApzTopXHZ2pBD
HWh3Sx5+X+ioi2PMYtx48fMJCAjcZAM=
=rFWJ
-----END PGP SIGNATURE-----

V
V
Vagrant Cascadian wrote on 20 Jul 2023 08:01
Update U-boot to 2023.07.02, arm-trusted-firmware to 2.9
(name . Maxim Cournoyer)(address . maxim.cournoyer@gmail.com)
87cz0n15r5.fsf@wireframe
On 2023-07-19, Maxim Cournoyer wrote:
Toggle quote (15 lines)
> vagrant@debian.org writes:
>> From: Vagrant Cascadian <vagrant@debian.org>
>>
>> I *think* I have resolved all mentioned issues so far.
>>
>> This series keeps arm-trusted-firmware-imx8mq at 2.8, as it no longer builds.
>>
>> It turns out using the #:config to disable CONFIG_SPL_FIT_SIGNATURE is working
>> after all, so only used that one.
>
> Great!
>
> I haven't been able to apply this series locally, but I've had a glimpse
> and it LGTM. Feel free to push it!

Thanks for the review!

Pushed as:

cf1216d8763adf3c5e9d79d7abd2c5ecc8861d60 gnu: patman: Add python-u-boot-pylib to inputs.
ffbcc113df02293e1676310dbf3bfb23df8cae10 gnu: Add python-u-boot-pylib.
ed5dc3a25d858a394bb7db937a51d866c3cdc6ed gnu: u-boot: Add crust firmware to pinebook, pine64_plus and pine64-lts.
b0d47d9e18e52ff7935aebe6ab37e702f58101be gnu: u-boot: Update to 2023.07.02.
d6a53849935f8584e1df57faa79c18c23fbb2aa1 gnu: arm-trusted-firmware: Update to 2.9.


live well,
vagrant
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCZLjNngAKCRDcUY/If5cW
qg1SAP9weTSy5vSEoB1ymnZcwXElgjL9m68ItfrkubKVx7nviAD/YxOJOsweVTlq
bu2Jq3hBDsuKvexmhw1BVgT/0aj6wwQ=
=ClWQ
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 64142@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 64142
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch