OK, so do we keep 5.6 / 5.7 or remove them in favour of 5.8? I think this is probably too old for us to be declaring support for, since it has been unsupported upstream for some time

Thanks Tom, that solved it right away. -- Gtalk: daniel.toussaint@... Skype: supertoussi Cell: +886-915-680-291

Hi, I just sent a patch yesterday to fix similar problems in some other BSPs. The fix was to replace this: with this: FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" Can you try making that change

Hello All, Im using yocto with meta-ti and meta-openembedded. I have some packeges in my local.conf. IMAGE_INSTALL_append = " \ tcc \ curl \ perl \ minicom \

I have my own custom layer on top of Yocto. My layer provides a custom machine , custom image and a couple of applications that go into it. My problem : Nomatter what I do, I can't get my own custom

Hi Kevin, This needs to be: PRINC = "1" or, to ensure other layers can also increment the value: PRINC := "${@int(PRINC) + 1}" Cheers, Paul -- Paul Eggleton Intel Open Source Technology

This mail was sent out by Package Report System. It will list all the recipes which can't check upstream version by script, and will show how long it is since their last mannual version check. You can

This mail was sent out by Package Report System. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade this time, they can fill in

From: Tom Zanussi <tom.zanussi@...> The xserver-xf86-config .bbappends are still using FILESPATH - update them to use FILESEXTRAPATHS as recommended by the Poky Reference Manual and BSP

From: Tom Zanussi <tom.zanussi@...> This patchset fixes Yocto bug Bug 3158 [xserver-xorg-config_0.1.bbappend bsp FILESPATH not set in a robust manner]. meta-cedartrail: add machine override

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, We are pleased to announce the fourth milestone of the coming release of Yocto 1.3. This milestone release is available

Thanks Tom, I've been frequently flipping between atom-pc and cedartrail and this was getting annoying. Ross

Correct the port order to only list SDVOB and LVDS. Update the Edid flags as appropriate. No EDID over LVDS. Enable built-in and edid timings as well as DTDs for the SDVOB port. Force 24-bit mode

Correct the port order to only list SDVOB and LVDS. Update the Edid flags as appropriate. No EDID over LVDS. Enable built-in and edid timings as well as DTDs for the SDVOB port. Force 24-bit mode

I don't think it is just the intel ones. All the BSPs I've looked at had this problem. The yocto-bsp also creates packages that add to the problem, as it's finished product adds files that end up in

From the perspective of a new, easily confused and overwhelmed user, I whole heartedly agree with the index entry. And now it makes sense why there is a PV to store version of a recipe.

The version of nfsd used in 3.4 kernels tries to upcall the new reboot-recovery daemon and gets stuck if it is not found. This causes client mounts to fail and prints the following error message

The new recovery mechanism used by nfs in 3.4 kernels is currently failing when building baryon against poky 1.3_M3. This workaround causes nfs to revert back to the old recovery mechanism. The issue

<paul.eggleton@...> wrote: Not that it matters in the grand scheme of things, but I would be in favour of switching the variable names. Consistency is as consistency does; if there's any

(I answered Scott privately by mistake - here's some feedback on-list) I'm in favor of mentioning the history somewhere, because the names do have a 'P' in them, and this is confusing