From: Vagrant Cascadian <vagrant@debian.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: phodina@protonmail.com, 64142@debbugs.gnu.org, ludo@gnu.org,
jonathan.brielmaier@web.de, marius@gnu.org
Subject: [bug#64142] Update arm-trusted-firmware to 2.9
Date: Sun, 18 Jun 2023 00:47:02 -0700 [thread overview]
Message-ID: <87r0q99pqh.fsf@wireframe> (raw)
In-Reply-To: <ZI6rYPe3QHFeQFRH@3900XT>
[-- Attachment #1: Type: text/plain, Size: 1863 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2023-06-18 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 3:47 [bug#64142] Update arm-trusted-firmware to 2.9 Vagrant Cascadian
2023-06-18 6:59 ` Efraim Flashner
2023-06-18 7:47 ` Vagrant Cascadian [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0q99pqh.fsf@wireframe \
--to=vagrant@debian.org \
--cc=64142@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=jonathan.brielmaier@web.de \
--cc=ludo@gnu.org \
--cc=marius@gnu.org \
--cc=phodina@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).