[yocto] Additional / new BSP collection?

[Bruce Ashfield]

On 07/27/11 08:40, Kumar Gala wrote:
>
> On Jul 27, 2011, at 3:45 AM, Richard Purdie wrote:
>
>> On Wed, 2011-07-27 at 00:21 -0500, Kumar Gala wrote:
>>> Who is the best person to ask about adding new BSPs into yocto.  What
>>> I mean by this is having a meta layer hosted on git.yoctoproject.org
>>> like meta-intel and the mechanics associated with this (getting new
>>> repo on git server, autobuilder support, webpage details, etc.).
>>
>> This list is as good a place as any! :)
>>
>> Its relatively easy to arrange for a git repository. The main things we
>> ask are that it has clearly defined maintainership (a clear maintainer
>> and submission process) and a clear scope. Do you have any specific BSPs
>> in mind?
>
> Maintainership would be straight forward.  Not sure about submissions process, what is done for meta-intel today?
>
> BSP would be for Freescale PowerPC SoC and the reference designs produced by FSL for them.

Hi Kumar,

As you know, I've been working on several kernel efforts
around the FSL parts as well (in particular the ones that
have enough pieces upstream to work out of the box).  I
definitely don't want to overlap in a way that doesn't
create complimentary efforts.

What are your current thoughts around kernels and the
(nearly religious) kernel version question ? It would be
great to get some alignment on features (-rt, tracing,
boot, footprint reduction, etc, etc) and save some effort
on maintenance and validation. Also if we want to create
some yocto reference BSPs, having a kernel version and feature
set match is important as well (i.e. what we've done for
the intel ones).

To that end, do you have an thoughts about using linux-yocto
as a base to any BSP work ? That statement doesn't do it
justice though, since when I say 'use linux-yocto as a base',
it really means that linux-yocto uses your BSPs as an
upstream/official reference and can pull support for them
into branches, and have the configuration and other tooling
get them any functionality that is being developed.

No control over BSP content, or anything like this, is being
suggested or asserted here. Just looking to all push in the
same direction (embedded features and BSPs to upstream) and
re-use the work of BSPs available in the community. If the
base is the same (and hence kernel version), then this relationship
and workflow is very simple.

... and as a bonus, if the workflow doesn't work easily, then
there's a problem with it and we can work on something that
is suitable (change tools, etc).

Thanks,

Bruce

>
>> The wiki is available to host information and we can work out links on
>> the website as the specific needs come up. Autobuilder support is
>> something we need to figure out since its a finite resource but we can
>> likely figure something out there once we understand what kind of BSPs
>> we're talking about.
>>
>> Beth Flanagan<elizabeth.flanagan at intel.com>  is the person who'd handle
>> the mechanics of setting up the repository, the name is likely the
>> hardest bit!
>
> meta-fsl-ppc ;)
>
> - k
>
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto