Op 19 jul 2011, om 07:21 heeft Kumar Gala het volgende geschreven:
> 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 fro
Hi all,
I am new to Yocto and to Distro work in general.
I want to use Yocto on the Kontron nanoETXexpressTT boards.
(http://de.kontron.com/products/computeronmodules/com+express/com+express+ultra/nanoetxexpresstt.html)
These boards are based on the Intel Atom E6xx and the EG20T platform
control
On Jul 19, 2011, at 2:44 AM, Koen Kooi wrote:
>
> Op 19 jul 2011, om 07:21 heeft Kumar Gala het volgende geschreven:
>
>> 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 u
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
>> wrote:
>>> The e500v2 core utilizes a unique floating point programming model
This bug: http://bugzilla.yoctoproject.org/show_bug.cgi?id=1177 only
occurs on my CentOS 5 boxes (not on my Fedora 13 box). I have
determined that this git patch
4b66ce472871618cfe4761861392b7f9c3c265b0 is causing the problem.
Reverting the patch fixes this.
Still looking at this more but I though
Agenda:
- opens - 5 min
- Review Yocto 1.1 M2 Release Criteria - 20 min (Song) See details at:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.1_Release_Criteria
- Review M3 status and schedule - 10 min (Song)
- Discussion of using Weighted Defect density as one of the release criteria:
(4
To whom may concern,
I tried to build Yocto for a real device, which is EeePC901. Because of
README.hardware mentioned.
Here are my steps:
# source poky-bernard-5.0.1/poky-init-build.env build-poky-5.0.1
Modify the local.conf (As attachment)
# bitbake poky-image-sato-directdisk
However I got t
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 Gala
>>> wrote:
I've been working on trying to get an e500v2 (linux-gnuspe) compiler
working a
I hope this is the correct place to post this. If not, please let me
know.
I'm trying to create a recipe for OpenDDS. The recipe works so far as
fetching, unpacking, and configuration. Or it seems to. :) Part of the
configuration piece is that it also pulls down ACE+TAO real-time CORBA.
This part
On Mon, Jul 18, 2011 at 11:47 PM, 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
>> wrote:
>>> The e500v2 core utilizes a unique floating point programming model / ABI.
>>> We utilize TARGET_FPU = "spe" to distinguish this cho
On 07/19/2011 06:17 AM, Kumar Gala wrote:
On Jul 19, 2011, at 2:44 AM, Koen Kooi wrote:
Op 19 jul 2011, om 07:21 heeft Kumar Gala het volgende geschreven:
The majority of support for the PowerPC e500v2/SPE target already
exists. However some minor cleans are required to get things working
On Jul 19, 2011, at 10:32 AM, Saul Wold wrote:
> On 07/19/2011 06:17 AM, Kumar Gala wrote:
>>
>> On Jul 19, 2011, at 2:44 AM, Koen Kooi wrote:
>>
>>>
>>> Op 19 jul 2011, om 07:21 heeft Kumar Gala het volgende geschreven:
>>>
The majority of support for the PowerPC e500v2/SPE target alrea
On 07/19/2011 08:40 AM, Kumar Gala wrote:
On Jul 19, 2011, at 10:32 AM, Saul Wold wrote:
On 07/19/2011 06:17 AM, Kumar Gala wrote:
On Jul 19, 2011, at 2:44 AM, Koen Kooi wrote:
Op 19 jul 2011, om 07:21 heeft Kumar Gala het volgende geschreven:
The majority of support for the PowerPC e50
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Andre Haupt
>
> Hi all,
>
> I am new to Yocto and to Distro work in general.
>
> I want to use Yocto on the Kontron nanoETXexpressTT boards.
> (http://de.kontron.com/products/computeronmodules/com+expr
On Fri, 2011-07-15 at 21:23 +, McClintock Matthew-B29882 wrote:
> This bug: http://bugzilla.yoctoproject.org/show_bug.cgi?id=1177 only
> occurs on my CentOS 5 boxes (not on my Fedora 13 box). I have
> determined that this git patch
> 4b66ce472871618cfe4761861392b7f9c3c265b0 is causing the probl
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
__
Signed-off-by: Kumar Gala
---
meta/conf/machine/include/tune-ppce500v2.inc |4
1 files changed, 4 insertions(+), 0 deletions(-)
create mode 100644 meta/conf/machine/include/tune-ppce500v2.inc
* Removed TARGET_OS_powerpc (not needed)
diff --git a/meta/conf/machine/include/tune-ppce500v
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
---
meta/recipes-connectivity/openssl/openssl.inc |3 +++
.../recipes-connectivity/openssl/openssl_0.9.8r.bb |2 +-
2
For a PPC target flac will try to build with altivec optimizations.
Altivec and SPE are mutually exclusive options. Between flac's
configure choices and the ppce500v2 tune file options we'd end up with
a compile invocation with the following arguments:
-mabi=spe -mspe -mabi=altivec -maltivec
Whi
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
---
meta/conf/distro/include/tclibc-eglibc.inc |
On Tue, Jul 19, 2011 at 12:06 PM, Joshua Lock wrote:
> You can use 'objdump -T' for this, i.e. (from my F15 box):
> joshual@scimitar:~
> $ objdump -T /lib/libc.so.6 | grep realpath
> 416c3f00 g DF .text 0041 (GLIBC_2.0) realpath
> 415e60e0 g DF .text 0478 GLIBC_2.3 realpath
> 4
On 07/18/2011 11:17 PM, Li, Simon wrote:
> To whom may concern,
>
> I tried to build Yocto for a real device, which is EeePC901. Because of
> README.hardware mentioned.
>
> Here are my steps:
> # source poky-bernard-5.0.1/poky-init-build.env build-poky-5.0.1
>
> Modify the local.conf (As attachm
Really sorry if many of the past meeting agenda and minutes have not been able
to reach you. I had some problems with the Yocto project mailing list. Please
let me know if you hear anyone still having this problem.
Thanks!
Song
Attendees:
Mark, Dave, Paul, Shane, Saul, Beth, Richard, Josh, Jaso
Some distro's don't include these macros in /usr/include/endian.h
so we include them via this patch
Signed-off-by: Matthew McClintock
---
This fixes builds on my CentOS 5.5 box
.../ldconfig-native-2.12.1/endianess-header.patch | 102
meta/recipes-core/eglibc/ldconfig-nati
On 07/19/2011 04:37 PM, Matthew McClintock wrote:
Some distro's don't include these macros in /usr/include/endian.h
so we include them via this patch
Matthew:
Thanks for this patch.
What will happen on distros that do include these macros? Will we get
redefines? I don't see any conditional
On Fri, 2011-07-15 at 11:31 +0800, Ke Liping wrote:
> From: Liping Ke
>
> Since Hob only needes package dependency information, we can
> create a new version of package information retrieving methods,
> remove task dependency information, so that we can greatly
> reduce data loading time for Hob
On Mon, 2011-07-11 at 15:31 +0800, Ke Liping wrote:
> From: Liping Ke
>
> The two patches are the implmentation of Hob Cache for accelarating
> UI switching. If one configuration has been saved before, when user
> switch back to the same configuration combination, we will use the
> cache content
On Thu, 2011-07-14 at 09:34 +0800, NiQingliang wrote:
> new version
>
> diff --git a/oe-init-build-env b/oe-init-build-env
> index 77332a7..0fe1b5e 100755
> --- a/oe-init-build-env
> +++ b/oe-init-build-env
> @@ -39,6 +39,35 @@ else
> $OEROOT/scripts/oe-setup-builddir
> unset OEROOT
>
On Tue, Jul 19, 2011 at 6:58 PM, Saul Wold wrote:
> Matthew:
>
> Thanks for this patch.
>
> What will happen on distros that do include these macros? Will we get
> redefines? I don't see any conditional testing to determine if they exist
> already.
I suspect redefines. I did compile this on a m
update accroding your suggestion.
This patch is for bitbake indeed, but bitbake is not part of
openembedded. Is it RIGHT?
diff --git a/oe-init-build-env b/oe-init-build-env
index 77332a7..acf4e96 100755
--- a/oe-init-build-env
+++ b/oe-init-build-env
@@ -39,6 +39,34 @@ else
$OEROOT/scripts/oe
Oh, sorry, I have found the git tree of openembedded-core.
On Wed, 2011-07-20 at 10:31 +0800, NiQingliang wrote:
> update accroding your suggestion.
> This patch is for bitbake indeed, but bitbake is not part of
> openembedded. Is it RIGHT?
>
>
> diff --git a/oe-init-build-env b/oe-init-build-e
Hi, Darren,
Yes, I use poky-image-sato-live and it works well on EeePC901 now.
Since it run from USB drive directly, it runs quite slow.
Is there any way to install it into SSD driver from USB drive?
Thanks.
Best Regards,
Simon
-Original Message-
From: Darren Hart [mailto:dvh...@linux.in
On 07/19/2011 07:49 PM, Li, Simon wrote:
> Hi, Darren,
> Yes, I use poky-image-sato-live and it works well on EeePC901 now.
> Since it run from USB drive directly, it runs quite slow.
> Is there any way to install it into SSD driver from USB drive?
At boot time, press tab at the syslinux boot: pro
34 matches
Mail list logo
