GNU bug report logs - #64142
Update arm-trusted-firmware to 2.9

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 64142 in the body.
You can then email your comments to 64142 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Vagrant Cascadian <vagrant <at> debian.org>
To: guix-patches <at> gnu.org
Cc: ludo <at> gnu.org, efraim <at> flashner.co.il
Subject: Update arm-trusted-firmware to 2.9
Date: Sat, 17 Jun 2023 20:47:49 -0700

[Message part 1 (text/plain, inline)]

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

[0001-gnu-arm-trusted-firmware-Update-to-2.9.patch (text/x-diff, inline)]

From 3e41d1cf2753757b45b81d75cd406c6fe0c5232b Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagrant <at> 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(-)

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

[signature.asc (application/pgp-signature, inline)]

Message #8 received at 64142 <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: Vagrant Cascadian <vagrant <at> debian.org>
Cc: phodina <at> protonmail.com, 64142 <at> debbugs.gnu.org, ludo <at> gnu.org,
 jonathan.brielmaier <at> web.de, marius <at> gnu.org
Subject: Re: Update arm-trusted-firmware to 2.9
Date: Sun, 18 Jun 2023 09:59:44 +0300

[Message part 1 (text/plain, inline)]

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!
> 
> 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 <at> 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

[signature.asc (application/pgp-signature, inline)]

Message #11 received at 64142 <at> debbugs.gnu.org (full text, mbox):

From: Vagrant Cascadian <vagrant <at> debian.org>
To: Efraim Flashner <efraim <at> flashner.co.il>
Cc: phodina <at> protonmail.com, 64142 <at> debbugs.gnu.org, ludo <at> gnu.org,
 jonathan.brielmaier <at> web.de, marius <at> gnu.org
Subject: Re: Update arm-trusted-firmware to 2.9
Date: Sun, 18 Jun 2023 00:47:02 -0700

[Message part 1 (text/plain, inline)]

On 2023-06-18, Efraim Flashner wrote:
> 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...


>> 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. 


> 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

[signature.asc (application/pgp-signature, inline)]

Message #16 received at 64142-done <at> debbugs.gnu.org (full text, mbox):

From: Vagrant Cascadian <vagrant <at> debian.org>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 64149-done <at> debbugs.gnu.org, jonathan.brielmaier <at> web.de, ludo <at> gnu.org,
 efraim <at> flashner.co.il, 64142-done <at> debbugs.gnu.org, marius <at> gnu.org,
 phodina <at> protonmail.com
Subject: Update U-boot to 2023.07.02, arm-trusted-firmware to 2.9
Date: Wed, 19 Jul 2023 23:01:02 -0700

[Message part 1 (text/plain, inline)]

On 2023-07-19, Maxim Cournoyer wrote:
> vagrant <at> debian.org writes:
>> From: Vagrant Cascadian <vagrant <at> 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

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.