All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: James Abernathy <jfabernathy@gmail.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>, yocto@yoctoproject.org
Subject: Re: meta-ti?????
Date: Fri, 23 Dec 2011 08:26:38 -0500	[thread overview]
Message-ID: <4EF4818E.5050203@balister.org> (raw)
In-Reply-To: <B65605DA-ADD9-4EBB-956A-6C785B5F204E@gmail.com>

On 12/23/2011 08:10 AM, James Abernathy wrote:
> 
> On Dec 23, 2011, at 3:50 AM, Koen Kooi wrote:
> 
>>
>> Op 23 dec. 2011, om 09:37 heeft Paul Eggleton het volgende geschreven:
>>
>>> On Friday 23 December 2011 09:28:31 Koen Kooi wrote:
>>>> Op 22 dec. 2011, om 16:06 heeft Jim Abernathy het volgende geschreven:
>>>>> I know the examples in the documentation of Yocto use meta-intel a lot
>>>>> to get the board specific BSPs like meta-crownbay or meta-n450.
>>>>>
>>>>> Is there a meta-ti or similar that gets you the meta-beagleboard and
>>>>> meta-pandaboard?  If not how do you clone and checkout the pandaboard
>>>>> BPS?
>>>> http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/
>>>>
>>>> It has a README in there on how to set it up, read it and follow it
>>>> precisely.
>>>
>>> Just out of interest, why does meta-texasinstruments depend on meta-angstrom?
>>
>> It needs extra things in overrides and reuses tasks from there.
> 
> Sorry for the follow-up, but if I clone the meta-texasinstruments bsp repository and checkout the pandaboard-rework branch,
> how does that relate to the Yocto branch/bsp yocto/standard/pandaboard on the Yocto site?
> 
> Being a Yocto newbie, it's hard enough to understand all the branches on the yocto site. Relating the meta-angstrom is confusing.
> 
> The light bulb has now gone on yet :-)

I would guess the panda support in the Yocto BSP branch are there to
show Yocto (a word with many different meanings to different people) can
build stuff for non-Intel hardware. However if I were building for a
Panda, I would use the meta-texas-instruments stuff because I would
expect it to support all the bits of hardware (3D etc) available on the
Pandaboard.

The Panda and Beagleboards are readily available so they make good
demonstration cases for BSP's, but enabling all the features on these
SoC's is a lot more work.

Philip


  parent reply	other threads:[~2011-12-23 13:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-22 15:06 meta-ti????? Jim Abernathy
2011-12-22 15:08 ` meta-ti????? Chris Larson
2011-12-23  8:28 ` meta-ti????? Koen Kooi
2011-12-23  8:37   ` meta-ti????? Paul Eggleton
2011-12-23  8:50     ` meta-ti????? Koen Kooi
2011-12-23 13:10       ` meta-ti????? James Abernathy
2011-12-23 13:23         ` meta-ti????? Koen Kooi
2011-12-23 13:43           ` meta-ti????? Paul Eggleton
2011-12-23 15:01             ` meta-ti????? Philip Balister
2011-12-23 13:26         ` Philip Balister [this message]
2011-12-23 17:10         ` meta-ti????? Bruce Ashfield
2011-12-23 17:38           ` meta-ti????? Philip Balister
2011-12-23 17:45             ` meta-ti????? Bruce Ashfield
2011-12-23 17:52               ` meta-ti????? Koen Kooi
2011-12-23 17:59                 ` meta-ti????? Bruce Ashfield
2012-01-04  5:15                   ` meta-ti????? Khem Raj
2012-01-04  5:17                     ` meta-ti????? 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=4EF4818E.5050203@balister.org \
    --to=philip@balister.org \
    --cc=jfabernathy@gmail.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=yocto@yoctoproject.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.