Date   

Re: Meta Intel / Cedartrail / Denzil - how to get unionfs in the kernel

Bruce Ashfield
 

On Sun, Oct 7, 2012 at 6:08 PM, Chris Tapp <opensource@...> wrote:
On 7 Oct 2012, at 03:00, Saxena, Rahul wrote:

Try adding the unionfs feature (below) to your kernel:

http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/tree/meta/cfg/kernel-cache/features/unionfs?h=meta

create a file my_cedartrail.scc with following line:
include features/unionfs/unionfs.scc

put this file in a dir linux-yocto, the dir being created in

meta-cedartrail/recipes-kernel/linux

add following line in meta-cedartrail/recipes-kernel/Linux/linux-yocto_3.0.bbappend

SRC_URI +="file://my_cedartrail.scc"
Thanks - I thought just running 'menuconfig' would allow me to enable it (for a quick test).

However, this still doesn't seem to be working. I can see that 'my_cedartrail.scc' gets fetched in to the build area, but I still don't see CONFIG_UNION_FS if I run 'menuconfig'. There is also no 'unionfs' folder in fs/ of the build tree.

Also, if I specify an invalid feature (e.g. feature2/unionfs/unionfs.scc) I'm not seeing any diagnostic.
unionfs was never merged to the 3.0 kernel, I re-added it to the development
trees for 3.2 and the 3.4 kernel (aufs for the 3.6 tree at the moment). The meta
data is carried forward from the older kernels as a placeholder and is
documented
in the .scc file itself:

-----------------------
kconf non-hardware unionfs.cfg

# commented pending update to a newer version ported to 2.6.35+
# patch unionfs-2.5.4-integration.patch
-----------------------

So to get unionfs in the 3.0 kernel, we'd need a port .. but since
we've moved on
quite a bit past 3.0, I don't know of any pending ports myself.

Cheers,

Bruce



-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Chris Tapp
Sent: Saturday, October 06, 2012 5:43 PM
To: yocto@... Project
Subject: [yocto] Meta Intel / Cedartrail / Denzil - how to get unionfs in the kernel

I' trying to enable unionfs in the 3.0.32 kernel for the cedartrail BSP under Denzil 7.0.1.

However, the CONFIG_UNION_FS config flag isn't in the .config ...

Is there something else I need to enable, or do I need to find another way?

Chris Tapp

opensource@...
www.keylevel.com



_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
Chris Tapp

opensource@...
www.keylevel.com



_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"


Re: core-image-sato keyboard

Ross Burton <ross.burton@...>
 

On Saturday, 6 October 2012 at 20:20, Edward Vidal wrote:
Hello,
Just built core-image-sato for beagleboard xM C.
I have a usb keyboard and mouse connected. The Mouse works but not the keyboard when Terminal is selected. The virtual keyboard works okay.

Does the keyboard work at a console? Can you try an alternative keyboard and USB socket to rule out weird behaviour with the keyboard or USB socket?

Ross


Re: Meta Intel / Cedartrail / Denzil - how to get unionfs in the kernel

Chris Tapp
 

On 7 Oct 2012, at 03:00, Saxena, Rahul wrote:

Try adding the unionfs feature (below) to your kernel:

http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/tree/meta/cfg/kernel-cache/features/unionfs?h=meta

create a file my_cedartrail.scc with following line:
include features/unionfs/unionfs.scc

put this file in a dir linux-yocto, the dir being created in

meta-cedartrail/recipes-kernel/linux

add following line in meta-cedartrail/recipes-kernel/Linux/linux-yocto_3.0.bbappend

SRC_URI +="file://my_cedartrail.scc"
Thanks - I thought just running 'menuconfig' would allow me to enable it (for a quick test).

However, this still doesn't seem to be working. I can see that 'my_cedartrail.scc' gets fetched in to the build area, but I still don't see CONFIG_UNION_FS if I run 'menuconfig'. There is also no 'unionfs' folder in fs/ of the build tree.

Also, if I specify an invalid feature (e.g. feature2/unionfs/unionfs.scc) I'm not seeing any diagnostic.


-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Chris Tapp
Sent: Saturday, October 06, 2012 5:43 PM
To: yocto@... Project
Subject: [yocto] Meta Intel / Cedartrail / Denzil - how to get unionfs in the kernel

I' trying to enable unionfs in the 3.0.32 kernel for the cedartrail BSP under Denzil 7.0.1.

However, the CONFIG_UNION_FS config flag isn't in the .config ...

Is there something else I need to enable, or do I need to find another way?

Chris Tapp

opensource@...
www.keylevel.com



_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
Chris Tapp

opensource@...
www.keylevel.com


Re: Meta Intel / Cedartrail / Denzil - how to get unionfs in the kernel

Saxena, Rahul <rahul.saxena@...>
 

Try adding the unionfs feature (below) to your kernel:

http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/tree/meta/cfg/kernel-cache/features/unionfs?h=meta

create a file my_cedartrail.scc with following line:
include features/unionfs/unionfs.scc

put this file in a dir linux-yocto, the dir being created in

meta-cedartrail/recipes-kernel/linux

add following line in meta-cedartrail/recipes-kernel/Linux/linux-yocto_3.0.bbappend

SRC_URI +="file://my_cedartrail.scc"

Rebuild..

Thanks
Rahul

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Chris Tapp
Sent: Saturday, October 06, 2012 5:43 PM
To: yocto@... Project
Subject: [yocto] Meta Intel / Cedartrail / Denzil - how to get unionfs in the kernel

I' trying to enable unionfs in the 3.0.32 kernel for the cedartrail BSP under Denzil 7.0.1.

However, the CONFIG_UNION_FS config flag isn't in the .config ...

Is there something else I need to enable, or do I need to find another way?

Chris Tapp

opensource@...
www.keylevel.com



_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Meta Intel / Cedartrail / Denzil - how to get unionfs in the kernel

Chris Tapp
 

I' trying to enable unionfs in the 3.0.32 kernel for the cedartrail BSP under Denzil 7.0.1.

However, the CONFIG_UNION_FS config flag isn't in the .config ...

Is there something else I need to enable, or do I need to find another way?

Chris Tapp

opensource@...
www.keylevel.com


[Package Report System]Upgrade recipes name list

Yocto Project Package Report System <package-reporting@...>
 

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 RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this recipe remainder until newer upstream version was detected.
Example:
RECIPE_NO_UPDATE_REASON_pn-"xxx" = "Not upgrade to 2.0 because the new version is unstable"
You can check the detail information at http://packages.yoctoproject.org/upgradepkgname


PackageName Version UpVersion Maintainer NoUpgradeReason
ccache 3.1.7 3.1.8 Wenzong Fan <wenzong.fan@...>
xdg-utils 1.0.2 1.1.0 Valentin Popa <valentin.popa@...>
liberation-fonts 1.04 2.00.0 Valentin Popa <valentin.popa@...>
libxslt 1.1.26 1.1.27 Valentin Popa <valentin.popa@...>
evolution-data-server 2.30+git1+3ca578d968d097 6.0 Valentin Popa <valentin.popa@...>
puzzles r9594 9660 Valentin Popa <valentin.popa@...>
matchbox-panel-2 0.0+git1+cdf7a22716b8746 2.0 Valentin Popa <valentin.popa@...>
lttng-viewer 0.12.38 0.12.38.21032011 Valentin Popa <valentin.popa@...>
sysprof 1.1.8+git1+4692f85f625f4 1.2.0 Tom Zanussi <tom.zanussi@...>
shadow 4.1.4.3 4.1.5.1 Scott Garman <scott.a.garman@...>
sudo 1.8.5p2 1.8.6 Scott Garman <scott.a.garman@...>
blktool 4-6 4 Scott Garman <scott.a.garman@...>
apmd 3.2.2-14 3.2.2 Scott Garman <scott.a.garman@...>
openssh 6.0p1 6.1p1 Scott Garman <scott.a.garman@...>
mc 4.8.4 4.8.6 Saul Wold <sgw@...>
libtasn1 2.13 2.14 Saul Wold <sgw@...>
libnl 2.0 3.2.13 Saul Wold <sgw@...> libnl-3.2.2 is incompatible w...
createrepo 0.4.11 0.9.9 Saul Wold <sgw@...> Versions after 0.9.* use YUM,...
apt 0.7.14 0.9.7.5 Saul Wold <sgw@...>
pkgconfig 0.25 0.27.1 Saul Wold <sgw@...> 0.26 removes glib-conf, adds ...
build-appliance-image 1.0 3.2.1 Saul Wold <sgw@...>
util-linux 2.21.2 2.22 Saul Wold <sgw@...>
libxml2 2.8.0 2.9.0 Saul Wold <sgw@...>
resolvconf 1.67 1.68 Saul Wold <sgw@...>
dhcp 4.2.4-P1 4.2.4 Saul Wold <sgw@...> ftp://ftp.isc.org/isc/dhcp/4.2.4-P1/dhcp-4.2.4-P1.tar.gz
tiff 4.0.2 4.0.3 Saul Wold <sgw@...>
logrotate 3.8.1 3.8.2 Robert Yang <liezhi.yang@...>
liburcu 0.6.7 0.7.4 Radu Moisan <radu.moisan@...>
curl 7.26.0 7.27.0 Radu Moisan <radu.moisan@...>
js 1.7.0+1.8.0rc1 1.60 Radu Moisan <radu.moisan@...>
u-boot-mkimage 2011.06 2012.07 Radu Moisan <radu.moisan@...>
valgrind 3.7.0 3.8.1 Radu Moisan <radu.moisan@...>
babeltrace 0.12+git1+0d8f8c2ea27df0 1.0.0 Radu Moisan <radu.moisan@...>
udev 164 182 Radu Moisan <radu.moisan@...>
mobile-broadband-provider-info1.0.0+gitr1+d9995ef693cb 20090309 Radu Moisan <radu.moisan@...>
nativesdk-bdwgc 20110107 7.2alpha5 No Maintainer information
nativesdk-curl 7.26.0 7.27.0 No Maintainer information
libksba 1.2.0 1.3.0 No Maintainer information
cmake 2.8.8 2.8.9 No Maintainer information
nativesdk-cmake 2.8.8 2.8.9 No Maintainer information
nativesdk-automake 1.12.3 1.12.4 No Maintainer information
nativesdk-pkgconfig 0.25 0.27.1 No Maintainer information
nativesdk-perl 5.14.2 5.17.4 No Maintainer information
lttng-modules 2.0.pre11+git4d3e89e379f 2.1.0 No Maintainer information
nativesdk-linux-libc-headers 3.4.3 3.6 No Maintainer information
nativesdk-linux-libc-headers- 3.4+git-1+a1cdb60720c452 3.4.9 No Maintainer information
nativesdk-libxml2 2.8.0 2.9.0 No Maintainer information
nativesdk-zlib 1.2.7 121 No Maintainer information
libdumpvalue-perl 1.16 1.17 No Maintainer information
nativesdk-openssl 1.0.0j 1.0.1 No Maintainer information
zypper 1.5.3-git1+2c5bb6ceb99ec 11.0 Mark Hatle <mark.hatle@...>
libzypp 0.0-git1+15b6c52260bbc52 11.0 Mark Hatle <mark.hatle@...>
fontconfig 2.9.0 2.10.1 Laurentiu Palcu <laurentiu.palcu@...>
xkeyboard-config 2.1 2.6.99 Laurentiu Palcu <laurentiu.palcu@...>
xserver-xorg 1.11.2 1.13.0 Laurentiu Palcu <laurentiu.palcu@...>
xf86-input-mouse 1.7.2 1.8.1 Laurentiu Palcu <laurentiu.palcu@...>
xf86-input-evdev 2.7.0 2.7.3 Laurentiu Palcu <laurentiu.palcu@...>
xf86-video-vesa 2.3.1 2.3.2 Laurentiu Palcu <laurentiu.palcu@...>
xf86-video-fbdev 0.4.2 0.4.3 Laurentiu Palcu <laurentiu.palcu@...>
xf86-video-intel 2.19.0 2.20.8 Laurentiu Palcu <laurentiu.palcu@...>
xf86-input-keyboard 1.6.1 1.6.2 Laurentiu Palcu <laurentiu.palcu@...>
ghostscript 9.05 9.06 Kai Kang <kai.kang@...>
directfb 1.6.1 1.6.2 Kai Kang <kai.kang@...>
qmmp 0.6.1 0.6.3 Kai Kang <kai.kang@...>
syslinux 4.03 4.05 Darren Hart <dvhart@...> Waiting for 4.06 for 3.3 kern...
net-tools 1.60-23 1.60 Cristian Iorga <cristian.iorga@...>
connman 1.4 1.7 Cristian Iorga <cristian.iorga@...>
ofono 1.10 1.11 Cristian Iorga <cristian.iorga@...>
telepathy-mission-control 5.13.0 5.13.2 Cristian Iorga <cristian.iorga@...>
telepathy-glib 0.19.8 0.19.10 Cristian Iorga <cristian.iorga@...>
libmusicbrainz 3.0.3 4.0.0 Cristian Iorga <cristian.iorga@...>
gst-plugins-base 0.10.36 0.11.90 Cristian Iorga <cristian.iorga@...>
gst-ffmpeg 0.10.13 0.11.2 Cristian Iorga <cristian.iorga@...>
gst-plugins-good 0.10.31 0.11.90 Cristian Iorga <cristian.iorga@...>
gst-plugins-bad 0.10.23 0.11.90 Cristian Iorga <cristian.iorga@...>
gst-plugins-ugly 0.10.19 0.11.90 Cristian Iorga <cristian.iorga@...>
gstreamer 0.10.36 0.11.90 Cristian Iorga <cristian.iorga@...> upgrading to 0.11.1 causes gs...
gst-fluendo-mp3 0.10.19 0.10.20 Cristian Iorga <cristian.iorga@...>
libconvert-asn1-perl 0.22 0.26 Bogdan Marinescu <bogdan.a.marinescu@...>
patch 2.6.1 2.7 Bogdan Marinescu <bogdan.a.marinescu@...>
tcf-agent 0.4.0+git1+4ef94ecb927a8 8.0 Bogdan Marinescu <bogdan.a.marinescu@...>
automake 1.12.3 1.12.4 Bogdan Marinescu <bogdan.a.marinescu@...>
bison 2.5.1 2.6.2 Bogdan Marinescu <bogdan.a.marinescu@...>
nasm 2.10.01 2.10.05 Bogdan Marinescu <bogdan.a.marinescu@...>
lttng2-ust 2.0.2+git1+a367ee66aad3f 2.1.0 Bogdan Marinescu <bogdan.a.marinescu@...>
linux-libc-headers-yocto 3.4+git-1+a1cdb60720c452 3.4.9 Bogdan Marinescu <bogdan.a.marinescu@...>
linux-libc-headers 3.4.3 3.6 Bogdan Marinescu <bogdan.a.marinescu@...>
lttng-control 0.89 0.89.05122011 Bogdan Marinescu <bogdan.a.marinescu@...>
Upgradable Count: 82
Upgrade Total Count: 88
The based commit merge time is:
Thu Sep 27 16:15:38 2012 -0700
The based commit is:
commit fc1822fc6b3cbe6fb52e7f08eac4c6b624fba462
Author: Richard Purdie <richard.purdie@...>
Date: Thu Sep 27 23:06:06 2012 +0100
Any problem, please contact Saul Wold <sgw@...>


[Package Report System]Manual check recipes name list

Yocto Project Package Report System <package-reporting@...>
 

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 check the detail information at http://packages.yoctoproject.org/manuallychkinfo


PackageName Version LastChkVersion LastChkTime Maintainer NoUpgradeReason
lsb 4.1 4.1 172 day Yi Zhao <yi.zhao@...... 1.4 is fixed version of LSB Te...
freetype 2.4.10 2.4.10 93 days Valentin Popa <valentin.popa@... No data
menu-cache 0.3.3 0.3.3 41187 d Valentin Popa <valentin.popa@... No data
libfm 0.1.17 1.30 93 days Valentin Popa <valentin.popa@... No data
pcmanfm 0.9.10 0.9.10 93 days Valentin Popa <valentin.popa@... No data
gtkhtml2 2.11.0+svnr11... 2.11.1 41187 d Valentin Popa <valentin.popa@... No data
libevent 2.0.16 2.0.20 269 day Scott Garman <scott.a.garman@... No data
e2fsprogs 1.42.1 1.42.5 94 days Scott Garman <scott.a.garman@... No data
chrpath 0.14 0.14 94 days Scott Garman <scott.a.garman@... No data
opensp 1.5.2 1.5.2 94 days Scott Garman <scott.a.garman@... No data
expat 2.1.0 2.0.1 94 days Scott Garman <scott.a.garman@... No data
nfs-utils 1.2.3 1.2.6 94 days Scott Garman <scott.a.garman@... No data
libpng 1.2.49 1.5.11 94 days Scott Garman <scott.a.garman@... 1.4.3 and later changes the AP...
libatomics-ops 7.2 N/A 41187 d Scott Garman <scott.a.garman@... No data
cracklib 2.8.19 2.8.19 94 days Saul Wold <sgw@...... No data
psmisc 22.19 22.19 94 days Saul Wold <sgw@...... No data
sysstat 10.1.1 10.1.1 94 days Saul Wold <sgw@...... No data
less 444 444 94 days Saul Wold <sgw@...... No data
glew 1.9.0 1.9.0 94 days Saul Wold <sgw@...... No data
mx 1.4.6 N/A 41187 d Saul Wold <sgw@...... No data
libexif 0.6.21 0.6.21 94 days Saul Wold <sgw@...... No data
sqlite3 3.7.13 3.7.13 94 days Saul Wold <sgw@...... No data
boost 1.51.0 1.51.0 94 days Saul Wold <sgw@...... No data
libcheck 0.9.8 0.9.8 94 days Saul Wold <sgw@...... No data
libacpi 0.2 0.2 41187 d Saul Wold <sgw@...... No data
sysfsutils 2.1.0 2.1.0 94 days Saul Wold <sgw@...... No data
console-tools 0.3.2 0.3.2 94 days Saul Wold <sgw@...... No data
libmad 0.15.1b 0.15.2b 94 days Saul Wold <sgw@...... No data
popt 1.16 1.16 41187 d Saul Wold <sgw@...... No data
clutter-gst-1.8 1.4.6 N/A 41187 d Ross Burton <ross.burton@inte... No data
cogl 1.8.2 Jul 17, 2012 299 day Ross Burton <ross.burton@inte... No data
clutter-1.8 1.8.4 N/A 41187 d Ross Burton <ross.burton@inte... No data
clutter-gtk-1.8 0.11.4 N/A 41187 d Ross Burton <ross.burton@inte... No data
tzdata 2012d 2012c 93 days Radu Moisan <radu.moisan@inte... No data
bzip2 1.0.6 1.0.6 502 day Radu Moisan <radu.moisan@inte... No data
zip 3.0 3.0 93 days Radu Moisan <radu.moisan@inte... No data
watchdog 5.12 5.12 93 days Radu Moisan <radu.moisan@inte... No data
hdparm 9.39 9.39 93 days Radu Moisan <radu.moisan@inte... No data
tslib 1.0 1.0 93 days Radu Moisan <radu.moisan@inte... No data
unzip 6.0 6.0 93 days Radu Moisan <radu.moisan@inte... No data
beecrypt 4.2.1 4.2.1 93 days Radu Moisan <radu.moisan@inte... No data
setserial 2.17 2.17 165 day Radu Moisan <radu.moisan@inte... No data
acpid 1.0.10 1.0.10 93 days Radu Moisan <radu.moisan@inte... No data
squashfs-tools 4.2 4.2 93 days Radu Moisan <radu.moisan@inte... No data
u-boot-fw-utils 2011.06 20012.07 41187 d Radu Moisan <radu.moisan@inte... No data
ubootchart 0.0+r12 0.0+r12 41187 d Radu Moisan <radu.moisan@inte... No data
opkg 0.1.8+svnr633... 0.1.8 93 days Radu Moisan <radu.moisan@inte... No data
fotowall 0.9 0.9 41187 d Radu Moisan <radu.moisan@inte... No data
quicky 0.4 N/A 41187 d Radu Moisan <radu.moisan@inte... No data
kmod 9 9 41187 d Radu Moisan <radu.moisan@inte... No data
tinylogin 1.4 1.4 288 day Radu Moisan <radu.moisan@inte... No data
gupnp 0.16.1 0.18.4 41187 d Radu Moisan <radu.moisan@inte... No data
lame 3.99.5 3.99.5 93 days Radu Moisan <radu.moisan@inte... No data
nativesdk-libarchive... 2.8.5 N/A 41187 d No Maintainer information No data
nativesdk-bzip2 1.0.6 N/A 41187 d No Maintainer information No data
nativesdk-mpfr 3.1.0 N/A 41187 d No Maintainer information No data
nativesdk-sqlite3 3.7.13 N/A 41187 d No Maintainer information No data
nativesdk-db 5.3.15 N/A 41187 d No Maintainer information No data
nativesdk-libmpc 0.8.2 N/A 41187 d No Maintainer information No data
nativesdk-u-boot-mki... 2011.06 N/A 41187 d No Maintainer information No data
kconfig-frontends 3.5.0 3.5.0 41187 d No Maintainer information No data
nativesdk-pseudo 1.4.1 N/A 41187 d No Maintainer information No data
python-argparse 1.2.1 N/A 41187 d No Maintainer information No data
nativesdk-opkg 0.1.8+svnr633... N/A 41187 d No Maintainer information No data
nativesdk-chrpath 0.14 N/A 41187 d No Maintainer information No data
nativesdk-eglibc 2.16 N/A 41187 d No Maintainer information No data
libcgroup 0.37.1 0.38-1 41187 d No Maintainer information No data
nativesdk-expat 2.1.0 N/A 41187 d No Maintainer information No data
mpeg2dec 0.4.1 0.5.1 502 day No Maintainer information Why are we currently at 0.4.1?
nativesdk-alsa-lib 1.0.25 N/A 41187 d No Maintainer information No data
ltp 20120903 20120903 208 day Mihai Lindner <mihaix.lindner... No data
pseudo 1.4.1 1.2 340 day Mark Hatle <mark.hatle@windri... No data
prelink 1.0+git1+a2d8... 1.0+git1+9552... 268 day Mark Hatle <mark.hatle@windri... No data
rpm 5.4.9 5.4.10 41187 d Mark Hatle <mark.hatle@windri... No data
x11vnc 0.9.13 0.9.13 93 days Laurentiu Palcu <laurentiu.pa... No data
libarchive 2.8.5 3.0.4 41187 d Kai Kang <kai.kang@windriver.... No data
mingetty 1.08 1.08 269 day Kai Kang <kai.kang@windriver.... No data
alsa-tools 1.0.25 N/A 41187 d Kai Kang <kai.kang@windriver.... No data
adt-installer 0.1.8+svnr596... 1.1 41187 d Jessica Zhang <jessica.zhang@... No data
cwautomacros 20110201 20110201 93 days Cristian Iorga <cristian.iorg... No data
minicom 2.6.1 2.6.1 93 days Cristian Iorga <cristian.iorg... No data
libtirpc 0.2.2 0.2.2 93 days Cristian Iorga <cristian.iorg... No data
rpcbind 0.2.0 0.2.0 93 days Cristian Iorga <cristian.iorg... No data
quota 4.00 4.00 93 days Cristian Iorga <cristian.iorg... No data
db 5.3.15 5.0.26 41187 d Cristian Iorga <cristian.iorg... API compatibility issue
libproxy 0.4.7 0.4.7 616 day Cristian Iorga <cristian.iorg... No data
taglib 1.8 1.7.2 616 day Cristian Iorga <cristian.iorg... No data
lrzsz 0.12.20 0.12.20 616 day Cristian Iorga <cristian.iorg... No data
libical 0.48 0.48 93 days Cristian Iorga <cristian.iorg... No data
wireless-tools 29 29 93 days Cristian Iorga <cristian.iorg... No data
irda-utils 0.9.18 0.9.18 93 days Cristian Iorga <cristian.iorg... No data
libpcap 1.3.0 4.3.0 41187 d Cristian Iorga <cristian.iorg... No data
gssdp 0.10.0 0.10.0 41187 d Cristian Iorga <cristian.iorg... No data
gupnp-tools 0.8.1 N/A 41187 d Cristian Iorga <cristian.iorg... No data
gupnp-av 0.8.0 0.10.3 41187 d Cristian Iorga <cristian.iorg... No data
tremor 20120314 20120122 41187 d Cristian Iorga <cristian.iorg... No data
liba52 0.7.4 0.7.4 616 day Cristian Iorga <cristian.iorg... No data
flac 1.2.1 1.2.1 93 days Cristian Iorga <cristian.iorg... No data
libomxil 0.9.3 0.9.3 93 days Cristian Iorga <cristian.iorg... No data
libsamplerate0 0.1.8 0.1.8 93 days Cristian Iorga <cristian.iorg... No data
alsa-utils 1.0.25 N/A 41187 d Cristian Iorga <cristian.iorg... No data
alsa-lib 1.0.25 N/A 41187 d Cristian Iorga <cristian.iorg... No data
mpfr 3.1.0 3.1.1 93 days Bogdan Marinescu <bogdan.a.ma... No data
libpcre 8.31 8.31 93 days Bogdan Marinescu <bogdan.a.ma... No data
libmpc 0.8.2 0.9 621 day Bogdan Marinescu <bogdan.a.ma... No data
python-scons 2.1.0 2.2.0 41187 d Bogdan Marinescu <bogdan.a.ma... No data
distcc 2.18.3 3.1.1 41187 d Bogdan Marinescu <bogdan.a.ma... No data
intltool 0.50.0 0.50.2 41187 d Bogdan Marinescu <bogdan.a.ma... No data
strace 4.7 4.7 93 days Bogdan Marinescu <bogdan.a.ma... No data
git 1.7.7 N/A 41187 d Bogdan Marinescu <bogdan.a.ma... No data
tcl 8.5.11 8.5.12 93 days Bogdan Marinescu <bogdan.a.ma... No data
powertop 1.13 1.97 536 day Bogdan Marinescu <bogdan.a.ma... Do not upgrade to version 1.97...
oprofile 0.9.7 0.9.8 93 days Bogdan Marinescu <bogdan.a.ma... No data
latencytop 0.5 0.5 536 day Bogdan Marinescu <bogdan.a.ma... No data
eglibc 2.16 git:16540 280 day Bogdan Marinescu <bogdan.a.ma... No data
Manual Check Count: 115
Manual Need Check Count: 115
Any problem, please contact Saul Wold <sgw@...>


core-image-sato keyboard

Edward Vidal <vidal.develone@...>
 

Hello,
Just built core-image-sato for beagleboard xM C.
I have a usb keyboard and mouse connected.  The Mouse works but not the keyboard when Terminal is selected.  The virtual keyboard works okay.
The following is what I see with dmesg.
usb 1-2.2: new low-speed USB device number 4 using ehci-omap
input: CHESEN USB Keyboard as /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.2/1-2.2:1.0/input/input
0
generic-usb 0003:0A81:0101.0001: input: USB HID v1.10 Keyboard [CHESEN USB Keyboard] on usb-ehci-omap.0-2.2
/input0
input: CHESEN USB Keyboard as /devices/platform/usbhs_omap/ehci-omap.0/usb1/1-2/1-2.2/1-2.2:1.1/input/input
1
generic-usb 0003:0A81:0101.0002: input: USB HID v1.10 Device [CHESEN USB Keyboard] on usb-ehci-omap.0-2.2/i
nput1

The file /etc/formfactor/machconfig
# Assume a USB mouse and touchscreen are connected
HAVE_TOUCHSCREEN=0
HAVE_KEYBOARD=1
I chmod +x /etc/formfactor/config and /etc/formfactor/matchconfig
Thanks in advance for any help



Re: HTTP-accessible poky repo?

Evade Flow <evadeflow@...>
 

On Fri, Oct 5, 2012 at 10:51 AM, Evade Flow <evadeflow@...> wrote:
I'd like to track yocto development more closely, but I'm stuck behind a
restrictive HTTP-only firewall all day at work. Is there an official
(or unofficial-but-up-to-date), HTTP-accessible mirror of
git://git.yoctoproject.org/poky.git I can clone from?

I can create a clone on github and run some cron scripts at home to sync
it, but I'd rather not bother if there's already something like this out
there...
It seems no one is particularly interested in this. Oh, well. FWIW, I put
a couple mirrors here:

- http://github.com/yoctoproject-mirrors

I figured this would make it easier for me to track upstream development
from behind the firewall at work. (*Now* I'm sure people will chime in
and tell me there's already a complete set of HTTP-accessible mirrors
somewhere... :-})


Re: [PATCH 0/1] meta-tlk: fix included file name

Tom Zanussi <tom.zanussi@...>
 

Pulled into meta-intel/master.

Thanks,

Tom

On Sat, 2012-10-06 at 18:16 +0300, Mihai Lindner wrote:
PN in linux-yocto-tlk.inc takes the .inc file name and becomes
linux-yocto-tlk. Renamed to linux-yocto_tlk.inc to avoid confusions.
Related to: [YOCTO #3217]

Signed-off-by: Mihai Lindner <mihaix.lindner@...>
---
The following changes since commit 7228f6b0c81817c8a8455ea78271abfd5d66fed8:

meta-tlk: fix ignored SRC_URI appends (2012-10-05 14:47:55 -0500)

are available in the git repository at:

git://git.yoctoproject.org/poky-contrib mihai/bug3217
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mihai/bug3217

Mihai Lindner (1):
meta-tlk: fix included file name

meta-tlk/recipes-kernel/linux/linux-yocto_3.0.bbappend | 2 +-
meta-tlk/recipes-kernel/linux/linux-yocto_3.2.bbappend | 2 +-
meta-tlk/recipes-kernel/linux/linux-yocto_3.4.bbappend | 2 +-
.../recipes-kernel/linux/{linux-yocto-tlk.inc => linux-yocto_tlk.inc} | 0
4 files changed, 3 insertions(+), 3 deletions(-)
rename meta-tlk/recipes-kernel/linux/{linux-yocto-tlk.inc => linux-yocto_tlk.inc} (100%)


[PATCH 1/1] meta-tlk: fix included file name

Mihai Lindner <mihaix.lindner@...>
 

PN in linux-yocto-tlk.inc takes the .inc file name and becomes
linux-yocto-tlk. Renamed to linux-yocto_tlk.inc to avoid confusions.
Related to: [YOCTO #3217]

Signed-off-by: Mihai Lindner <mihaix.lindner@...>
---
meta-tlk/recipes-kernel/linux/linux-yocto_3.0.bbappend | 2 +-
meta-tlk/recipes-kernel/linux/linux-yocto_3.2.bbappend | 2 +-
meta-tlk/recipes-kernel/linux/linux-yocto_3.4.bbappend | 2 +-
.../recipes-kernel/linux/{linux-yocto-tlk.inc => linux-yocto_tlk.inc} | 0
4 files changed, 3 insertions(+), 3 deletions(-)
rename meta-tlk/recipes-kernel/linux/{linux-yocto-tlk.inc => linux-yocto_tlk.inc} (100%)

diff --git a/meta-tlk/recipes-kernel/linux/linux-yocto_3.0.bbappend b/meta-tlk/recipes-kernel/linux/linux-yocto_3.0.bbappend
index e316320..f580168 100644
--- a/meta-tlk/recipes-kernel/linux/linux-yocto_3.0.bbappend
+++ b/meta-tlk/recipes-kernel/linux/linux-yocto_3.0.bbappend
@@ -1 +1 @@
-require ${PN}-tlk.inc
+require ${PN}_tlk.inc
diff --git a/meta-tlk/recipes-kernel/linux/linux-yocto_3.2.bbappend b/meta-tlk/recipes-kernel/linux/linux-yocto_3.2.bbappend
index e316320..f580168 100644
--- a/meta-tlk/recipes-kernel/linux/linux-yocto_3.2.bbappend
+++ b/meta-tlk/recipes-kernel/linux/linux-yocto_3.2.bbappend
@@ -1 +1 @@
-require ${PN}-tlk.inc
+require ${PN}_tlk.inc
diff --git a/meta-tlk/recipes-kernel/linux/linux-yocto_3.4.bbappend b/meta-tlk/recipes-kernel/linux/linux-yocto_3.4.bbappend
index e316320..f580168 100644
--- a/meta-tlk/recipes-kernel/linux/linux-yocto_3.4.bbappend
+++ b/meta-tlk/recipes-kernel/linux/linux-yocto_3.4.bbappend
@@ -1 +1 @@
-require ${PN}-tlk.inc
+require ${PN}_tlk.inc
diff --git a/meta-tlk/recipes-kernel/linux/linux-yocto-tlk.inc b/meta-tlk/recipes-kernel/linux/linux-yocto_tlk.inc
similarity index 100%
rename from meta-tlk/recipes-kernel/linux/linux-yocto-tlk.inc
rename to meta-tlk/recipes-kernel/linux/linux-yocto_tlk.inc
--
1.7.12


[PATCH 0/1] meta-tlk: fix included file name

Mihai Lindner <mihaix.lindner@...>
 

PN in linux-yocto-tlk.inc takes the .inc file name and becomes
linux-yocto-tlk. Renamed to linux-yocto_tlk.inc to avoid confusions.
Related to: [YOCTO #3217]

Signed-off-by: Mihai Lindner <mihaix.lindner@...>
---
The following changes since commit 7228f6b0c81817c8a8455ea78271abfd5d66fed8:

meta-tlk: fix ignored SRC_URI appends (2012-10-05 14:47:55 -0500)

are available in the git repository at:

git://git.yoctoproject.org/poky-contrib mihai/bug3217
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mihai/bug3217

Mihai Lindner (1):
meta-tlk: fix included file name

meta-tlk/recipes-kernel/linux/linux-yocto_3.0.bbappend | 2 +-
meta-tlk/recipes-kernel/linux/linux-yocto_3.2.bbappend | 2 +-
meta-tlk/recipes-kernel/linux/linux-yocto_3.4.bbappend | 2 +-
.../recipes-kernel/linux/{linux-yocto-tlk.inc => linux-yocto_tlk.inc} | 0
4 files changed, 3 insertions(+), 3 deletions(-)
rename meta-tlk/recipes-kernel/linux/{linux-yocto-tlk.inc => linux-yocto_tlk.inc} (100%)

--
1.7.12


[PATCHv3 1/1] crownbay.conf: add kernel parameters for EMGD video acceleration

nitin.a.kamble@...
 

From: Nitin A Kamble <nitin.a.kamble@...>

This is recommended in the EMGD User Guide.

My understanding is that, the emgd kernel driver need
to allocate memory dynamically, and the "vmalloc=256MB"
parameter ensures enough will be available for the driver.

Signed-off-by: Nitin A Kamble <nitin.a.kamble@...>
---
meta-crownbay/conf/machine/crownbay.conf | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta-crownbay/conf/machine/crownbay.conf b/meta-crownbay/conf/machine/crownbay.conf
index 40dbd1d..c18fa1d 100644
--- a/meta-crownbay/conf/machine/crownbay.conf
+++ b/meta-crownbay/conf/machine/crownbay.conf
@@ -21,7 +21,7 @@ PREFERRED_VERSION_xserver-xorg ?= "1.9.3"
PREFERRED_VERSION_mesa-dri ?= "7.11"
PREFERRED_VERSION_xf86-input-evdev ?= "2.6.0"

-APPEND += "video=vesafb vga=0x318"
+APPEND += "video=vesafb vga=0x318 vmalloc=256MB"

VA_FEATURES = "${@bb.utils.contains("LICENSE_FLAGS_WHITELIST", \
"commercial", "gst-va-intel va-intel", "va-intel", d)}"
--
1.7.3.4


[PATCHv3 0/1] meta-intel misc commits

nitin.a.kamble@...
 

From: Nitin A Kamble <nitin.a.kamble@...>

Updated the kernel command line for crownbay BSP, after discussions with Darren.

Thanks,
Nitin

The following changes since commit 7228f6b0c81817c8a8455ea78271abfd5d66fed8:

meta-tlk: fix ignored SRC_URI appends (2012-10-05 14:47:55 -0500)

are available in the git repository at:
git://git.yoctoproject.org/meta-intel-contrib nitin/misc
http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin/misc

Nitin A Kamble (1):
crownbay.conf: add kernel parameters for EMGD video acceleration

meta-crownbay/conf/machine/crownbay.conf | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

--
1.7.3.4


Re: [PATCHv2 1/1] crownbay.conf: add kernel parameters for EMGD video acceleration

Kamble, Nitin A <nitin.a.kamble@...>
 

-----Original Message-----
From: Hart, Darren
Sent: Thursday, October 04, 2012 3:34 PM
To: Kamble, Nitin A
Cc: Zanussi, Tom; yocto@...
Subject: Re: [PATCHv2 1/1] crownbay.conf: add kernel parameters for EMGD
video acceleration

On 10/04/2012 03:23 PM, nitin.a.kamble@... wrote:
From: Nitin A Kamble <nitin.a.kamble@...>

This is recommended in the EMGD User Guide.

My understanding is the emgd kernel driver need to allocate memory
dynamically, and the "vmalloc=256MB" parameter ensures enough will be
available for the driver.
OK, this explains the change to vmalloc.

Why the change of vga=current and the drop of video=vesafb ?
Darren,
Good catch. I changed this for cleanup, but now I see that it affects the splash screen. So I will resend the commit by dropping these extra changes.

Thanks,
Nitin



--
Darren


Signed-off-by: Nitin A Kamble <nitin.a.kamble@...>
---
meta-crownbay/conf/machine/crownbay.conf | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta-crownbay/conf/machine/crownbay.conf
b/meta-crownbay/conf/machine/crownbay.conf
index 40dbd1d..f02615e 100644
--- a/meta-crownbay/conf/machine/crownbay.conf
+++ b/meta-crownbay/conf/machine/crownbay.conf
@@ -21,7 +21,7 @@ PREFERRED_VERSION_xserver-xorg ?= "1.9.3"
PREFERRED_VERSION_mesa-dri ?= "7.11"
PREFERRED_VERSION_xf86-input-evdev ?= "2.6.0"

-APPEND += "video=vesafb vga=0x318"
+APPEND += "vga=current vmalloc=256MB"

VA_FEATURES = "${@bb.utils.contains("LICENSE_FLAGS_WHITELIST", \
"commercial", "gst-va-intel va-intel", "va-intel", d)}"
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


Re: [PATCH 0/1] meta-tlk: fix ignored SRC_URI appends

Tom Zanussi <tom.zanussi@...>
 

On Fri, 2012-10-05 at 14:20 +0300, Mihai Lindner wrote:
Fix SRC_URI appends ignored by meta-cedartrail and meta-crownbay. Used
SRC_URI_append instead of SRC_URI.
Also placed all variables in an .inc file to be required by all
linux-yocto recipes in here, since all versions use the same.

[YOCTO #3217]

Signed-off-by: Mihai Lindner <mihaix.lindner@...>
---
The following changes since commit 6eea475e2038c1de3fbbd5bcd0986862ff85bb9a:

meta-crownbay: remove 3.0 kernel support (2012-10-04 20:20:52 -0500)

are available in the git repository at:

git://git.yoctoproject.org/poky-contrib mihai/bug3217
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mihai/bug3217
Pulled into meta-intel/master.

Thanks,

Tom

Mihai Lindner (1):
meta-tlk: fix ignored SRC_URI appends

meta-tlk/recipes-kernel/linux/linux-yocto.inc | 3 +++
meta-tlk/recipes-kernel/linux/linux-yocto_3.0.bbappend | 7 +------
meta-tlk/recipes-kernel/linux/linux-yocto_3.2.bbappend | 7 +------
meta-tlk/recipes-kernel/linux/linux-yocto_3.4.bbappend | 7 +------
4 files changed, 6 insertions(+), 18 deletions(-)
create mode 100644 meta-tlk/recipes-kernel/linux/linux-yocto.inc


Re: Yocto Project 1.3 beta feedback

Rifenbark, Scott M <scott.m.rifenbark@...>
 

Andrea,

Thanks for the detailed feedback on the YP documentation. Agree that it is difficult to meet the needs of the wide group of users and that it is difficult to have the released documentation match that of the "latest" from the website. The "latest" documentation is always under development and I fear will never match the released documentation. One radical scheme to consider is releasing a separate tarball for documentation that a user could download and then insert into their poky repository on the local system. This would in a sense de-couple the docs and the released poky tarball. Probably not a popular idea among the team but an out-of-the-box one nonetheless.

We will continue to try and improve specific workflows based on specific target audience needs. Feedback such as this helps.

Scott

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Andrea Galbusera
Sent: Friday, October 05, 2012 8:43 AM
To: yocto@...
Subject: [yocto] Yocto Project 1.3 beta feedback

Below you can find my answers to the Yocto Project 1.3 beta testing survey.

Regards,
Andrea


Experience survey of using Yocto 1.3

Q: Which architecture did you choose to build?

A: qemuppc, beagleboard

Q: How easily were you able to build an image and boot an image?

A: Quite easily. I also took some time for reviewing the QS guide
which looks adequate to me either for newbies or users coming from
different build systems.

Q: Is there any surprise to you in the process of doing this Beta
testing? If so, would you please describe
it and tell us how you expected it to work?

A: Not really a surprise (already knew about that), but a very
pleasant experience was knotty2. It results cleaner than its
"forever-scrolling" parent.

Q: How do you like our HOB interface? Please provide us with your
thoughts and suggestions on HOB
interface and functionality.

A: I like the hob design. It actually does not support yet a few
workflows that I consider much important for my work: i.e. adding new
recipes, supporting kernel development (mainly configuration,
patching). I understand not every user does require them and hence I
don't consider myself as the actual hob's average target user. Anyway
I appreciate the project is working on more intuitive tools like HOB
and I look forward to see if similar effort will also bring us webhob
experience in the future. People doing mainly package integration
would benefit the best from HOB, since they need not to dig into the
build system's details.

Q: Was it easy to find the support you needed to build and boot an image?

A: Procedures for the official emulated target are well documented and
clear enough for the task required by this beta testing. Support for
deploying and booting on reference real-hardware target is a little
bit lacking but a lot of resources and documentation are already
available online and I agree on not duplicating reference material.

Q: Which Bugzilla reports did you submit?

A: None till now. Still investigating on some oddities and discussing
with the team on IRC. Also hit bug #3135, which is already fixed in
master now.

Q: Did you try anything else with Yocto 1.3?

A: Building an SDK and investigating procedures to deploy toolchains,
SDKs and ADTs is one of my primary goals. I built toolchains for the
arm architecture and tested the environment to build a simple C
source. Relocatable SDK is a good improvement in term of flexibility
when deploying for application developers. The beta snapshot does
bring bug #3135, but it's already fixed in master.

Q: What would you like to have in Yocto Project for future releases?

A: Documentation as a whole IMHO should and must improve a bit to make
it more useful for reference. At the design level, I see the team is
working very well, by keeping the documentation in a single place:
this grants us consistency and its really a good point. I still see
some confusion between online documentation, documentation source you
can build from master and the "latest" online documentation which is
often referenced on the mailing list. However I know that keeping all
the docs up-to-date and consistent is not an easy job.
Needs with respect to documentation do largely depend on the user's
perspective. For instance, if your goal is writing new recipes for
your own layers, you'll ask for a good variables reference and, maybe,
a reasonable checklist with best conventions for keeping metadata
consistent. This is also required if you want to contribute back with
high degree of confidence that your patches will be considered and
reviewed. If, on the other hand, your are more involved in kernel
configuration and customization, your hope is to keep your work as
much as possible integrated with the build system: this will grant you
a closer develop-deploy-test flow by using the same tools will be used
for production. Such a workflow does have documentation but I
personally believe this is a point we can improve a lot.
Yocto Project users do belong to a very heterogeneous base: I see a
great challenge in keeping docs usable by differently focused people!
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Yocto Project 1.3 beta feedback

Andrea Galbusera
 

Below you can find my answers to the Yocto Project 1.3 beta testing survey.

Regards,
Andrea


Experience survey of using Yocto 1.3

Q: Which architecture did you choose to build?

A: qemuppc, beagleboard

Q: How easily were you able to build an image and boot an image?

A: Quite easily. I also took some time for reviewing the QS guide
which looks adequate to me either for newbies or users coming from
different build systems.

Q: Is there any surprise to you in the process of doing this Beta
testing? If so, would you please describe
it and tell us how you expected it to work?

A: Not really a surprise (already knew about that), but a very
pleasant experience was knotty2. It results cleaner than its
"forever-scrolling" parent.

Q: How do you like our HOB interface? Please provide us with your
thoughts and suggestions on HOB
interface and functionality.

A: I like the hob design. It actually does not support yet a few
workflows that I consider much important for my work: i.e. adding new
recipes, supporting kernel development (mainly configuration,
patching). I understand not every user does require them and hence I
don't consider myself as the actual hob's average target user. Anyway
I appreciate the project is working on more intuitive tools like HOB
and I look forward to see if similar effort will also bring us webhob
experience in the future. People doing mainly package integration
would benefit the best from HOB, since they need not to dig into the
build system's details.

Q: Was it easy to find the support you needed to build and boot an image?

A: Procedures for the official emulated target are well documented and
clear enough for the task required by this beta testing. Support for
deploying and booting on reference real-hardware target is a little
bit lacking but a lot of resources and documentation are already
available online and I agree on not duplicating reference material.

Q: Which Bugzilla reports did you submit?

A: None till now. Still investigating on some oddities and discussing
with the team on IRC. Also hit bug #3135, which is already fixed in
master now.

Q: Did you try anything else with Yocto 1.3?

A: Building an SDK and investigating procedures to deploy toolchains,
SDKs and ADTs is one of my primary goals. I built toolchains for the
arm architecture and tested the environment to build a simple C
source. Relocatable SDK is a good improvement in term of flexibility
when deploying for application developers. The beta snapshot does
bring bug #3135, but it's already fixed in master.

Q: What would you like to have in Yocto Project for future releases?

A: Documentation as a whole IMHO should and must improve a bit to make
it more useful for reference. At the design level, I see the team is
working very well, by keeping the documentation in a single place:
this grants us consistency and its really a good point. I still see
some confusion between online documentation, documentation source you
can build from master and the "latest" online documentation which is
often referenced on the mailing list. However I know that keeping all
the docs up-to-date and consistent is not an easy job.
Needs with respect to documentation do largely depend on the user's
perspective. For instance, if your goal is writing new recipes for
your own layers, you'll ask for a good variables reference and, maybe,
a reasonable checklist with best conventions for keeping metadata
consistent. This is also required if you want to contribute back with
high degree of confidence that your patches will be considered and
reviewed. If, on the other hand, your are more involved in kernel
configuration and customization, your hope is to keep your work as
much as possible integrated with the build system: this will grant you
a closer develop-deploy-test flow by using the same tools will be used
for production. Such a workflow does have documentation but I
personally believe this is a point we can improve a lot.
Yocto Project users do belong to a very heterogeneous base: I see a
great challenge in keeping docs usable by differently focused people!


HTTP-accessible poky repo?

Evade Flow <evadeflow@...>
 

I'd like to track yocto development more closely, but I'm stuck behind a
restrictive HTTP-only firewall all day at work. Is there an official
(or unofficial-but-up-to-date), HTTP-accessible mirror of
git://git.yoctoproject.org/poky.git I can clone from?

I can create a clone on github and run some cron scripts at home to sync
it, but I'd rather not bother if there's already something like this out
there...


Re: Making recipes depend on specific layers

Tomas Frydrych <tf+lists.yocto@...>
 

Hi,

On 05/10/12 14:58, Philip Balister wrote:
I run into problems (typically with BSP layers) where I want the layer
to build only against oe-core, but I also would like to have recipes
that depend on other layers. Typically, a "complex" image that uses
packages built from other layers.
Not sure if I fully understood what you are trying to do, but I'd be
worried about adding yet another dependency dimension to the system as a
whole.

Regarding the problems with coexisting bsp layers, I eventually came to
the conclusion that it's best to avoid parsing any irrelevant bsp layers
altogether. The way we handle this in Guacamayo is to keep the
bsp-related recipes in dedicated directories that can be easily BBMASKed
out:

recipes-bsp/ti-appends: for recipes related to meta-ti
recipes-bsp/rpi-appends: for recipes related to meta-raspberrypi

For each machine we support we then have a machine conf that looks like
this (e.g., for beagleboard.conf):

# source canonical beagleboard.conf from meta-ti
require ../../../layers/meta-ti/conf/machine/beagleboard.conf

BBMASK .= "|.*/meta-raspberrypi|.*/recipes-bsp/rpi-appends"

Consequently for any given machine only a single bsp layer is ever
parsed and the layers do not interfere with each other; this currently
triggers a bitbake warning about no recipes being in the masked out
layers, but other than does exactly what it is meant to.

Tomas