All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: Additional / new BSP collection?
Date: Wed, 27 Jul 2011 08:50:20 -0500	[thread overview]
Message-ID: <1311774620.3739.49.camel@elmorro> (raw)
In-Reply-To: <66F46EDD-010E-41CC-BE5E-196894B3BA22@kernel.crashing.org>

On Wed, 2011-07-27 at 05:40 -0700, 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?
> 

Hi Kumar,

For meta-intel, it's pretty simple and is summarized by this blurb from
the meta-intel MAINTAINERS file: 

"Please submit any patches against meta-intel BSPs to the Yocto mailing
list (yocto@yoctoproject.org)."

Basically, new patches get submitted to the mailing list, go through the
standard on-list comment and review process, and then get pulled into
master by whoever maintains the BSP when everything looks good.

Hope that helps,

Tom

> BSP would be for Freescale PowerPC SoC and the reference designs produced by FSL for them.
> 
> > 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@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@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto




  parent reply	other threads:[~2011-07-27 13:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27  5:21 Additional / new BSP collection? Kumar Gala
2011-07-27  8:45 ` Richard Purdie
2011-07-27 12:40   ` Kumar Gala
2011-07-27 13:30     ` Bruce Ashfield
2011-07-27 13:52       ` Richard Purdie
2011-07-27 13:55       ` Kumar Gala
2011-07-27 14:23         ` Richard Purdie
2011-07-27 14:58           ` Bruce Ashfield
2011-07-27 13:50     ` Tom Zanussi [this message]
2011-07-27 13:53       ` Kumar Gala
2011-07-27 14:06         ` Tom Zanussi
2011-07-27 14:13           ` Kumar Gala
2011-07-27 14:33           ` Cherry, John

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=1311774620.3739.49.camel@elmorro \
    --to=tom.zanussi@intel.com \
    --cc=galak@kernel.crashing.org \
    --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.