From: Andrew Davis <afd@ti.com>
To: Simon Glass <sjg@chromium.org>,
U-Boot Mailing List <u-boot@lists.denx.de>
Cc: U-Boot Custodians <u-boot-custodians@lists.denx.de>,
Quentin Schulz <quentin.schulz@cherry.de>,
Neha Malcom Francis <n-francis@ti.com>
Subject: Re: Binman and blobs
Date: Tue, 3 Mar 2026 14:03:37 -0600 [thread overview]
Message-ID: <233a88cd-c83f-4e72-ac54-fa773b60ff20@ti.com> (raw)
In-Reply-To: <CAFLszTgrGjthPK8uxD0fErNfgaGYawiv6ojF42sakLj7oVejQg@mail.gmail.com>
On 3/3/26 9:14 AM, Simon Glass wrote:
> Hi,
>
> At present binman handles finding/building tools needed to build images.
>
> There is no equivalent mechanism for the firmware blobs themselves.
> Users must manually obtain these and point binman at them.
>
> This is quite painful at present. Each board requires some splunking,
> reading vendor documentation, etc.
>
If the pain is in finding/collecting these blobs, then would this be
solved better by having a single location for vendors to host their
blobs?
If we had one repo that we could point BINMAN_DIR to, and the existing
"filename" properties would resolve and produce a working bootloader,
would that fix much of the issue?
https://www.youtube.com/watch?v=iz7l9On8qik
Andrew
> I believe we could create a similar setup for blobs, where they are
> described in the image description (compatible string) and there is a
> way to build them, download them, etc.
>
> What do people think?
>
> Regards,
> Simon
prev parent reply other threads:[~2026-03-03 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 15:14 Binman and blobs Simon Glass
2026-03-03 15:51 ` Tom Rini
2026-03-03 16:47 ` Quentin Schulz
2026-03-03 20:03 ` Andrew Davis [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=233a88cd-c83f-4e72-ac54-fa773b60ff20@ti.com \
--to=afd@ti.com \
--cc=n-francis@ti.com \
--cc=quentin.schulz@cherry.de \
--cc=sjg@chromium.org \
--cc=u-boot-custodians@lists.denx.de \
--cc=u-boot@lists.denx.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