yocto@lists.yoctoproject.org

Re: some yocto/poky issues and errors

Can you point at a copy of this recipe or the do_package function? At this point its hard to guess what the problem might be. I suspect you might be right about there being a reference to but not a

By Richard Purdie <rpurdie@...> · #181 ·

Re: some yocto/poky issues and errors

2010/11/3 Richard Purdie <rpurdie@...>: ess it would be nice if bitbake would have given a decent error msg though. Richard, the recipe was a private kernel recipe which actually didn't do

By Frans Meulenbroeks <fransmeulenbroeks@...> · #182 ·

Re: zypper and poky architectures

Thats the full purpose of the winner is to deal with conflicts. Libraries should never conflict, if they do it's a bug in the library. The file dependencies that I added in the 0.9 work will resolve

By Mark Hatle <mark.hatle@...> · #183 ·

ppc e500v2 support?

Hi, I'm trying to add my powerpc board to yocto (as a test). This board mpc8536ds has an e500v2 core. It works under OE (MACHINE = "calamari"). but gcc-cross-initial fails in do_compile when it

By Frans Meulenbroeks <fransmeulenbroeks@...> · #184 ·

Re: ppc e500v2 support?

At this point we have no added any e500 support to Poky. It would certainly be interesting to me to add/enable e500 support, as well as other spe optimizations that eglibc might provide. --Mark

By Mark Hatle <mark.hatle@...> · #185 ·

Re: ppc e500v2 support?

I can definitely guarantee that this would work in the yocto kernel (with a small local step for you), in fact, I've got a full BSP for this, and any of the extra features in the kernel (SPE, IEEE

By Bruce Ashfield <bruce.ashfield@...> · #186 ·

Re: ppc e500v2 support?

2010/11/3 Bruce Ashfield <bruce.ashfield@...>: Sounds good. Is there anything you could share as a starting point? Frans

By Frans Meulenbroeks <fransmeulenbroeks@...> · #187 ·

Re: ppc e500v2 support?

There is. And I'll clean it up a bit. The BSP bootstrap currently has a couple of different steps that are local to your build (but eventually merge to the kernel tree if a board is supported) which

By Bruce Ashfield <bruce.ashfield@...> · #188 ·

About test

test

By Xiaofeng Yan <xiaofeng.yan@...> · #189 ·

Re: ppc e500v2 support?

Hello Bruce, <bruce.ashfield@...> wrote: Was combo did you see problems with? I added e500v2 support to OpenEmbedded more than one year ago and have not seen issues yet in userspace

By Leon Woestenberg <leon.woestenberg@...> · #190 ·

Re: ppc e500v2 support?

It was particular to the mpc8315e config. Runtime on the target is fine, since this is all well known and working (we've had SPE/e500/e500v2 BSPs working for quite some time), the issue was specific

By Bruce Ashfield <bruce.ashfield@...> · #191 ·

Re: ppc e500v2 support?

I'm not sure we have all of the pieces in place yet in the toolchain. My quick looking of my own e500v1 & e500v2 support includes both libc patches and compiler patches. Just an FYI.. the compiler

By Mark Hatle <mark.hatle@...> · #192 ·

minor recognition success!

I'm sitting in a talk by Arnd Bergmann (IBM) at LPC. He's is speaking about "porting Linux to a new architecture, done right" and among the build systems he lists as good starting point he mentioned

By Dirk Hohndel <hohndel@...> · #193 ·

Re: ppc e500v2 support?

Hello Mark, In OpenEmbedded we use the core variant as the packaging name: TARGET_CC_ARCH = "-mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double" BASE_PACKAGE_ARCH =

By Leon Woestenberg <leon.woestenberg@...> · #194 ·

Re: ppc e500v2 support?

I think this is an area we need to coordinate.. I'm not against calling is ppce500v2 for right now. However, I think this is a place we need to coordinate efforts. I'm going to attempt to pull

By Mark Hatle <mark.hatle@...> · #195 ·

Re: ppc e500v2 support?

Hello Mark, I don't see how we could be "final" on this, it seems a returning topic every few years. To bring in the OpenEmbedded arch namespace and our optimizations, from the "master" branch at

By Leon Woestenberg <leon.woestenberg@...> · #196 ·

Re: ppc e500v2 support?

This is a place where I think the Yocto Project can help. We're likely never going to have a final answer.. but what we'll be able to do is give these impromptu ABIs reasonable names so when people

By Mark Hatle <mark.hatle@...> · #197 ·

Re: nightly-release takes more than 24 hours to build.

Great, thanks Dave! :) I have spec'ed out and initiated an order for our newest server. In case anyone likes to geek out on hardware specs, here they are: Dell PowerEdge R710 2x Xeon X5680 @

By Scott Garman <scott.a.garman@...> · #198 ·

[PULL] fixes to eglibc and busybox

This is a rebased and resent version of that I sent to poky@... (Thanks to Mark and Saul's suggestion). Since this is a non poky core change, I post this version in this mailing list. Please

By Cui, Dexuan <dexuan.cui@...> · #199 ·

Re: World Package List

Please find enclosed the annotated list of recipes that are not currently built as part of any task or image. There are a some basic options that could occur with these recipes, do nothing, move the

By Saul Wold <sgw@...> · #200 ·

Messages