From: Marco Felsch <m.felsch@pengutronix.de>
To: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>
Cc: barebox@lists.infradead.org
Subject: Re: Yocto migration meta-barebox -> walnascar
Date: Tue, 6 Jan 2026 10:52:53 +0100 [thread overview]
Message-ID: <20260106095253.souvmkzvzufrkecv@pengutronix.de> (raw)
In-Reply-To: <aVzVyOKQ-mc4LLBd@hephaistos>
Hi Konstantin,
On 26-01-06, Konstantin Kletschke wrote:
> Dear barebox people,
> Happy New Year everybody :-)
Thanks, happy new year to you too :)
> I used up until scarthgap https://github.com/menschel-d/meta-barebox
>
> In our meta layer we have config in distro conf like this:
>
> ABREBOX_CONFIG:beaglebone-yocto = "omap_defconfig"
> BAREBOX_CONFIG:pn-barebox-pbl:beaglebone-yocto = "am335x_mlo_defconfig"
> BAREBOX_IMAGE_SRC:beaglebone-yocto = "images/barebox-am33xx-beaglebone.img"
> BAREBOX_IMAGE_SRC:pn-barebox-pbl:beaglebone-yocto = "images/barebox-am33xx-beaglebone-mlo.img"
> RDEPENDS:barebox:beaglebone-yocto += "barebox-pbl"
> COMPATIBLE_MACHINE:pn-barebox:beaglebone-yocto = "beaglebone-yocto"
> COMPATIBLE_MACHINE:pn-barebox-pbl:beaglebone-yocto = "beaglebone-yocto"
> PREFERRED_PROVIDER_virtual/bootloader = "barebox"
>
> And a append recipe mainly with patches creating our custom
> configuration.
>
> Now I learned, barebox went into openembedded-core, this is great news!
>
> I ditched the meta-barebox, tried my best, needed to remove alle configs
> regarding "-pbl" and compiled:
> ERROR: Nothing RPROVIDES 'barebox-pbl'
> (but /home/konsti/Melitta/scarthgap/meta/recipes-bsp/barebox/barebox.bb
> RDEPENDS on or otherwise requires it)
Which barebox version do you use?
> Now I get several ~580kB img files in the deployment images directory,
> "ours" seems to be barebox-am33xx-beaglebone.img. File size is plausible
> for the ex barebox.bin and strings suggest our insidem2m stuff to
> boot/tftp/nfs landed up in it.
>
> Where is the MLO part? Is barebox-am33xx-beaglebone.img the 1:1
> barebox.bin equivalent?
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.
> We are used to create a partition table, first partition is vfat type
> 0x0c, MLO and barebox.bin are put there, works.
Since the single image approach targets only the SD/MMC boot, the
standalone MLO image should be still possible.
Regards,
Marco
>
> Kind Regards
> Konstantin Kletschke
>
>
> --
> 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
>
>
>
--
#gernperDu
#CallMeByMyFirstName
Pengutronix e.K. | |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
next prev parent reply other threads:[~2026-01-06 9:53 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 [this message]
2026-01-06 10:12 ` Konstantin Kletschke
2026-01-06 11:33 ` Ahmad Fatoum
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=20260106095253.souvmkzvzufrkecv@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=konstantin.kletschke@inside-m2m.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