Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: [RFC] U-Boot Recipes
Date: Fri, 01 Mar 2013 11:47:21 +0000	[thread overview]
Message-ID: <51309549.8010502@communistcode.co.uk> (raw)

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.

When I submit a patch to get 2013.01 supported, that would make 4 
different releases of u-boot; which seems a bit excessive.

Thoughts?

-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--




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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01 11:47 Jack Mitchell [this message]
2013-03-01 13:33 ` [RFC] U-Boot Recipes Bruce Ashfield
2013-03-01 14:42   ` Richard Purdie
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=51309549.8010502@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --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