On Aug 9, 2011, at 11:18 PM, Darren Hart wrote:
Bruce,
The following patch is needed for qemuppc and fsl-mpc8315e-rdb (same
reasons as before). Can you pull this in from the 2.6.37 yocto tree?
commit 5ff609967ffe87c49d534d7861a7e0b150517726
Author: Bruce Ashfield
Is there some command to get the set of packages that will be attempted to be
built?
- k
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Aug 3, 2011, at 10:12 AM, Richard Purdie wrote:
On Wed, 2011-08-03 at 09:50 -0500, Kumar Gala wrote:
On Aug 3, 2011, at 9:22 AM, Richard Purdie wrote:
On Wed, 2011-08-03 at 09:04 -0500, Kumar Gala wrote:
Bug submitted:
http://bugzilla.pokylinux.org/show_bug.cgi?id=1323
My question
http://bugzilla.pokylinux.org/show_bug.cgi?id=1323
My question still stands even w/o it being in formal docs.
FWIW, POKYMODE was replaced by TCMODE as part of the OE-Core changes.
I'd be interested to know where we've missed the references to it and
get to get those references fixed.
more about the context of the problem from
someone. The bug could just be against documentation in general and specify
the need for better documentation using a prebuilt toolchain.
ScottR
-Original Message-
From: Kumar Gala [mailto:ga...@kernel.crashing.org]
Sent: Tuesday
On Aug 3, 2011, at 9:29 AM, Paul Eggleton wrote:
On Wednesday 03 August 2011 15:22:56 Richard Purdie wrote:
On Wed, 2011-08-03 at 09:04 -0500, Kumar Gala wrote:
Bug submitted:
http://bugzilla.pokylinux.org/show_bug.cgi?id=1323
My question still stands even w/o it being in formal docs
I can, but not sure what the bug is.
- k
On Jul 28, 2011, at 11:39 PM, Stewart, David C wrote:
Scott - I have had a couple of questions about this exact topic. Can you
please submit a bug on this? Thanks.
Sent from my Blackberry
- Original Message -
From: Kumar Gala
One of my Chinese colleagues mentioned he was not able to get to the
http://www.yoctoproject.org/ website. I was wondering if anyone else might be
experience this or not?
Is this something someone at LF can look into?
- k
___
yocto mailing list
On Aug 2, 2011, at 10:53 PM, Kumar Gala wrote:
One of my Chinese colleagues mentioned he was not able to get to the
http://www.yoctoproject.org/ website. I was wondering if anyone else might
be experience this or not?
Is this something someone at LF can look into?
Oops, sorry
as soon as I find the cause.
Regards
Malcolm
-Original Message-
From: yocto-boun...@yoctoproject.org
[mailto:yocto-boun...@yoctoproject.org] On Behalf Of Kumar Gala
Sent: 28 July 2011 15:26
To: Patches and discussions about the oe-core layer
Cc: Yocto discussion list
Subject
On Jul 28, 2011, at 11:05 AM, Saul Wold wrote:
On 07/28/2011 08:45 AM, Kumar Gala wrote:
I think I know the cause, let me dig up the change that is related. What
bit is looking for just ppc603e?
This might also be related to the PACKAGE_EXTRA_ARCHS issue, please try the
patch that Koen
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
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
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
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
On Jul 20, 2011, at 12:05 PM, Saul Wold wrote:
On 07/19/2011 10:41 AM, Kumar Gala wrote:
The majority of support for the PowerPC e500v2/SPE target already
exists. However some minor cleans are required to get things working
completely.
The e500v2 utilizes a unique floating point
On Jul 15, 2011, at 12:31 AM, Bruce Ashfield wrote:
On 11-07-15 12:56 AM, Kumar Gala wrote:
The MPC8315E has a e300c3 core in it with 'classic' or normal PPC
floating point.
'SPE' floating point is what exists on the e500v2 core.
Acked-by: Bruce Ashfield bruce.ashfi...@windriver.com
For a new bsp/target what's the best config choice to try and build all of
yocto? Is it core-image-sato?
- k
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Signed-off-by: Kumar Gala ga...@kernel.crashing.org
---
meta/conf/machine/include/tune-ppce500mc.inc |4
1 files changed, 4 insertions(+), 0 deletions(-)
create mode 100644 meta/conf/machine/include/tune-ppce500mc.inc
diff --git a/meta/conf/machine/include/tune-ppce500mc.inc
b/meta
On Jul 19, 2011, at 1:01 AM, Khem Raj wrote:
On Mon, Jul 18, 2011 at 10:21 PM, Kumar Gala ga...@kernel.crashing.org
wrote:
Signed-off-by: Kumar Gala ga...@kernel.crashing.org
---
meta/conf/machine/include/tune-ppce500v2.inc |5 +
1 files changed, 5 insertions(+), 0 deletions
On Jul 19, 2011, at 1:04 AM, Khem Raj wrote:
On Mon, Jul 18, 2011 at 10:21 PM, Kumar Gala ga...@kernel.crashing.org
wrote:
The e500v2 core utilizes a unique floating point programming model / ABI.
We utilize TARGET_FPU = spe to distinguish this choice. When building
the toolchain
Adding openembedded-core to see if any feedback on my query.
- k
On Jul 19, 2011, at 1:47 AM, Kumar Gala wrote:
On Jul 19, 2011, at 1:04 AM, Khem Raj wrote:
On Mon, Jul 18, 2011 at 10:21 PM, Kumar Gala ga...@kernel.crashing.org
wrote:
The e500v2 core utilizes a unique floating point
On Jul 18, 2011, at 12:22 PM, Saul Wold wrote:
On 07/18/2011 07:54 AM, Kumar Gala wrote:
On Jul 18, 2011, at 9:45 AM, Khem Raj wrote:
On Mon, Jul 18, 2011 at 5:58 AM, Kumar Galaga...@kernel.crashing.org
wrote:
I've been working on trying to get an e500v2 (linux-gnuspe) compiler
The e500v2 core utilizes a unique floating point programming model / ABI.
We utilize TARGET_FPU = ppc-efd to distinguish this choice (Embedded
scalar single-precision floating-point). When building the toolchain for
this ABI we need configure gcc with --enable-e500_double.
Signed-off-by: Kumar
The majority of support for the PowerPC e500v2/SPE target already
exists. However some minor cleans are required to get things working
completely.
The e500v2 utilizes a unique floating point programming model / ABI from
other PowerPC targets and thus requires special handling.
- k
If trying to build for an e500v2 target openssl will fail to build since
the configure script didn't know how to handle a 'gnuspe' target.
Signed-off-by: Kumar Gala ga...@kernel.crashing.org
---
meta/recipes-connectivity/openssl/openssl.inc |3 +++
.../recipes-connectivity/openssl
Which would cause the compile to fail due to the mutual exclusion.
Pulled in a patch from the debian SPE port that addresses this issue:
http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2010-June/010212.html
Signed-off-by: Kumar Gala ga...@kernel.crashing.org
---
.../flac/flac
Its possible that BASE_PACKAGE_ARCH isn't set to ppce500 or ppce500v2 when
we build native toolchains. So we can utilize TARGET_FPU being set to
'ppc-efd' or 'ppc-efs' to determine if we should enable the gnuspe ABI.
Signed-off-by: Kumar Gala ga...@kernel.crashing.org
---
meta/conf/distro
I've been working on trying to get an e500v2 (linux-gnuspe) compiler working
and seem to have build a native toolchain. However when I try and compile a
simple hello world style app I get:
root@p2020-ds:~# gcc float.c
gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found
I was trying a core-image-minimal build with 'tools-sdk' added to
EXTRA_IMAGE_FEATURES and was expecting a native gcc in the generated rootfs.
This was for mpc8315e-rdb config.
conf/local.conf has:
EXTRA_IMAGE_FEATURES = tools-sdk debug-tweaks
Is this wrong? is my expectation wrong based on
On Jul 18, 2011, at 12:22 PM, Saul Wold wrote:
On 07/18/2011 07:54 AM, Kumar Gala wrote:
On Jul 18, 2011, at 9:45 AM, Khem Raj wrote:
On Mon, Jul 18, 2011 at 5:58 AM, Kumar Galaga...@kernel.crashing.org
wrote:
I've been working on trying to get an e500v2 (linux-gnuspe) compiler
On Jul 18, 2011, at 1:01 PM, Kumar Gala wrote:
On Jul 18, 2011, at 12:22 PM, Saul Wold wrote:
On 07/18/2011 07:54 AM, Kumar Gala wrote:
On Jul 18, 2011, at 9:45 AM, Khem Raj wrote:
On Mon, Jul 18, 2011 at 5:58 AM, Kumar Galaga...@kernel.crashing.org
wrote:
I've been working
You can try -fno-use-linker-plugin as a workaround. Does
liblto_plugin.so exist on target rfs ?
it might be then gcc driver bug if the library is not there then we
forgot to package it.
File appears to be there:
root@p2020-ds:/# file
On Jul 18, 2011, at 1:37 PM, Khem Raj wrote:
On Mon, Jul 18, 2011 at 11:24 AM, Kumar Gala ga...@kernel.crashing.org
wrote:
You can try -fno-use-linker-plugin as a workaround. Does
liblto_plugin.so exist on target rfs ?
it might be then gcc driver bug if the library is not there then we
On Jul 18, 2011, at 2:27 PM, Khem Raj wrote:
On Mon, Jul 18, 2011 at 12:22 PM, Kumar Gala ga...@kernel.crashing.org
wrote:
On Jul 18, 2011, at 1:37 PM, Khem Raj wrote:
On Mon, Jul 18, 2011 at 11:24 AM, Kumar Gala ga...@kernel.crashing.org
wrote:
You can try -fno-use-linker-plugin
The majority of support for the PowerPC e500v2/SPE target already
exists. However some minor cleans are required to get things working
completely.
The e500v2 utilizes a unique floating point programming model / ABI from
other PowerPC targets and thus requires special handling.
- k
The e500v2 core utilizes a unique floating point programming model / ABI.
We utilize TARGET_FPU = spe to distinguish this choice. When building
the toolchain for this ABI we need configure gcc with --enable-e500_double.
Signed-off-by: Kumar Gala ga...@kernel.crashing.org
---
meta/recipes
Its possible that BASE_PACKAGE_ARCH isn't set to ppce500 or ppce500v2 when
we build native toolchains. So we can utilize TARGET_FPU being set to
spe to determine if we should enable the gnuspe ABI.
Signed-off-by: Kumar Gala ga...@kernel.crashing.org
---
meta/conf/distro/include/tclibc
Signed-off-by: Kumar Gala ga...@kernel.crashing.org
---
meta/conf/machine/include/tune-ppce500v2.inc |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
create mode 100644 meta/conf/machine/include/tune-ppce500v2.inc
diff --git a/meta/conf/machine/include/tune-ppce500v2.inc
b/meta
If trying to build for an e500v2 target openssl will fail to build since
the configure script didn't know how to handle a 'gnuspe' target.
Signed-off-by: Kumar Gala ga...@kernel.crashing.org
---
meta/recipes-connectivity/openssl/openssl.inc |3 +++
.../recipes-connectivity/openssl
Which would cause the compile to fail due to the mutual exclusion.
Pulled in a patch from the debian SPE port that addresses this issue:
http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2010-June/010212.html
Signed-off-by: Kumar Gala ga...@kernel.crashing.org
---
.../flac/flac
On Jul 15, 2011, at 12:31 AM, Bruce Ashfield wrote:
On 11-07-15 12:56 AM, Kumar Gala wrote:
The MPC8315E has a e300c3 core in it with 'classic' or normal PPC
floating point.
'SPE' floating point is what exists on the e500v2 core.
Acked-by: Bruce Ashfield bruce.ashfi...@windriver.com
On Jul 14, 2011, at 9:36 PM, Kumar Gala wrote:
Where is the best place to ask questions and try and get support for adding
some toolchain variations in?
I'm wanting to add support in for a few different flavors of PPC that are not
currently supported:
* e500v2 (gcc needs --enable
On Jul 15, 2011, at 8:37 AM, Richard Purdie wrote:
On Fri, 2011-07-15 at 08:33 -0500, Kumar Gala wrote:
On Jul 14, 2011, at 9:36 PM, Kumar Gala wrote:
Where is the best place to ask questions and try and get support for adding
some toolchain variations in?
I'm wanting to add support
In my attempts to get an e500v2/gnuspe toolchain working I was able to get
core-image-minimal working. However when I try the 'meta-toolchain' I run into
the following below. I believe this is because of TARGET_OS being
'linux-gnuspe'.
Any ideas ?
- k
[kumar@right build-p2020]$ bitbake
On Jul 15, 2011, at 2:28 PM, Khem Raj wrote:
On Thu, Jul 14, 2011 at 7:36 PM, Kumar Gala ga...@kernel.crashing.org wrote:
Where is the best place to ask questions and try and get support for adding
some toolchain variations in?
I'm wanting to add support in for a few different flavors
On Jul 15, 2011, at 4:29 PM, Khem Raj wrote:
On Fri, Jul 15, 2011 at 2:10 PM, Kumar Gala ga...@kernel.crashing.org wrote:
In my attempts to get an e500v2/gnuspe toolchain working I was able to get
core-image-minimal working. However when I try the 'meta-toolchain' I run
into the following
On Nov 10, 2010, at 7:58 AM, Bruce Ashfield wrote:
On 10-11-10 08:38 AM, Bruce Ashfield wrote:
On 10-11-10 01:46 AM, Kumar Gala wrote:
Why does the meta/conf/machine/mpc8315e-rdb.conf list TARGET_FPU as
SPE. This isn't correct for an MPC8313 SoC.
It isn't used at the moment, so we can
On Nov 10, 2010, at 8:23 AM, Bruce Ashfield wrote:
On 10-11-10 09:11 AM, Kumar Gala wrote:
On Nov 10, 2010, at 7:58 AM, Bruce Ashfield wrote:
On 10-11-10 08:38 AM, Bruce Ashfield wrote:
On 10-11-10 01:46 AM, Kumar Gala wrote:
Why does the meta/conf/machine/mpc8315e-rdb.conf list
50 matches
Mail list logo
