Re: meta-ti?????

[Bruce Ashfield <bruce.ashfield@windriver.com>]

On 11-12-23 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?

I'll jump into the middle of the thread, and answer a couple of specific
questions and leave the larger what depends on what, and where
things evolve and why .. for another day.

The yocto/standard/pandaboard in the 3.0 kernel tree is the refresh/update
of a reference BSP for the 3.0 (and newer) kernel(s).

But what you are seeing ,in the linux-yocto kernel tree, is a work in
progress at the moment, since there is an associated layer that is a
combo layer, and uses the layer tooling to build on top work that has
already been done by TI and other distro layers.

Since, as already been covered in this thread, there (often) multiple
places support for any  given board can be found. What you use, all
depends on what you are looking for.

The linux-yocto variant is built/tested with a yocto + oe-core base
and receives updates of features/fixes that other BSPs in the tree
gets. (note: I'm not claiming this is unique, just that it is done
using the yocto kernel tooling ). A common set of features and docs
would accompany any related BSPs. In this case, the BSP was contributed
to the project on the 3.0 kernel, so I merged it into the tree to
have that integrated support with as few layers as possible.

If you want the angstrom/TI pandaboard, doing what Koen suggests is
the ticket. Look at those layers, follow their READMEs and you'll be
good to go.

Cheers,

Bruce



>
> 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 :-)
>
> Jim A
>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto