mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Sascha Hauer" <s.hauer@pengutronix.de>
To: "Michael Tretter" <m.tretter@pengutronix.de>
Cc: BAREBOX <barebox@lists.infradead.org>,
	Michael Tretter <m.tretter@pengutronix.de>
Subject: Re: [PATCH 00/11] arm: socfpga: agilex5: add xload support for bl33 to FSBL
Date: Tue, 20 Oct 2026 14:30:42 +0000	[thread overview]
Message-ID: <743f8734-e541-48db-8abd-76a79ee5651d@pengutronix.de> (raw)
In-Reply-To: <20261007-socfpga-agilex5-xload-v1-0-f8fb2d2819da@pengutronix.de>

Hi Michael,

On 2026-10-07 12:55, Michael Tretter wrote:
> The image of the first stage boot loader on the Agilex 5 is limited to
> approximately 256k. The SRAM is actually 512k, but there is some handoff
> data at the send of the SRAM, which must not be overridden. There are
> some size checks, but due to compression of the FSBL image, it's the
> possible image size cannot be determined reliably.
> 
> The barebox PBL and a full featured barebox proper are easily larger
> than the allowed size. Compression of the piggy data may even be counter
> productive, since the entire FSBL image is compressed again when
> creating the boot image.
> 
> Add support to remove the piggy data from the FSBL image, and load the
> second stage (consisting of a barebox PBL and barebox proper) from flash
> in the PBL.
> 
> Patches 1-4 rework the Cadence QSPI NOR flash driver to be available in
> the PBL via the pbl_bio abstraction.
> 
> Patches 5-9 extend the Agilex 5 support to initialize the flash driver
> in the PBL and chain load an SSBL as bl33 instead of copying the
> currently running barebox. The patches also add the infrastructure to
> build the PBL without piggy data and device tree.
> 
> Patches 10-11 enable the xload support in the Arrow AXE5 Eagle board.
> 

This series currently breaks compilation on -next. socfpga-agilex5_defconfig
fails with:

../arch/arm/boards/arrow-axe5-eagle/lowlevel.c:17:23: error: 'CONFIG_MACH_SOCFPGA_ARROW_AXE5_EAGLE_XLOAD_ADDR' undeclared here (not in a function); did you mean 'CONFIG_MACH_SOCFPGA_ARROW_AXE5_EAGLE'?
   17 |         .nor_offset = CONFIG_MACH_SOCFPGA_ARROW_AXE5_EAGLE_XLOAD_ADDR,
      |                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                       CONFIG_MACH_SOCFPGA_ARROW_AXE5_EAGLE
../arch/arm/boards/arrow-axe5-eagle/lowlevel.c:18:21: error: 'CONFIG_MACH_SOCFPGA_ARROW_AXE5_EAGLE_XLOAD_SIZE' undeclared here (not in a function); did you mean 'CONFIG_MACH_SOCFPGA_ARROW_AXE5_EAGLE'?
   18 |         .nor_size = CONFIG_MACH_SOCFPGA_ARROW_AXE5_EAGLE_XLOAD_SIZE,
      |                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                     CONFIG_MACH_SOCFPGA_ARROW_AXE5_EAGLE

xload support is currently optional and disabled, the existence of
CONFIG_MACH_SOCFPGA_ARROW_AXE5_EAGLE_XLOAD_ADDR depends on the xload
being enabled, but they are used unconditionally.

Could you send a fixup?

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 |




      parent reply	other threads:[~2026-10-20 14:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 10:55 Michael Tretter
2026-10-07 10:55 ` [PATCH 01/11] mtd: spi-nor: drop requirement for device field Michael Tretter
2026-10-07 10:55 ` [PATCH 02/11] mtd: spi-nor: enable module in PBL Michael Tretter
2026-10-20  7:39   ` [PATCH] fixup! " Sascha Hauer
2026-10-20  9:05     ` Sascha Hauer
2026-10-07 10:55 ` [PATCH 03/11] mtd: spi-nor: cadence: extract common part for use " Michael Tretter
2026-10-07 10:55 ` [PATCH 04/11] mtd: spi-nor: cadence: add a PBL driver Michael Tretter
2026-10-07 10:55 ` [PATCH 05/11] arm: socfpga: agilex5: add bl33 xload support Michael Tretter
2026-10-07 10:55 ` [PATCH 06/11] arm: socfpga: agilex5: separate load and start of bl33 Michael Tretter
2026-10-07 10:55 ` [PATCH 07/11] arm: socfpga: agilex5: enable xload for bl33 Michael Tretter
2026-10-07 10:55 ` [PATCH 08/11] arm: socfpga: agilex5: initialize QSPI flash in PBL Michael Tretter
2026-10-07 12:11   ` Michael Tretter
2026-10-07 10:55 ` [PATCH 09/11] arm: socfpga: agilex5: add agilex5_barebox_entry_xload Michael Tretter
2026-10-07 10:55 ` [PATCH 10/11] arm: socfpga: axe5-eagle: move lowlevel init to separate function Michael Tretter
2026-10-07 10:55 ` [PATCH 11/11] arm: socfpga: axe5-eagle: build FSBL without piggy data Michael Tretter
2026-10-21  8:38   ` [PATCH] fixup! " Michael Tretter
2026-10-19 12:43 ` [PATCH 00/11] arm: socfpga: agilex5: add xload support for bl33 to FSBL Sascha Hauer
2026-10-20 14:30 ` Sascha Hauer [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

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

  git send-email \
    --in-reply-to=743f8734-e541-48db-8abd-76a79ee5651d@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=m.tretter@pengutronix.de \
    /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