mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Enrico Jörns" <ejo@pengutronix.de>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>,
	Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Marco Felsch <m.felsch@pengutronix.de>,
	openembedded-core@lists.openembedded.org,  yocto@pengutronix.de,
	barebox@lists.infradead.org
Subject: Re: [yocto] [OE-core] [PATCH 1/2] barebox: add initial support
Date: Wed, 15 Feb 2023 15:06:29 +0100	[thread overview]
Message-ID: <45dbf5141a71bc1db6756cfc9df3fb0c0b33b3be.camel@pengutronix.de> (raw)
In-Reply-To: <CAP9ODKqjkCuhyVkfhskOSdF3g57=R9MO6Bcy2R5zBV9fVd6wZQ@mail.gmail.com>

Am Mittwoch, dem 15.02.2023 um 10:53 -0300 schrieb Otavio Salvador:
> Em qua., 15 de fev. de 2023 às 10:44, Alexander Kanavin
> <alex.kanavin@gmail.com> escreveu:
> > On Wed, 15 Feb 2023 at 12:22, Otavio Salvador
> > <otavio.salvador@ossystems.com.br> wrote:
> > > > Fair enough, I'm open to the idea. It would be interesting/useful to
> > > > see if anyone else in the community is in favour of this or not. I'm
> > > > sure you appreciate why we need to ask the question and why we can't
> > > > just add everything! :)
> > > > 
> > > > The community usage does appear to be primarily phytec/ptx.
> > > 
> > > I have used barebox in some projects in the past for multiple customers. It is a solid and
> > > commonly used bootloader. I consider U-Boot the industry standard, but Barebox is also widely
> > > used, and it makes sense to be part of OE-Core.
> > 
> > I do not quite understand why barebox needs to be specifically in
> > oe-core. There's a well maintained layer for it:
> > https://github.com/menschel-d/meta-barebox
> > so once all those meta-phytec recipes are phased out in favour of
> > using that layer, there's no fragmentation.
> 
> I think the Barebox inside OE-Core allows a bigger integration and
> reuse of existing tooling for signing and other classes currently well
> integrated with U-Boot.

Yes, this is another valid point. We have already identified that many things in OE are a bit
tailored to u-boot. Having another option (as one has for x86 with grub anyway) could, especially on
ARM platforms, inspire to make things more generic and probably also create community synergy
effects.

What clearly would not be the intention is to tailor things in oe-core for barebox only.

> For me, a critical point for decision is if
> Pengutronix will commit to support it.

Yes, I stated that this is clearly our intention.
So support isn't only a one-man show at all ;)


Thanks and best regards, Enrico

-- 
Pengutronix e.K.                           | Enrico Jörns                |
Embedded Linux Consulting & Support        | https://www.pengutronix.de/ |
Steuerwalder Str. 21                       | Phone: +49-5121-206917-180  |
31137 Hildesheim, Germany                  | Fax:   +49-5121-206917-9    |




  reply	other threads:[~2023-02-15 14:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230203135011.2061939-1-m.felsch@pengutronix.de>
     [not found] ` <12e370a3183d04572da1c5749d8e64dcf5091a0c.camel@linuxfoundation.org>
2023-02-14  9:46   ` Enrico Jörns
2023-02-14 13:56     ` Richard Purdie
     [not found]       ` <CAP9ODKokQpGL3ttukqRaq3-8m0ci7qp8mckbgudGJx1HOu-fPw@mail.gmail.com>
2023-02-15 13:43         ` Alexander Kanavin
2023-02-15 13:49           ` Enrico Jörns
2023-02-15 13:53           ` Otavio Salvador
2023-02-15 14:06             ` Enrico Jörns [this message]
2023-02-15 14:11             ` Alexander Kanavin
2023-02-15 14:59               ` Otavio Salvador
2023-02-15 15:01               ` Enrico Jörns
2023-02-15 15:12                 ` Alexander Kanavin

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=45dbf5141a71bc1db6756cfc9df3fb0c0b33b3be.camel@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=alex.kanavin@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=m.felsch@pengutronix.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=yocto@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