From: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Marco Felsch <m.felsch@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: Yocto migration meta-barebox -> walnascar
Date: Tue, 6 Jan 2026 14:10:08 +0100 [thread overview]
Message-ID: <aV0JsI7NisQ3gans@hephaistos> (raw)
In-Reply-To: <e31c674b-8d63-42bc-bd54-bcb9c7b5b92d@pengutronix.de>
Hello Ahmad!
On Tue, Jan 06, 2026 at 12:33:21PM +0100, Ahmad Fatoum wrote:
> 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.
I do not necessaryly need two images, if booting is now done with a
combined one, which is new, if I understood this correct.
In my images deploy dir the following images showed up after my
migration to walnascar away from the meta-barebox layer which is not
used anymore.
barebox-am33xx-afi-gf.img
barebox-am33xx-baltos.img
barebox-am33xx-beaglebone.img
barebox-am33xx-myirtech.img
barebox-am33xx-phytec-phycard.img
barebox-am33xx-phytec-phycore-emmc.img
barebox-am33xx-phytec-phycore-no-eeprom.img
barebox-am33xx-phytec-phycore-no-spi-no-eeprom.img
barebox-am33xx-phytec-phycore-no-spi.img
barebox-am33xx-phytec-phycore.img
barebox-am33xx-phytec-phyflex-no-eeprom.img
barebox-am33xx-phytec-phyflex-no-spi-no-eeprom.img
barebox-am33xx-phytec-phyflex-no-spi.img
barebox-am33xx-phytec-phyflex.img
barebox-am35xx-pfc-750-820x.img
barebox-beagleboard.img
barebox-dt-2nd.img
And that is, when I wondered myself, if - in our case - barebox-am33xx-beaglebone.img
is going to be named MLO and put into the vfat boot partition or if I
have something missing or done wrong, which is absolutely possible, of
course!
So, no *mlo* file.
> 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.
So only using this approach with two barebox.bb and barebox-pbl.bb I
would get an additional *mlo* file, right?
As said, if I can omit this approach this is fine by me.
Regards
Konsti
--
INSIDE M2M GmbH
Konstantin Kletschke
Berenbosteler Straße 76 B
30823 Garbsen
Telefon: +49 (0) 5137 90950136
Mobil: +49 (0) 151 15256238
Fax: +49 (0) 5137 9095010
konstantin.kletschke@inside-m2m.de
http://www.inside-m2m.de
Geschäftsführung: Michael Emmert, Derek Uhlig
HRB: 111204, AG Hannover
next prev parent reply other threads:[~2026-01-06 13:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 9:28 Yocto migration meta-barebox -> walnascar Konstantin Kletschke
2026-01-06 9:52 ` Marco Felsch
2026-01-06 10:12 ` Konstantin Kletschke
2026-01-06 11:33 ` Ahmad Fatoum
2026-01-06 13:10 ` Konstantin Kletschke [this message]
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=aV0JsI7NisQ3gans@hephaistos \
--to=konstantin.kletschke@inside-m2m.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.