mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: "Richard Purdie" <richard.purdie@linuxfoundation.org>,
	"Enrico Jörns" <ejo@pengutronix.de>,
	"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 14:43:45 +0100	[thread overview]
Message-ID: <CANNYZj8_RkjMASpozi+oSu3XOHCW04n9YUC5UgHKy+2vm=cDrQ@mail.gmail.com> (raw)
In-Reply-To: <CAP9ODKokQpGL3ttukqRaq3-8m0ci7qp8mckbgudGJx1HOu-fPw@mail.gmail.com>

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.

Alex



  parent reply	other threads:[~2023-02-15 13:45 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 [this message]
2023-02-15 13:49           ` Enrico Jörns
2023-02-15 13:53           ` Otavio Salvador
2023-02-15 14:06             ` Enrico Jörns
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='CANNYZj8_RkjMASpozi+oSu3XOHCW04n9YUC5UgHKy+2vm=cDrQ@mail.gmail.com' \
    --to=alex.kanavin@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=ejo@pengutronix.de \
    --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