Agree in principle. Let me confirm: - kernel runtime (this includes all errors, panics, BUGs, etc. from the three categories I listed above - no objection). It's still 3 categories, but separate

Hi all, This is the Poky weekly bug trend charts for last week (WW44). The open bug number increased to 133. There were only few bugs submitted/fixed in last week. The 1st chart indicates the total

In case you didn't note Qing's investigation last week, attach his mail for your reference. Thanks Kevin

Hi, 2010/11/1 Hector Oron <hector.oron@...>: NOTE: package libtool-cross-2.2.10-r1: task do_package_write: Succeeded NOTE: Running task 1448 of 1529 (ID:

Which MACHINE is that set for? Its unusual for the system to be using linux-dummy. Cheers, Richard

Hello, 2010/11/1 Richard Purdie <rpurdie@...>: Yes, it is 64 bit kernel host running a 32 bit userland. Linux enorme 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64

Hello, 2010/11/2 Richard Purdie <rpurdie@...>: It is a balloon3 [1]. I think you have not official support for it. I also got an Intel Embedded Devkit 1-N450 (Black Sand) which I

Only certainly variables can be passed through the environment. Can you put the line in local.conf please and retry as otherwise it won't have any effect. Ok, good. Cheers, Richard

So to be clear, you set MACHINE="balloon3"? You're therefore building with some layer or additional metadata? I'd suggest trying a supported machine like "atom-pc" first before trying to add your

Hello, 2010/11/2 Richard Purdie <rpurdie@...>: Yes and yes. I'll attempt "atom-pc" later on, but that is not much of interest for me. Thanks. Best regards, --  Héctor Orón "Our Sun

I'd just appreciate people being a little clearer about what they're attempting to do. Obviously I don't know how you've setup this balloon3 target but knowing this isn't an out the box

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

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

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

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

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

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

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,

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

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