Date   

create a sdcard image

Andre Bella <scancool@...>
 

when I run yocto for  the first time i created a *.sdcard image, and after that I added a few more packages and click on build image but it does not create a *.sdcard image any more, and this are the only options I get on the menu(attachment)


Re: [PATCH] Fix oprofileui build with automake-1.13

Ross Burton
 

On 18 February 2013 17:31, Burton, Ross <ross.burton@intel.com> wrote:
Merged to oprofileui master, thanks.
I lie - I don't have permission to push there. I'll find someone who
either can push or can give me access to push.

Ross


Re: [PATCH] Fix oprofileui build with automake-1.13

Ross Burton
 

Hi Marko,

Merged to oprofileui master, thanks.

Ross


Re: [meta-ti] Wifi Module + udev configs

Raul Mu?oz
 

Any suggestions?

I really do not know what to do, the file "/lib/udev/firmware" never appear.

Thank you.


2013/2/14 Raul Rosetto Munoz <munoz0raul@...>

Now Im with 173 from meta-fsl bbapend, but I tryed with many others from meta-oe and poky.






2013/2/14 Denys Dmytriyenko <denys@...>
On Thu, Feb 14, 2013 at 02:23:14PM -0200, Raul Rosetto Munoz wrote:
> Denys,
> There are something strange,
>
> First there are no  linux-firmware-{rtl8192cu,rtl8192ce,rtl8192su}
> installed at rfs.

I was talking about packages, looks like you have them already installed.


> raul@phi04:.../tmp/deploy/images$ find
> /media/ed86e6a2-20c2-464e-a2f3-f28ff48983ef/lib/firmware/ -name "*8192*"
> /media/ed86e6a2-20c2-464e-a2f3-f28ff48983ef/lib/firmware/RTL8192E
> /media/ed86e6a2-20c2-464e-a2f3-f28ff48983ef/lib/firmware/rtlwifi/rtl8192sefw.bin
> /media/ed86e6a2-20c2-464e-a2f3-f28ff48983ef/lib/firmware/rtlwifi/rtl8192defw.bin
>
> Another problem is that "/lib/udev/firmware" are not installed to.
>
> raul@phi04:.../tmp/deploy/images$ find
> /media/ed86e6a2-20c2-464e-a2f3-f28ff48983ef/lib/udev/ -name "*firmware*"
> raul@phi04:.../tmp/deploy/images$

What is your udev version?


> But I can see theses files at my "tmp/sysroots/beaglebone"
>
> raul@phi04:.../tmp/sysroots/beaglebone$ find lib/firmware/ -name "*8192*"
> lib/firmware/RTL8192E
> lib/firmware/rtlwifi/rtl8192sefw.bin
> lib/firmware/rtlwifi/rtl8192defw.bin
> lib/firmware/rtlwifi/rtl8192cfw.bin
> lib/firmware/rtlwifi/rtl8192cufw.bin
>
> raul@phi04:.../tmp/sysroots/beaglebone$ find lib/udev/ -name "*firmware*"
> lib/udev/firmware
> lib/udev/rules.d/50-firmware.rules
>
> I tryed copy this files for the sdcard but doesnt work.
>
> Do you have any suggest?
>
> Thanks for all help.



--
Raul Rosetto Muñoz



--
Raul Rosetto Muñoz


Re: Updated Yocto Hands-on Kernel Lab available

Tom Zanussi <tom.zanussi@...>
 

On Sun, 2013-02-17 at 21:16 -0500, Trevor Woerner wrote:
...sorry, I meant to CC the list too


---------- Forwarded message ----------
From: Trevor Woerner <twoerner@gmail.com>
Date: Sun, Feb 17, 2013 at 9:15 PM
Subject: Re: [yocto] Updated Yocto Hands-on Kernel Lab available
To: Tom Zanussi <tom.zanussi@intel.com>


Hi Tom,

I can see how the kernel *.bb files get pulled in due to the following
line in each lab's layer configuration (${LAYERDIR}/conf/layer.conf):

BBFILES := "... ${LAYERDIR}/recipes-*/*/*.bb ..."

Since the *.bb files are located under
${LAYERDIR}/recipes-kernel/linux/<kernel>.bb this matched the above
pattern.

What I can't figure out is why, for example, in lab1 are the kernel
patch files located in

${LAYERDIR}/recipes-kernel/linux/linux

while the kernel patch files for lab2 are in

${LAYERDIR}/recipes-kernel/linux/files

Does bitbake find the patch files for lab1 in a subdirectory called
"linux" because the recipe's name is linux_3.0.18.bb? Because I don't
see anything in that particular recipe which would suggest it
(bitbake) should look there (linux). And when I go to lab2 and rename
the "files" directory to "linux-yocto" the build doesn't work, so this
behaviour would seem to discount the belief that a patch directory
name can take on the recipe name and be found.
Hi,

Yes, in lab1 bitbake finds the patch files because they're in the
'linux' subdirectory. It should also be able to find them if you
renamed that directory to 'linux-3.0.18', and it would also find them in
the 'files' directory. These subdirectories are added to FILESPATH in
base.bbclass:

FILESPATH = "${@base_set_filespath(["${FILE_DIRNAME}/${BP}", "${FILE_DIRNAME}/${BPN}", "${FILE_DIRNAME}/files"], d)}"

Those are relative to a .bb, which is what we have in lab1 - the kernel
recipe is linux_3.0.18.bb.

In lab2, we have a linux-yocto_3.4.bbappend file rather than a .bb file.

If you look at the .bbappend, you can see:

FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

which is what we need to add to the .bbappend to get bitbake to look in
the 'files' subdirectory under the .bbappend - since the FILESPATH is
relative to the base recipe in meta/, linux-yocto_3.4.bb, and not
our .bbappend, bitbake won't find the files under our .bbappend unless
we add our .bbappend's 'files' subdir to FILESPATH via FILESEXTRAPATHS.

If you wanted to change the name of the directory under the .bbappend to
'linux-yocto', you could just use:

FILESEXTRAPATHS_prepend := "${THISDIR}/linux-yocto:"

or better:

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"

Tom

Best regards,
Trevor
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Updated Yocto Hands-on Kernel Lab available

Trevor Woerner
 

...sorry, I meant to CC the list too


---------- Forwarded message ----------
From: Trevor Woerner <twoerner@gmail.com>
Date: Sun, Feb 17, 2013 at 9:15 PM
Subject: Re: [yocto] Updated Yocto Hands-on Kernel Lab available
To: Tom Zanussi <tom.zanussi@intel.com>


Hi Tom,

I can see how the kernel *.bb files get pulled in due to the following
line in each lab's layer configuration (${LAYERDIR}/conf/layer.conf):

BBFILES := "... ${LAYERDIR}/recipes-*/*/*.bb ..."

Since the *.bb files are located under
${LAYERDIR}/recipes-kernel/linux/<kernel>.bb this matched the above
pattern.

What I can't figure out is why, for example, in lab1 are the kernel
patch files located in

${LAYERDIR}/recipes-kernel/linux/linux

while the kernel patch files for lab2 are in

${LAYERDIR}/recipes-kernel/linux/files

Does bitbake find the patch files for lab1 in a subdirectory called
"linux" because the recipe's name is linux_3.0.18.bb? Because I don't
see anything in that particular recipe which would suggest it
(bitbake) should look there (linux). And when I go to lab2 and rename
the "files" directory to "linux-yocto" the build doesn't work, so this
behaviour would seem to discount the belief that a patch directory
name can take on the recipe name and be found.

Best regards,
Trevor


Re: kernel menuconfig unusable Was: Updated Yocto Hands-on Kernel Lab available

Trevor Woerner
 

On Sun, Feb 17, 2013 at 6:15 PM, Tom Zanussi <tom.zanussi@intel.com> wrote:
I guess a bug
should be opened for it.
I have created https://bugzilla.yoctoproject.org/show_bug.cgi?id=3898
in the hope it doesn't get dropped again.


Re: kernel menuconfig unusable Was: Updated Yocto Hands-on Kernel Lab available

Tom Zanussi <tom.zanussi@...>
 

On Sun, 2013-02-17 at 16:22 -0500, Trevor Woerner wrote:
On Fri, Feb 15, 2013 at 9:29 PM, Tom Zanussi <tom.zanussi@intel.com> wrote:
I'm happy to announce that an updated version of the Yocto 'Hands-on
Kernel Lab' has been released and is available here:
This is awesome, and much appreciated (especially by those of us who
can't make it out to these events).

Following the lab, however, I very quickly ran into the dreaded
"kernel menuconfig unusable" issue. Is there any way Liang Li's
suggested fix[1] could make it into mainline and the danny branch
which is used for these labs? Is there a better fix? Is there another
way around this issue, perhaps with a pure conf/local.conf setting?
Yeah, I ran into this too on Fedora 17, but not Ubuntu. I thought it
was a local thing and basically 'powered through it' and changed the
settings, knowing I was seeing double.

I don't know what the proper fix for this is - if it's the patch you
pointed to, I'm not sure why it wasn't pulled in. If not, I guess a bug
should be opened for it.

Tom

Thanks and best regards,
Trevor

[1] http://lists.linuxtogo.org/pipermail/openembedded-core/2012-August/027130.html

NOTE: simply setting OE_TERMINAL to "xterm" doesn't fix the problem,
it only changes the terminal :-)
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


kernel menuconfig unusable Was: Updated Yocto Hands-on Kernel Lab available

Trevor Woerner
 

On Fri, Feb 15, 2013 at 9:29 PM, Tom Zanussi <tom.zanussi@intel.com> wrote:
I'm happy to announce that an updated version of the Yocto 'Hands-on
Kernel Lab' has been released and is available here:
This is awesome, and much appreciated (especially by those of us who
can't make it out to these events).

Following the lab, however, I very quickly ran into the dreaded
"kernel menuconfig unusable" issue. Is there any way Liang Li's
suggested fix[1] could make it into mainline and the danny branch
which is used for these labs? Is there a better fix? Is there another
way around this issue, perhaps with a pure conf/local.conf setting?

Thanks and best regards,
Trevor

[1] http://lists.linuxtogo.org/pipermail/openembedded-core/2012-August/027130.html

NOTE: simply setting OE_TERMINAL to "xterm" doesn't fix the problem,
it only changes the terminal :-)


[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
lsb 4.1 1.4 Yi Zhao <yi.zhao@windriver.com>
ccache 3.1.8 3.1.9 Wenzong Fan <wenzong.fan@windriver.com>
systemtap-uprobes 1.8+gitAUTOINC+48fa6b5e1 2.1 Tom Zanussi <tom.zanussi@intel.com>
sysprof 1.1.8+gitAUTOINC+4692f85 1.2.0 Tom Zanussi <tom.zanussi@intel.com>
boost 1.52.0 1.53.0 Saul Wold <sgw@linux.intel.com>
foomatic-filters 4.0.17 4.0-20130216 Saul Wold <sgw@linux.intel.com>
nspr 4.9.4 4.9.5 Saul Wold <sgw@linux.intel.com>
gconf 3.2.5 3.2.6 Saul Wold <sgw@linux.intel.com>
pkgconfig 0.25 0.28 Saul Wold <sgw@linux.intel.com> removes glib-conf, adds circu...
kconfig-frontends 3.6.0 3.7.0.0 Saul Wold <sgw@linux.intel.com>
glib-networking 2.28.7 2.35.6 Saul Wold <sgw@linux.intel.com>
createrepo 0.4.11 0.9.9 Saul Wold <sgw@linux.intel.com> Versions after 0.9.* use YUM,...
vte 0.28.2 0.34.2 Saul Wold <sgw@linux.intel.com>
resolvconf 1.69 1.70 Saul Wold <sgw@linux.intel.com>
sqlite3 3.7.15.2 3071502 Saul Wold <sgw@linux.intel.com>
build-appliance-image 1.0 3.2.1 Saul Wold <sgw@linux.intel.com>
socat 1.7.2.0 1.7.2.1 Saul Wold <sgw@linux.intel.com> http://www.dest-unreach.org/socat/download/socat-1.7.2.0.tar.bz2;name=src
man-pages 3.45 3.47 Saul Wold <sgw@linux.intel.com>
libffi 3.0.11 3.0.12 Saul Wold <sgw@linux.intel.com>
mtdev 1.1.2 1.1.3 Ross Burton <ross.burton@intel.com>
logrotate 3.8.1 3.8.3 Robert Yang <liezhi.yang@windriver.com>
busybox 1.20.2 1.21.0 Radu Moisan <radu.moisan@intel.com>
iputils s20101006 20121221 Radu Moisan <radu.moisan@intel.com>
unzip 6.0 60 Radu Moisan <radu.moisan@intel.com>
rxvt-unicode 9.15 9.16 Radu Moisan <radu.moisan@intel.com>
gawk 4.0.1 4.0.2 Radu Moisan <radu.moisan@intel.com>
zip 3.0 30 Radu Moisan <radu.moisan@intel.com>
openssl 1.0.0j 1.0.1e Radu Moisan <radu.moisan@intel.com> http://www.openssl.org/source/openssl-1.0.0j.tar.gz
pango 1.32.5 1.33.7 Radu Moisan <radu.moisan@intel.com>
ed 1.6 1.7 Radu Moisan <radu.moisan@intel.com>
u-boot-fw-utils 2011.06 2013.01.01 Radu Moisan <radu.moisan@intel.com>
atk 2.6.0 2.7.5 Radu Moisan <radu.moisan@intel.com>
u-boot-mkimage 2011.06 2013.01.01 Radu Moisan <radu.moisan@intel.com>
hdparm 9.39 9.43 Radu Moisan <radu.moisan@intel.com>
cronie 1.4.8 1.4.9 Radu Moisan <radu.moisan@intel.com>
systemtap 1.8+gitAUTOINC+48fa6b5e1 2.1 Radu Moisan <radu.moisan@intel.com>
coreutils 8.14 8.21 Radu Moisan <radu.moisan@intel.com>
libunique 1.1.6 3.0.2 Radu Moisan <radu.moisan@intel.com> Do not upgrade to version: 2....
liburcu 0.7.4 0.7.6 Radu Moisan <radu.moisan@intel.com>
babeltrace 1.0+gitAUTOINC+f6ed7fa46 1.0.3 Radu Moisan <radu.moisan@intel.com>
apr-util 1.4.1 1.5.1 Radu Moisan <radu.moisan@intel.com>
watchdog 5.12 5.13 Radu Moisan <radu.moisan@intel.com>
curl 7.28.1 7.29.0 Radu Moisan <radu.moisan@intel.com>
mobile-broadband-provider-info1.0.0+gitrAUTOINC+d9995e 20090309 Radu Moisan <radu.moisan@intel.com>
gsettings-desktop-schemas 3.7.3 3.7.5 No Maintainer information
xf86-video-omap 0.4.2+gitrAUTOINC+ae0394 0.4.3 No Maintainer information
wayland 1.0.3 1.0.5 No Maintainer information
weston 1.0.3 1.0.5 No Maintainer information
ltp 20120903 20130109 Mihai Lindner <mihaix.lindner@linux.intel.com>
rpm 5.4.9 5.4.10-0.20120706 Mark Hatle <mark.hatle@windriver.com>
xserver-xorg 1.13.1 1.13.99.902 Laurentiu Palcu <laurentiu.palcu@intel.com>
xf86-video-intel 2.21.0 2.21.2 Laurentiu Palcu <laurentiu.palcu@intel.com>
xrandr 1.3.5 1.4.0 Laurentiu Palcu <laurentiu.palcu@intel.com>
fontconfig 2.10.2 2.10.91 Laurentiu Palcu <laurentiu.palcu@intel.com>
xvinfo 1.1.1 1.1.2 Laurentiu Palcu <laurentiu.palcu@intel.com>
ghostscript 9.05 9.07 Kai Kang <kai.kang@windriver.com>
bind 9.8.1 9.9.2-P1 Kai Kang <kai.kang@windriver.com>
libsdl 1.2.15 1.2.15-1 Kai Kang <kai.kang@windriver.com>
directfb 1.6.1 1.6.3 Kai Kang <kai.kang@windriver.com>
trace-cmd 1.2+gitAUTOINC+7055ffd37 2.1.0 Darren Hart <dvhart@linux.intel.com>
kernelshark 1.2+gitAUTOINC+7055ffd37 2.1.0 Darren Hart <dvhart@linux.intel.com> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git;protocol=git
gst-plugins-bad 0.10.23 1.0.5 Cristian Iorga <cristian.iorga@intel.com> not compatible with gst-fluen...
bluez4 4.101 5.2 Cristian Iorga <cristian.iorga@intel.com>
polkit 0.104 0.110 Cristian Iorga <cristian.iorga@intel.com>
gst-plugins-good 0.10.31 1.0.5 Cristian Iorga <cristian.iorga@intel.com> not compatible with gst-fluen...
connman 1.10 1.11 Cristian Iorga <cristian.iorga@intel.com>
gst-ffmpeg 0.10.13 0.11.2 Cristian Iorga <cristian.iorga@intel.com> not compatible with gst-fluen...
libtirpc 0.2.2 0.2.3 Cristian Iorga <cristian.iorga@intel.com>
gst-plugin-bluetooth 4.101 5.2 Cristian Iorga <cristian.iorga@intel.com>
gst-fluendo-mp3 0.10.19 0.10.21 Cristian Iorga <cristian.iorga@intel.com>
gst-fluendo-mpegdemux 0.10.71 0.10.72 Cristian Iorga <cristian.iorga@intel.com>
glib-2.0 2.34.3 2.35.7 Cristian Iorga <cristian.iorga@intel.com>
gst-plugins-base 0.10.36 1.0.5 Cristian Iorga <cristian.iorga@intel.com> not compatible with gst-fluen...
gst-plugins-ugly 0.10.19 1.0.5 Cristian Iorga <cristian.iorga@intel.com> not compatible with gst-fluen...
gstreamer 0.10.36 1.0.5 Cristian Iorga <cristian.iorga@intel.com> not compatible with gst-flue...
pulseaudio 2.1 3.0 Cristian Iorga <cristian.iorga@intel.com>
gnome-common 2.28.0 3.7.4 Constantin Musca <constantinx.musca@intel.com>
gtk+ 2.24.15 3.7.8 Constantin Musca <constantinx.musca@intel.com> Do not upgrade to version: 2....
gnutls 2.12.21 3.1.5 Constantin Musca <constantinx.musca@intel.com>
apt 0.7.14 0.9.7.7 Constantin Musca <constantinx.musca@intel.com>
qemu 1.3.1 1.4.0 Constantin Musca <constantinx.musca@intel.com>
libtasn1 2.14 3.2 Constantin Musca <constantinx.musca@intel.com>
librsvg 2.32.1 2.37.0 Constantin Musca <constantinx.musca@intel.com>
gtk-engines 2.20.2 2.91.1 Constantin Musca <constantinx.musca@intel.com>
libsoup-2.4 2.40.2 2.41.5 Constantin Musca <constantinx.musca@intel.com>
gdk-pixbuf 2.26.5 2.27.1 Constantin Musca <constantinx.musca@intel.com>
augeas 0.10.0 1.0.0 Constantin Musca <constantinx.musca@intel.com>
mesa-dri 9.0.2 9.1 Constantin Musca <constantinx.musca@intel.com>
gnome-desktop 2.32.1 3.7.5 Constantin Musca <constantinx.musca@intel.com>
jpeg 8d 9 Constantin Musca <constantinx.musca@intel.com>
gnome-icon-theme 2.31.0 3.7.4 Constantin Musca <constantinx.musca@intel.com>
liberation-fonts 1.04 2.00.1 Constantin Musca <constantinx.musca@intel.com> 2.00.0 - fontforge package re...
js 1.7.0+1.8.0rc1 185-1.0.0 Constantin Musca <constantinx.musca@intel.com>
gnome-keyring 2.32.1 3.7.5 Constantin Musca <constantinx.musca@intel.com>
libgnome-keyring 2.32.0 3.7.5 Constantin Musca <constantinx.musca@intel.com>
webkit-gtk 1.8.3 1.11.5 Constantin Musca <constantinx.musca@intel.com>
shared-mime-info 1.0 1.1 Constantin Musca <constantinx.musca@intel.com>
inputproto 2.2 2.2.99.1 Constantin Musca <constantinx.musca@intel.com>
libxi 1.6.1 1.6.99.1 Constantin Musca <constantinx.musca@intel.com>
cairo 1.12.12 1.12.14 Constantin Musca <constantinx.musca@intel.com>
groff 1.20.1 1.22.2 Constantin Musca <constantinx.musca@intel.com> 1.18.1.4 is latest GPLv2 Vers...
linux-libc-headers-yocto 3.4+git-AUTOINC+a1cdb607 3.4.9 Bruce Ashfield <bruce.ashfield@windriver.com>
linux-libc-headers 3.7 3.7.8 Bruce Ashfield <bruce.ashfield@windriver.com>
lttng-modules 2.1.0 2.1.1 Bogdan Marinescu <bogdan.a.marinescu@intel.com>
diffstat 1.55 1.56 Bogdan Marinescu <bogdan.a.marinescu@intel.com>
tcl 8.5.13 8.6.0 Bogdan Marinescu <bogdan.a.marinescu@intel.com>
flex 2.5.35 2.5.37 Bogdan Marinescu <bogdan.a.marinescu@intel.com>
python 2.7.3 3.3.0 Bogdan Marinescu <bogdan.a.marinescu@intel.com>
tcf-agent 0.4.0+gitAUTOINC+4ef94ec 8.0 Bogdan Marinescu <bogdan.a.marinescu@intel.com>
lttng-ust 2.1.0 2.1.1 Bogdan Marinescu <bogdan.a.marinescu@intel.com>
python-pygobject 2.27.91 3.7.5.1 Bogdan Marinescu <bogdan.a.marinescu@intel.com>
bdwgc 7.2 7.3alpha2 Bogdan Marinescu <bogdan.a.marinescu@intel.com>
gmp 5.1.0 5.1.0a Bogdan Marinescu <bogdan.a.marinescu@intel.com>
intltool 0.50.2 0.51.0 Bogdan Marinescu <bogdan.a.marinescu@intel.com>
automake 1.12.6 1.13.1 Bogdan Marinescu <bogdan.a.marinescu@intel.com>
git 1.8.1.2 1.8.1.3 Bogdan Marinescu <bogdan.a.marinescu@intel.com>
sudo 1.8.6p4 1.8.6p6 Andrei Dinu <andrei.adrianx.dinu@intel.com>
dbus-glib 0.100 0.100.1 Andrei Dinu <andrei.adrianx.dinu@intel.com>
shadow 4.1.4.3 4.1.5.1 Andrei Dinu <andrei.adrianx.dinu@intel.com>
e2fsprogs 1.42.6 1.42.7 Andrei Dinu <andrei.adrianx.dinu@intel.com>
Upgradable Count: 105
Upgrade Total Count: 120
The based commit merge time is:
Fri Feb 15 16:04:53 2013 -0800
The based commit is:
commit 05021f82589df2d6eff29f046faf6fb87cda6e95
Author: Peter Seebach <peter.seebach@windriver.com>
Date: Tue Feb 12 16:07:51 2013 -0600
Any problem, please contact Saul Wold <sgw@linux.intel.com>


[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
opkg 0.1.8+svnr649... 0.1.8 170 day Radu Moisan <radu.moisan@inte... No data
kmod 9 9 205 day Radu Moisan <radu.moisan@inte... No data
ubootchart 0.0+r12 0.0+r12 159 day Radu Moisan <radu.moisan@inte... No data
tinylogin 1.4 1.4 167 day Radu Moisan <radu.moisan@inte... TinyLogin was merged into Busy...
libpfm4 4.3.0 N/A 41320 d No Maintainer information No data
gtk+3 3.4.4 N/A 41320 d No Maintainer information No data
prelink 1.0+gitAUTOIN... 1.0+git1+9552... 170 day Mark Hatle <mark.hatle@windri... No data
adt-installer 0.1.8+svnr596... 1.1 159 day Jessica Zhang <jessica.zhang@... No data
tremor 20120314 20120122 101 day Cristian Iorga <cristian.iorg... No data
minicom 2.6.1 2.6.1 170 day Cristian Iorga <cristian.iorg... No data
libxslt 1.1.28 N/A 41320 d Constantin Musca <constantinx... No data
libpng 1.5.14 N/A 41320 d Andrei Dinu <andrei.adrianx.d... 1.4.3 and later changes the AP...
Manual Check Count: 12
Manual Need Check Count: 12
Any problem, please contact Saul Wold <sgw@linux.intel.com>


Re: [PATCH 0/2][meta-intel] Remove Cedartrail BSP

Tom Zanussi <tom.zanussi@...>
 

On Fri, 2013-02-08 at 14:34 -0800, kishore.k.bodke@intel.com wrote:
From: Kishore Bodke <kishore.k.bodke@intel.com>

Hi All,

This patch set is to remove Cedartrail BSP from
meta-intel/master.
Cedartrail BSP will be no longer supported in Yocto
from 1.4 release.

Please pull these patches into meta-intel/master.
Pulled into meta-intel/master.

Thanks
Kishore.

The following changes since commit 575f93dd4ba1fb9aca8a58dc66e9066eca0a3925:

meta-intel: remove kernel AUTOREVs (2013-02-04 10:39:06 -0600)

are available in the git repository at:

git://git.pokylinux.org/meta-intel-contrib kishore/cedartrail_remove
http://git.pokylinux.org/cgit.cgi/meta-intel-contrib/log/?h=kishore/cedartrail_remove

Kishore Bodke (2):
Cedartrail: Remove Cedartrail BSP
meta-intel: Update the MAINTAINERS list.

MAINTAINERS | 4 -
meta-cedartrail/COPYING.MIT | 17 --
meta-cedartrail/README | 199 --------------------
meta-cedartrail/README.sources | 17 --
meta-cedartrail/conf/layer.conf | 12 --
meta-cedartrail/conf/machine/cedartrail-nopvr.conf | 21 ---
meta-cedartrail/conf/machine/cedartrail.conf | 29 ---
.../formfactor/cedartrail-nopvr/machconfig | 3 -
.../formfactor/formfactor/cedartrail/machconfig | 3 -
.../recipes-bsp/formfactor/formfactor_0.0.bbappend | 3 -
.../images/core-image-cdv-media-sdk.bb | 12 --
.../images/core-image-cdv-media.bb | 13 --
.../xorg-driver/cdv-pvr-driver_1.0.3.bb | 197 -------------------
.../xserver-xf86-config/cedartrail-nopvr/xorg.conf | 26 ---
.../xserver-xf86-config/cedartrail/xorg.conf | 19 --
.../xorg-xserver/xserver-xf86-config_0.1.bbappend | 1 -
.../linux/linux-yocto-rt_3.0.bbappend | 18 --
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 23 ---
.../ogg-CC-BY-3.0-music-samples_0.1.bb | 21 ---
.../video-samples/bigbuckbunny-ogg.bb | 22 ---
20 files changed, 660 deletions(-)
delete mode 100755 meta-cedartrail/COPYING.MIT
delete mode 100755 meta-cedartrail/README
delete mode 100755 meta-cedartrail/README.sources
delete mode 100644 meta-cedartrail/binary/.gitignore
delete mode 100644 meta-cedartrail/conf/layer.conf
delete mode 100644 meta-cedartrail/conf/machine/cedartrail-nopvr.conf
delete mode 100644 meta-cedartrail/conf/machine/cedartrail.conf
delete mode 100644 meta-cedartrail/recipes-bsp/formfactor/formfactor/cedartrail-nopvr/machconfig
delete mode 100644 meta-cedartrail/recipes-bsp/formfactor/formfactor/cedartrail/machconfig
delete mode 100644 meta-cedartrail/recipes-bsp/formfactor/formfactor_0.0.bbappend
delete mode 100644 meta-cedartrail/recipes-cdv-media/images/core-image-cdv-media-sdk.bb
delete mode 100644 meta-cedartrail/recipes-cdv-media/images/core-image-cdv-media.bb
delete mode 100644 meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver_1.0.3.bb
delete mode 100644 meta-cedartrail/recipes-graphics/xorg-xserver/xserver-xf86-config/cedartrail-nopvr/xorg.conf
delete mode 100644 meta-cedartrail/recipes-graphics/xorg-xserver/xserver-xf86-config/cedartrail/xorg.conf
delete mode 100644 meta-cedartrail/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
delete mode 100644 meta-cedartrail/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
delete mode 100644 meta-cedartrail/recipes-kernel/linux/linux-yocto_3.0.bbappend
delete mode 100644 meta-cedartrail/recipes-mediasamples/music-samples/ogg-CC-BY-3.0-music-samples_0.1.bb
delete mode 100644 meta-cedartrail/recipes-mediasamples/video-samples/bigbuckbunny-ogg.bb


What's OnTrack DM6 Aux3 partition?

Andre Bella <scancool@...>
 


I'm using yocto to create a *.sdcard image, and when I transfer to the sd card it creates a partition call OnTrack DM6 Aux3, what is that? and how it can be read?

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048       10239        4096   53  OnTrack DM6 Aux3
/dev/sdb2           10240     6639615     3314688   83  Linux

I'm asking cause I will like to put a new uImage there,


Re: Updated Yocto Hands-on Kernel Lab available

David Stewart
 

On 2/15/13 6:29 PM, "Tom Zanussi" <tom.zanussi@intel.com> wrote:

Hi,

I'm happy to announce that an updated version of the Yocto 'Hands-on
Kernel Lab' has been released and is available here:

https://www.yoctoproject.org/sites/yoctoproject.org/files/elc2013-kernel-l
ab.pdf

The above document contains all the instructions you need to get started
from scratch.
Pretty frickin' awesome. Great job!


You can always get to the lab and associated content by visiting the
Yocto home page (https://www.yoctoproject.org/) and selecting 'Read
presentations about the project' from the drop-down list you get by
clicking on the 'Start Here to learn more' box on the left-hand side and
clicking on the 'Working with the Kernel' presentation link.

The 'Hands-on Kernel Lab' has been updated to Yocto 1.3 ('danny') and
has been substantially expanded from three to five labs, with completely
new sections covering custom kernels, loadable modules and getting them
into (and autoloaded into) images, external modules, local clones, bare
local clones, and enabling LTSI features.

See below for a more complete listing of what's covered along with the
lab number covering those topics.

I've run through the lab twice, once on Fedora 17 and once on Ubuntu
12.04, so it should be pretty solid at this point, but if you find
problems, please let me know...

* Creating and using a traditional kernel recipe (lab1)
* Using 'bitbake -c menuconfig' to modify the kernel configuration and
replace the defconfig with the new configuration (lab1)
* Adding a kernel module to the kernel source and configuring it as a
built-in module by adding options to the kernel defconfig (lab1)
* Creating and using a linux-yocto-based kernel (lab2)
* Adding a kernel module to the kernel source and configuring it as a
built-in module using linux-yocto 'config fragments' (lab2)
* Using the linux-yocto kernel as an LTSI kernel (configuring in an item
added by the LTSI kernel which is merged into linux-yocto) (lab2)
* Using an arbitrary git-based kernel via the linux-yocto-custom kernel
recipe (lab3)
* Adding a kernel module to the kernel source of an arbitrary git-based
kernel and configuring it as a loadable module using 'config fragments'
(lab3)
* Actually getting the module into the image and autoloading it on boot
(lab3)
* Using a local clone of an arbitrary git-based kernel via the
linux-yocto-custom kernel recipe to demonstrate a typical development
workflow (lab4)
* Modifying the locally cloned custom kernel source and verifying the
changes in the new image (lab4)
* Using a local clone of a linux-yocto- kernel recipe to demonstrate a
typical development workflow (lab4)
* Modifying the locally cloned linux-yocto kernel source and verifying
the changes in the new image (lab4)
* Using a 'bare' local clone of a linux-yocto- kernel recipe to
demonstrate a typical development workflow (lab4)
* Modifying the locally cloned 'bare' linux-yocto kernel source and
verifying the changes in the new image (lab4)
* Adding and using an external kernel module via a module recipe (lab4)
* Using the 'Yocto BSP Tools' yocto-bsp tool generate a new Yocto BSP
(lab5)
* Using the 'Yocto BSP Tools' yocto-kernel tool to add kernel patches and
config fragments (lab5)


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


Re: Slides from the Yocto Developer Day

Tom Zanussi <tom.zanussi@...>
 

On Wed, 2013-01-30 at 08:43 -0800, Darren Hart wrote:
On 01/30/2013 06:41 AM, Marco wrote:
Il 13/11/2012 08:01, Scott Garman ha scritto:
On 11/12/2012 11:52 AM, Anna Dushistova wrote:
Hi All,

Are the slides available somewhere?

Thanks!
Anna.
Hi Anna,

Attached are the slides and lab packet I used for the intro hands-on lab
in PDF format.

Hi all,
would be available slides and worksheet for the other YDD-2012 labs?

- "Hands on kernel lab" by Darren & Tom
We're working on making the kernel lab available online. Until then, the
materials would not be of much use as they were just specific enough to
the lab machines we set up, that they would frustrate more than
enlighten someone trying to use them on their own. Once they are up,
you'll be able to download them and do the labs on your own machines.
Hi,

The 'Hands-on Kernel Lab' has now been updated, and the instructions now
assume you'll be starting from scratch on your own machine - anything
related to the lab environment is now gone, and there's actually a lot
more material now (5 labs instead of 3). See here for details:

https://lists.yoctoproject.org/pipermail/yocto/2013-February/014408.html

Tom


Updated Yocto Hands-on Kernel Lab available

Tom Zanussi <tom.zanussi@...>
 

Hi,

I'm happy to announce that an updated version of the Yocto 'Hands-on
Kernel Lab' has been released and is available here:

https://www.yoctoproject.org/sites/yoctoproject.org/files/elc2013-kernel-lab.pdf

The above document contains all the instructions you need to get started
from scratch.

You can always get to the lab and associated content by visiting the
Yocto home page (https://www.yoctoproject.org/) and selecting 'Read
presentations about the project' from the drop-down list you get by
clicking on the 'Start Here to learn more' box on the left-hand side and
clicking on the 'Working with the Kernel' presentation link.

The 'Hands-on Kernel Lab' has been updated to Yocto 1.3 ('danny') and
has been substantially expanded from three to five labs, with completely
new sections covering custom kernels, loadable modules and getting them
into (and autoloaded into) images, external modules, local clones, bare
local clones, and enabling LTSI features.

See below for a more complete listing of what's covered along with the
lab number covering those topics.

I've run through the lab twice, once on Fedora 17 and once on Ubuntu
12.04, so it should be pretty solid at this point, but if you find
problems, please let me know...

* Creating and using a traditional kernel recipe (lab1)
* Using 'bitbake -c menuconfig' to modify the kernel configuration and replace the defconfig with the new configuration (lab1)
* Adding a kernel module to the kernel source and configuring it as a built-in module by adding options to the kernel defconfig (lab1)
* Creating and using a linux-yocto-based kernel (lab2)
* Adding a kernel module to the kernel source and configuring it as a built-in module using linux-yocto 'config fragments' (lab2)
* Using the linux-yocto kernel as an LTSI kernel (configuring in an item added by the LTSI kernel which is merged into linux-yocto) (lab2)
* Using an arbitrary git-based kernel via the linux-yocto-custom kernel recipe (lab3)
* Adding a kernel module to the kernel source of an arbitrary git-based kernel and configuring it as a loadable module using 'config fragments' (lab3)
* Actually getting the module into the image and autoloading it on boot (lab3)
* Using a local clone of an arbitrary git-based kernel via the linux-yocto-custom kernel recipe to demonstrate a typical development workflow (lab4)
* Modifying the locally cloned custom kernel source and verifying the changes in the new image (lab4)
* Using a local clone of a linux-yocto- kernel recipe to demonstrate a typical development workflow (lab4)
* Modifying the locally cloned linux-yocto kernel source and verifying the changes in the new image (lab4)
* Using a 'bare' local clone of a linux-yocto- kernel recipe to demonstrate a typical development workflow (lab4)
* Modifying the locally cloned 'bare' linux-yocto kernel source and verifying the changes in the new image (lab4)
* Adding and using an external kernel module via a module recipe (lab4)
* Using the 'Yocto BSP Tools' yocto-bsp tool generate a new Yocto BSP (lab5)
* Using the 'Yocto BSP Tools' yocto-kernel tool to add kernel patches and config fragments (lab5)


2 vacation days (19 and 20)

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

I will be taking two vacation days next Tues and Weds.

Scott

Scott Rifenbark
Intel Corporation
Yocto Project Documentation
503.712.2702
503.341.0418 (cell)


Re: fails after adding package

Andre Bella <scancool@...>
 

I had attched the wrong file and I see why it fails, but I dont know where can I find this files, cause eglibc is already selected.

error: Failed dependencies:
    eglibc-binary-localedata-uk-ua.koi8u is needed by locale-base-uk-ua.koi8-u-2.13-r20.armv5te
    eglibc-binary-localedata-de-at.iso88591 is needed by locale-base-de-at.iso-8859-1-2.13-r20.armv5te
    eglibc-binary-localedata-tr-cy.iso88599 is needed by locale-base-tr-cy.iso-8859-9-2.13-r20.armv5te
    eglibc-binary-localedata-ru-ua.koi8u is needed by locale-base-ru-ua.koi8-u-2.13-r20.armv5te
    eglibc-binary-localedata-gl-es.iso88591 is needed by locale-base-gl-es.iso-8859-1-2.13-r20.armv5te
    eglibc-binary-localedata-ms-my.iso88591 is needed by locale-base-ms-my.iso-8859-1-2.13-r20.armv5te
    eglibc-binary-localedata-vi-vn.tcvn57121 is needed by locale-base-vi-vn.tcvn5712-1-2.13-r20.armv5te
    eglibc-binary-localedata-da-dk.iso88591 is needed by locale-base-da-dk.iso-8859-1-2.13-r20.armv5te
    eglibc-binary-localedata-nn-no.iso88591 is needed by locale-base-nn-no.iso-8859-1-2.13-r20.armv5te
    eglibc-binary-localedata-hu-hu.iso88592 is needed by locale-base-hu-hu.iso-8859-2-2.13-r20.armv5te
    eglibc-binary-localedata-pl-pl.iso88592 is needed by locale-base-pl-pl.iso-8859-2-2.13-r20.armv5te
    eglibc-binary-localedata-sv-fi.iso88591 is needed by locale-base-sv-fi.iso-88ERROR: Function failed: do_rootfs (see /home/icemetal/fsl-community-bsp/build/tmp/work/imx233_olinuxino_micro-poky-linux-gnueabi/hob-image-1.0-r0/temp/log.do_rootfs.10499 for further information)
59-1-2.13-r20.armv5te



--- On Thu, 2/14/13, Andre Bella <scancool@...> wrote:

From: Andre Bella <scancool@...>
Subject: [yocto] fails after adding package
To: yocto@...
Date: Thursday, February 14, 2013, 6:55 PM

Hello again I'm still learning yocto, so I had build an image using hob, and after the core-image-minimal was build I added a package (nano) and build again, but this time came with an error, (attachment)
what does this error means? how do you usually add packages?
I had tried many times, always the same error.

-----Inline Attachment Follows-----

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


fails after adding package

Andre Bella <scancool@...>
 

Hello again I'm still learning yocto, so I had build an image using hob, and after the core-image-minimal was build I added a package (nano) and build again, but this time came with an error, (attachment)
what does this error means? how do you usually add packages?
I had tried many times, always the same error.


Minutes: Yocto Project Technical Team Meeting - Tuesday, February 12, 2013 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).

Liu, Song <song.liu@...>
 

Sorry for the late.

Attendees:
Belen, ScottR, LaurentiuP, KevinS, Richard, TomZ, Amit, CristanI, BruceA, Nitin, JessicaZ, MichaelH, Ross, Denys, Saul, ChrisL, Corneliu, Fahad, Björn, DaveST, AlexG, Song
 
Agenda:
 
* Opens collection - 5 min (Song)
* Yocto Project 1.3.1 status - 10 min (Ross)
- Ross: Tried a build last night, hopefully we can get a proper build on everything. tonight.
* Yocto 1.4 status - 10 min (Song/team)
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.4_Status
- Feature development: no issues. More features are getting validated in the past week. Thanks to QA team.
- Bug fixing: Not much change on total # of bugs. Fixed 35, LaurentiuP (7), BogdanM (5), thank you! WDD is about the same as the week before. WDD+ is coming down because we have less number of high's.
- Schedule reminder: M4 feature cutoff is coming this Sunday. RC1 could be at risk due to the travel of some key team members. If that happens we will target RC2 timeframe for M4 and use next week for 1.3.1 testing. Otherwise, follow the existing schedule.
- Master status (Richard): did a build last night, a few small failures. Features pulled in. Last week, trying hard to get green build. We dealt with long standing ones. Frustrated on freescale arm build issues.
 
* SWAT team rotation: Nitin Kamble -> Elizabeth Flanagan
* Opens - 10 min
* Team Sharing - 20 min
- Corneliu: we have the final version of our QA report on testing. https://wiki.ctest.yoctodev.org/wiki/Sample_Summary_Report, https://wiki.ctest.yoctodev.org/wiki/Sample_Extended_Report. Would like feedback. RP/Song: Still need email for the summary of the report.
- Ross: systemd has more patches in, it should just work now in master. Core-image-sato.
- RP: recent changes: spend a lot of time on do_package. Email discussion on mailing list. There is some changes going in. Be aware of that. Python issue, work around at bitbake level now. PR server changes. Beware of those issues. Please let us know if you see problems. Interested to see the overall build time figure.
- Michael: got M3 out, helped with that, upgraded autobuilder 5 and 6. Once they fully tested will get 4 upgraded. Still tracking some bugs on 5 now. Applied changes for new security policies.
- LaurentiuP: continued work on postinstall. Put the patches on the mailing list. With this patch, I'm pretty much done. Will work on SDK bugs.