Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Which OE branch for beagleboard?
Date: Sat, 31 Jul 2010 14:08:44 +0200	[thread overview]
Message-ID: <i313oc$el$1@dough.gmane.org> (raw)
In-Reply-To: <1E016302-3017-40E6-9999-2A5DF47AF1F8@mac.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 31-07-10 12:58, Elvis Dowson wrote:
> 
> On Jul 31, 2010, at 1:50 PM, Koen Kooi wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 31-07-10 11:46, Elvis Dowson wrote:
>>> Hi, 
>>>        Which OE branch should I use to build angstrom images for the beagleboard?
>>
>>
>> Use http://gitorious.org/angstrom/angstrom-setup-scripts [1], that will
>> setup the right branch and bitbake for you.
>>
> 
> I've been working on the overo till now, and switching to beagleboard, there used to be a linux-omap3-2.6.xx series, but I don't see the omap3 linux recipes anymore. 
> 
> http://git.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux
> 
> Have they been replaced?
> 
> Which recipe would now how the correct omap3 recipe for beagle board with a TI OMAP 3530 processor?

'virtual/kernel' was, is and always will be the correct kernel for your
machines.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMVBJMMkyGM64RGpERAtK1AKC1sOuE4JZCiqYwG5ypwCcKpY2SKQCgkss7
mbcMuOxhpKrpzb5MPzhyBTg=
=3hK6
-----END PGP SIGNATURE-----




      reply	other threads:[~2010-07-31 12:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-31  9:46 Which OE branch for beagleboard? Elvis Dowson
2010-07-31  9:50 ` Koen Kooi
2010-07-31 10:58   ` Elvis Dowson
2010-07-31 12:08     ` Koen Kooi [this message]

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='i313oc$el$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@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