Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: David Vincent <freesilicon@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] barebox: Add recipe
Date: Mon, 28 Jul 2014 11:23:55 +0100	[thread overview]
Message-ID: <1406543035.13346.11.camel@ted> (raw)
In-Reply-To: <1406541304-18741-1-git-send-email-freesilicon@gmail.com>

On Mon, 2014-07-28 at 11:55 +0200, David Vincent wrote:
> barebox (formerly known as u-boot-v2) is a bootloader that inherits the
> best of U-Boot and the Linux kernel. This commit adds the possibility to
> use it as a virtual/bootloader instead of U-Boot.
> 
> Signed-off-by: David Vincent <freesilicon@gmail.com>
> ---
>  meta/recipes-bsp/barebox/barebox.inc          |   73 +++++++++++++++++++++++++
>  meta/recipes-bsp/barebox/barebox_2014.07.0.bb |   15 +++++
>  2 files changed, 88 insertions(+)
>  create mode 100644 meta/recipes-bsp/barebox/barebox.inc
>  create mode 100644 meta/recipes-bsp/barebox/barebox_2014.07.0.bb

I have to admit I don't know a lot about this. To make it into OE-Core
we need some kind of story about why its necessary and commonly used.
Are there a number of BSPs using this? Can you give some background to
why this is needed?

Cheers,

Richard



  reply	other threads:[~2014-07-28 10:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-28  9:55 [PATCH] barebox: Add recipe David Vincent
2014-07-28 10:23 ` Richard Purdie [this message]
     [not found]   ` <CAKRNOGwGr3BM8FTMoqjNQ+p0tFKUj55RdyL+0wemf_7f1r1UcQ@mail.gmail.com>
2014-07-28 12:02     ` David Vincent
2014-07-30 11:46   ` Stefan Müller-Klieser
2014-07-30 16:56     ` Khem Raj
2014-07-28 11:58 ` Eric Bénard
2014-07-28 12:15   ` David Vincent
2014-07-28 14:42     ` Eric Bénard
2014-07-30  9:40       ` David Vincent

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=1406543035.13346.11.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=freesilicon@gmail.com \
    --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