Re: building Yocto for Pandaboard

[Gary Thomas <gary@mlbassoc.com>]

On 2012-02-09 10:15, Denys Dmytriyenko wrote:
> On Thu, Feb 09, 2012 at 10:12:21AM -0700, Gary Thomas wrote:
>> On 2012-02-09 09:59, Philip Balister wrote:
>>> On 02/09/2012 08:36 AM, Denys Dmytriyenko wrote:
>>>> On Thu, Feb 09, 2012 at 11:23:14AM -0500, Brian Hutchinson wrote:
>>>>>   On Wed, Feb 8, 2012 at 8:16 PM, William Mills<wmills@ti.com>   wrote:
>>>>>> As Gary said there has not been too many end user questions on meta-ti yet.
>>>>>
>>>>>   All I care about is meta-ti as that is what all our products are based
>>>>>   on. I've been watching subject for a while now trying to discern all
>>>>>   the issues and make a wise choice.
>>>>
>>>> Brian,
>>>>
>>>>>   I'm wanting to switch from Arago to whatever TI supports next as I
>>>>>   supply the rest of our development team with tools and images that
>>>>>   they build applications on for our products and I can't jerk them
>>>>>   around changing distros.
>>>>
>>>> As you are aware, Arago is not going away - there is work going on in
>>>> meta-arago layer to update/port it to the new Yocto infrastructure.
>>>>
>>>> Arago/meta-arago is still going to be the official platform distribution for
>>>> TI SDK products. But, a separate meta-ti layer was created early in the
>>>> process to detach and unify the BSP layer and allow people to use TI hardware
>>>> with different distributions. And that's actually part of the problem, as
>>>> distributions like religions conflict with each other in a single layer... :)
>>>>
>>>
>>> Denys, from my point of view, there are two issues we need to solve:
>>>
>>> 1) Defining the meta-ti toolchain dependencies. Angstrom uses gcc-4.5
>>> for various reasons. Will the TI programs work against all gcc versions
>>> available from oe-core/meta-oe?
>>
>> I've had good luck with the meta-ti layer + Poky (oe-core&  meta-yocto).
>> I have my own kernels (for other OMAP boards that are not mainline), so
>> I don't use the meta-ti kernel recipes, but I do use much of the rest,
>> including the DSP bits.
>
> Can you elaborate on what your custom kernels are based on? Thanks.

Stock 3.0 (mainline) plus some local enhancements, board support, etc.
We also use Poky as the baseline for other products which are PowerPC based.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------