BSP guidelines

[Tom Rini]

On 02/27/2011 04:28 AM, Stefan Schmidt wrote:
> Hello.
>
> On Tue, 2011-02-22 at 14:22, Richard Purdie wrote:
>> On Tue, 2011-02-22 at 12:44 +0100, Koen Kooi wrote:
>>> Hi,
>>>
>>> As example BSPs we have the intel ones:
>>>
>>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/
>>>
>>> And the TI one I threw together:
>>>
>>> http://gitorious.org/angstrom/angstrom-layers/trees/master
>>>
>>> Based on those, do people have some guidelines already we can combine into a single document?
>>
>> http://www.yoctoproject.org/sites/default/files/bsp-guide_7.pdf ?
>
> Echoing what Koen and Tom already said I an only agree. It looks like a good
> description of the BSPs. We would need to look over the naming, Yocto, Poky,
> OE-core, etc, again after we have settled oe-core.
>
> Another thing is how we will handle include files like for omap3. Having these
> in core would not really work with the separate BSP layers. Having it in every
> omap3 based BSP brings in duplication and fragmentation and having it in another
> omap3-core layer brings in yet another layer.
>
> Any good ideas for this?

My first thought is that mature tune/family/etc files should be 
encouraged to live in the core, with appropriate soft-assigns.

-- 
Tom Rini
Mentor Graphics Corporation