mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Sascha Hauer" <s.hauer@pengutronix.de>
To: "Alexander Shiyan" <eagle.alexander923@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: v2026.05.0
Date: Wed, 20 May 2026 06:21:50 +0000	[thread overview]
Message-ID: <E1wPaJS-00000001yEr-2gmZ@pty.whiteo.stw.pengutronix.de> (raw)
In-Reply-To: <CAP1tNvQNpjt4e2AhwTPoMKM0E9gra__3feFdczhvVWTc6e_4CA@mail.gmail.com>

Hi Alexander,

On 2026-05-20 08:15, Alexander Shiyan wrote:
> Hello Sascha.
> 
> The first launch of the new release has failed.
> On the RK3568 platform, BL31 does not start. The size of the final
> binary has decreased from 1.5 MB
> to 930 KB - possibly due to the announced compression, but it seems to
> me that this is too
> large a reduction...
> Are there any additional settings/calls required for custom boards in
> the new release?

No board level adjustments required. I just re-tested the relase on a
Rock-3a board using rockchip_v8_defconfig. It works here.

The size reduction depends on the size of your firmware binaries. You
could look at the firmware/*.z files and compare with the original files
to see if that explains the size reduction. The TF-A and OP-TEE files
that I use only have around 700KiB in total, so a size reduction of
600KiB would be unreasonable in my case.

Do you have any console output to share?

Sascha

--
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2026-05-20  6:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19 19:34 v2026.05.0 Sascha Hauer
2026-05-20  5:15 ` v2026.05.0 Alexander Shiyan
2026-05-20  6:21   ` Sascha Hauer [this message]
2026-05-20 11:16     ` v2026.05.0 Alexander Shiyan
2026-05-20 12:40       ` v2026.05.0 Sascha Hauer
2026-05-20 12:11     ` v2026.05.0 Alexander Shiyan
2026-05-20 13:17       ` v2026.05.0 Sascha Hauer
2026-05-20 13:27         ` v2026.05.0 Alexander Shiyan
2026-05-20 13:38           ` v2026.05.0 Ahmad Fatoum
2026-05-20 13:42             ` v2026.05.0 Alexander Shiyan
2026-05-20 13:43               ` v2026.05.0 Ahmad Fatoum
2026-05-20 13:47                 ` v2026.05.0 Alexander Shiyan
2026-05-22 11:00           ` v2026.05.0 Ahmad Fatoum

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1wPaJS-00000001yEr-2gmZ@pty.whiteo.stw.pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=eagle.alexander923@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox