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
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
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
On Jul 27, 2011, at 8:50 AM, Tom Zanussi wrote:
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
On Wed, 2011-07-27 at 06:53 -0700, Kumar Gala wrote:
On Jul 27, 2011, at 8:50 AM, Tom Zanussi wrote:
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
I was wondering what distinction qualified for a BSP existing in a meta layer
vs in poky directly.
For FSL PPC we currently have MPC8315-RDB in poky. Ideally we'd have one BSP
for each major flavor [ associated with a unique compiler / libc target ].
This would end up being something like
On Wed, 2011-07-27 at 08:55 -0500, Kumar Gala wrote:
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
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Tom Zanussi
Sent: Wednesday, July 27, 2011 7:07 AM
To: Kumar Gala
Cc: Yocto discussion list
Subject: Re: [yocto] Additional / new BSP collection?
On Wed, 2011-07-27 at
On 07/27/11 10:23, Richard Purdie wrote:
On Wed, 2011-07-27 at 08:55 -0500, Kumar Gala wrote:
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
On 07/27/11 10:23, Kumar Gala wrote:
I was wondering what distinction qualified for a BSP existing in a meta layer
vs in poky directly.
For FSL PPC we currently have MPC8315-RDB in poky. Ideally we'd have one BSP
for each major flavor [ associated with a unique compiler / libc target ].
On Wed, 2011-07-27 at 09:23 -0500, Kumar Gala wrote:
I was wondering what distinction qualified for a BSP existing in a
meta layer vs in poky directly.
For FSL PPC we currently have MPC8315-RDB in poky. Ideally we'd have
one BSP for each major flavor [ associated with a unique compiler /
On 07/26/2011 12:22 PM, Matthew McClintock wrote:
A previous patch changed the default TERM to use xterm. This updates
local.conf.sample to match the change
Signed-off-by: Matthew McClintockm...@freescale.com
---
meta-yocto/conf/local.conf.sample |2 +-
1 files changed, 1 insertions(+),
Is it normal that the first stage (native) portion does not seem to either deal
with BB_NUMBER_THREADS or PARALLEL_MAKE?
- k
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
It seems like there is a way to use a prebuilt toolchain with poky but no real
details.
Some refs in the docs like:
POKYMODE
Toolchain selector. It can be external toolchain built from Poky or few
supported combinations of upstream GCC or CodeSourcery Labs toolchain.
But grepping the code
14 matches
Mail list logo
