Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Stefan Müller-Klieser" <s.mueller-klieser@phytec.de>
To: openembedded-core@lists.openembedded.org
Subject: [RFC 0/1] add support for the barebox bootloader
Date: Wed, 30 Jul 2014 13:48:05 +0200	[thread overview]
Message-ID: <53D8DB75.2030407@phytec.de> (raw)

I would be happy about comments on our barebox recipe and provide a 
story for it to be moved into OE-core:

The barebox is a bootloader created by and for kernel developers. Its 
system design and user interface is kept in close relation to the linux 
kernel. It has support for arm/blackfin/mips/ppc/x86... Most of the 
supported boards are current arm SoCs. As seen on
https://www.openhub.net/p/barebox
the community is very active with 1801 commits from 66 contributors in 
the last year (u-boot:3547/319). It gets maintained by pengutronix a big 
linux kernel contributor from Germany.
Currently, as far as I can see, only freescale supports barebox in the 
meta-fsl-arm bsp layer. As barebox is used by many arm SoC board 
vendors, e.g. we here at phytec.de use barebox, the missing support in 
OE-core could be one reason to see few public bsp layers to be pushed. 
Its the most crucial part of the bsp. We maintain our own version of the 
barebox recipe at the moment. It would be helpful to see it becoming 
mainline in OE-core as this could create some traction towards including 
barebox support in more bsp layers, as a lot of machines are supported 
by barebox.
Maybe there is a better place to put it in, or a better way of 
implementing it, as David already said.
Anyway, I hope this recipe will be helpful for someone.

Regards, Stefan


                 reply	other threads:[~2014-07-30 11:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=53D8DB75.2030407@phytec.de \
    --to=s.mueller-klieser@phytec.de \
    --cc=openembedded-core@lists.openembedded.org \
    /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