mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: "open list:BAREBOX" <barebox@lists.infradead.org>
Subject: Re: [PATCH v2 18/22] ARM: beagleplay: add binary files
Date: Tue, 7 Jan 2025 08:44:00 +0100	[thread overview]
Message-ID: <Z3zbQOQ80tSMLmT8@pengutronix.de> (raw)
In-Reply-To: <eb9a9d27-ca97-4bc5-b7c3-b6f4ea37b3b6@pengutronix.de>

On Mon, Jan 06, 2025 at 03:33:16PM +0100, Ahmad Fatoum wrote:
> Hello Sascha,
> 
> On 06.01.25 14:47, Sascha Hauer wrote:
> > These files are generated from yaml files in U-Boot. Ideally we would
> > use these yaml files and convert them ourselves, but for now just use
> > the binary files and leave the conversion for later patches.
> > 
> 
> What do these blobs do?

They contain various configuration options evaluated by the ROM.
There are four yaml files: board-cfg.yaml, pm-cfg.yaml, rm-cfg.yaml and
sec-cfg.yaml. An example board-cfg.yaml looks like this:

board-cfg:
    rev:
        boardcfg_abi_maj: 0x0
        boardcfg_abi_min: 0x1
    control:
        subhdr:
            magic: 0xC1D3
            size: 7
        main_isolation_enable: 0x5A
        main_isolation_hostid: 0x2
    secproxy:
        subhdr:
            magic: 0x1207
            size: 7
        scaling_factor: 0x1
        scaling_profile: 0x1
        disable_main_nav_secure_proxy: 0
    msmc:
        subhdr:
            magic: 0xA5C3
            size: 5
        msmc_cache_size: 0x0
    debug_cfg:
        subhdr:
            magic: 0x020C
            size: 8
        trace_dst_enables: 0x00
        trace_src_enables: 0x00

These files are loaded and evaluated against a schema and then
serialized. The yaml files are added for each board in U-Boot, many of
them are identical and hardly ever touched once added to the U-Boot
tree.

I haven't yet found any TI documentation about the binaries.

> 
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > ---
> >  arch/arm/boards/beagleplay/combined-dm-cfg.bin    | Bin 0 -> 1346 bytes
> >  arch/arm/boards/beagleplay/combined-sysfw-cfg.bin | Bin 0 -> 1740 bytes
> >  2 files changed, 0 insertions(+), 0 deletions(-)
> > 
> > diff --git a/arch/arm/boards/beagleplay/combined-dm-cfg.bin b/arch/arm/boards/beagleplay/combined-dm-cfg.bin
> > new file mode 100644
> > index 0000000000..83fb5ee925
> > Binary files /dev/null and b/arch/arm/boards/beagleplay/combined-dm-cfg.bin differ
> > diff --git a/arch/arm/boards/beagleplay/combined-sysfw-cfg.bin b/arch/arm/boards/beagleplay/combined-sysfw-cfg.bin
> > new file mode 100644
> > index 0000000000..25f35d46ce
> > Binary files /dev/null and b/arch/arm/boards/beagleplay/combined-sysfw-cfg.bin differ
> 
> We haven't had any binary files in barebox' git so far. Do we want to start now?
> 
> Can we make these firmware/ blobs, until the YAML tooling is imported?

By that you mean just move them from the board directory to firmware/ or
something else?

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:[~2025-01-07  7:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-06 13:46 [PATCH v2 00/22] ARM: K3: Add R5 boot support Sascha Hauer
2025-01-06 13:46 ` [PATCH v2 01/22] ARM: add ARMv7R MPU support Sascha Hauer
2025-01-06 13:46 ` [PATCH v2 02/22] lib/rationale: compile for pbl Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 03/22] DDR: Add k3 DDR driver Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 04/22] ARM: move ARM_CPU_PART_* defines to header Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 05/22] nommu_v7_vectors_init: disable for r5 Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 06/22] clocksource: timer-ti-dm: add support for K3 SoCs Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 07/22] ARM: K3: mount /boot even with env handling disabled Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 08/22] clk: add K3 clk driver Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 09/22] pmdomain: add K3 driver Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 10/22] rproc: add K3 arm64 rproc driver Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 11/22] ARM: k3: add k3_debug_ll_init() Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 12/22] ARM: K3: use debug_ll code for regular PBL console Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 13/22] elf: use iomem regions as fallback when loading to non-sdram memory Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 14/22] rproc: add K3 system_controller Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 15/22] firmware: ti_sci: add function to get global handle Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 16/22] ARM: k3: Add initial r5 support Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 17/22] ARM: k3: Add k3img tool Sascha Hauer
2025-01-06 14:34   ` Ahmad Fatoum
2025-01-06 13:47 ` [PATCH v2 18/22] ARM: beagleplay: add binary files Sascha Hauer
2025-01-06 14:33   ` Ahmad Fatoum
2025-01-07  7:44     ` Sascha Hauer [this message]
2025-01-06 13:47 ` [PATCH v2 19/22] ARM: beagleplay: add Cortex-R5 boot support Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 20/22] Documentation: add build documentation for TI K3 SoCs Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 21/22] ARM: am625: disable secondary watchdogs Sascha Hauer
2025-01-06 13:47 ` [PATCH v2 22/22] mci: am654-sdhci: Use PIO for small transfers Sascha Hauer

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=Z3zbQOQ80tSMLmT8@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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