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

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

test

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

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

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

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

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

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

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

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

2010/11/3 Frans Meulenbroeks <fransmeulenbroeks@...>: Nevermind, already found the cause of the traceback. I accidently ran bitbake in the wrong dir. My default setup is such that BBPATH etc is

Dear all, Not sure whether I should sent this here or to the poky ML. Trying here first, fee free to forward/redirect. After my initial success of building poky 4.0 with the delivered config, I

This is good. I may test if this works and let's see if Richard has any comments on it. It seems to be an elegant solution, but need some efforts to find out how this can fit in current zypper. Hmm,

Hi, I've seen a few comments that people are struggling with the python version Poky requires not being present in certain distros. I can now point to one potential solution in the form of a

I have updated the spreadsheet and removed items that should not have been included (-natives and other tools). I have also added annotation to the first column to show some potential adjustments and

It does. What we can also do, is split it between 'kernel' and 'BSP'. I've been triaging bugs like this for 6 years now, and typically it is very hard for the submitters to categorize properly. But

Let me chip in with some information here. Poky used to support the n800 machine semi-officially and it ran sato quite well including the wiki and touchscreen. The problem has been that the xserver

Yes, I agree. Right, it doesn't seem to be working out of the box - I'll take a look and see if we can't rescue it from meta-extras... BTW, I'd actually like to have one of these for myself - can

Hello again! I think nokia n8xx could be a nice example of what yocto/poky are capable of. Especially now that Nokia has abandoned this devices, it would be cool to have a new OS being supported on