All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: the oe-core layer <openembedded-core@lists.openembedded.org>, Patches
Subject: Re: [RFC] U-Boot Recipes
Date: Fri, 01 Mar 2013 14:42:41 +0000	[thread overview]
Message-ID: <1362148961.1055.57.camel@ted> (raw)
In-Reply-To: <CADkTA4PcJitHND_Nj2vD3tDSHk11eeN-w7uWqBQ9Yht1fp3C7g@mail.gmail.com>

On Fri, 2013-03-01 at 08:33 -0500, Bruce Ashfield wrote:
> On Fri, Mar 1, 2013 at 6:47 AM, Jack Mitchell <ml@communistcode.co.uk> wrote:
> > Today I was building an image for the beaglebone with oe-core +
> > meta-beagleboard. meta-beagleboard pretty much provides the machine
> > definition and the kernel. In order to build the correct u-boot (2013.01+) I
> > had to add u-boot 2013.01 to oe-core. Whilst during this I noticed the mess
> > that the u-boot directory had become, I think we need to have a show of
> > hands who uses what u-boot recipes and can they migrate to newer (common)
> > versions.
> 
> The mpc8315e-rdb reference uses v2012.04, and a quick survey didn't turn up
> any other explicit preferred versions in the layers that I have around my
> development machine.
> 
> So for now v2012.04 needs to stay, but as we bump that board to the 3.8 kernel,
> we can give another bootloader a test run.
> 
> >
> > When I submit a patch to get 2013.01 supported, that would make 4 different
> > releases of u-boot; which seems a bit excessive.
> 
> Most releases that I've ever used have kept compatibility fairly well, so I'm
> all for keeping the number of active versions to a minimum. I'd say three is
> a good number, since that matches the number of active kernel versions in
> oe-core as well.

I think one u-boot would be nice. Lets see if we can bump up the
mpc8315e-rdb version...

Cheers,

Richard




  reply	other threads:[~2013-03-01 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01 11:47 [RFC] U-Boot Recipes Jack Mitchell
2013-03-01 13:33 ` Bruce Ashfield
2013-03-01 14:42   ` Richard Purdie [this message]
2013-03-01 14:53     ` Bruce Ashfield

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=1362148961.1055.57.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.