From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>,
Marco Felsch <m.felsch@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Yocto migration meta-barebox -> walnascar
Date: Tue, 6 Jan 2026 12:33:21 +0100 [thread overview]
Message-ID: <e31c674b-8d63-42bc-bd54-bcb9c7b5b92d@pengutronix.de> (raw)
In-Reply-To: <aVzgGHbZipXS7kWr@hephaistos>
Hello Konstantin,
On 1/6/26 11:12 AM, Konstantin Kletschke wrote:
> On Tue, Jan 06, 2026 at 10:52:53AM +0100, Marco Felsch wrote:
>
>> Which barebox version do you use?
>
> It should be 2025.02.0.
> I switched to walnascar and this should be the part used:
> https://git.yoctoproject.org/poky/tree/meta/recipes-bsp/barebox?h=walnascar
>
>> Ahmad added the support for a single barebox binary:
>> - https://lore.barebox.org/barebox/20250422052635.3423961-1-a.fatoum@pengutronix.de/
>>
>> IIRC the purpose of the patchset was exactly to fulfill an easier Yocto
>> integration since the beaglebone is one of the oe-core real test hw.
>
> That's is very interesting.
> What I did not get, yet:
> So we can keep our partition scheme, the CPUs bootloader is searching
> hardcoded for partition table -> first vfat -> MLO.
> Then barebox-am33xx-beaglebone.img is put there as MLO?
When enabled, the same barebox build generates two images:
barebox-am33xx-beaglebone-mlo.mmc.img -> MLO
barebox-am33xx-beaglebone.img -> barebox.bin
Both are placed in the VFAT.
>> Since the single image approach targets only the SD/MMC boot, the
>> standalone MLO image should be still possible.
I didn't test it on eMMC and I suspect it needs light tweaking to work
there. If you are happy to test, I can find some time later to send a patch.
> Can this be switched on/off somewere in the yocto framework so the old
> MLO/barebox.bin pair is genereated?
For your old setup, you will need two recipes. Just define your own
barebox.bb and barebox-pbl.bb recipes and inherit barebox in each and
use different configs. All the core logic is in a barebox.bbclass to
allow you to easily create your own recipes.
This allows you also to use a newer version than v2025.02.0 for example
v2025.09.1, which is going to be maintained for longer than just a month.
Cheers,
Ahmad
>
> Regards
> Konstantin
>
>
--
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 |
next prev parent reply other threads:[~2026-01-06 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 9:28 Konstantin Kletschke
2026-01-06 9:52 ` Marco Felsch
2026-01-06 10:12 ` Konstantin Kletschke
2026-01-06 11:33 ` Ahmad Fatoum [this message]
2026-01-06 13:10 ` Konstantin Kletschke
2026-01-06 13:23 ` 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=e31c674b-8d63-42bc-bd54-bcb9c7b5b92d@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=konstantin.kletschke@inside-m2m.de \
--cc=m.felsch@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