Re: [yocto] Broken SDK
Hi Lianhao,
These patches worked for me.But still I am failing to create symbolic link
of mkspecs. It throws below mentioned error-
ln -s
/opt/poky/1.0/sysroots/arm-poky-linux-gnueabi/usr/share/qtopia/mkspecs
mkspecs
| ln: creating symbolic link `mkspecs': File exists
On commenting out
(cd ${SDK_OUTPUT}/${QT_TOOLS_PREFIX}/..; ln -s
${SDKTARGETSYSROOT}/usr/share/qtopia/mkspecs mkspecs;)
section of meta-toolchain-qte.bb, I can successfully create the SDK
including my cross toolchain of specified architecture. Do I need to change
any path?
On Mon, May 28, 2012 at 11:29 AM, Lu, Lianhao lianhao...@intel.com wrote:
Navani Srivastava wrote on 2012-05-28:
Hi,
I am working with poky-bernerd-5.0. I have built cross-toolchain for qt
with bitbake -v meta-toolchain-qte for arm1136 architecture.
I got the tool chain poky-eglibc-i686-arm-toolchain-1.0.tar.bz2 under
build/tmp/deploy/sdk/ directory. On untaring this Toolchain I found
that cross gcc wasn't included in the SDK. Can anyone please help me in
recognizing the problem?
I think the meta-toolchain-qte was not workable in benard. You might need
to cherry-pick other patches for the recipe meta-toolchian-qte.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/log/meta/recipes-qt/meta/meta-toolchain-qte.bb
Best Regards,
Lianhao
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Help in building an ad-hoc qte image
Hi Paul,
thanks for your reply.
If I understand correctly in that you have more than one machine and you
need
gstreamer on ANOTHERBOARD and all other machines don't need it,
let me rephrase for the sake of clearness.
This part of recipe:
RDEPENDS_${PN}-base_ANOTHERBOARD = \
libqt-embeddedphonon4 \
qt4-embedded-plugin-phonon-backend-gstreamer \
has the ultimate goal of adding phonon + gstreamer backend
for ANOTHERBOARD only to the rootfs.
It appears ok. We normally do not get indeed phonon + gstreamer backend.
The issue is that we get contents of
meta\recipes-multimedia\gstreamer\gstreamer_0.10.36.bb
(see original post for listing) in the rootfs and do not get what pull
them in.
We see that gstreamer is set as DEPENDS for qte (rif. qt4.inc) thus
correctly built together
with qt4-embedded.
But our task-qt4e-xyz recipe defines qt4-embedded as DEPENDS instead of
RDEPENDS.
Shouldn't be this enough to ask bitbake for building qte but not install
other than what specified in RDEPENDS to the rootfs?
Thanks in advance for your help. Regards.
Marco Monguzzi
RD Department
Exor International S.p.A.
Via Monte Fiorino,9
I-37057 San Giovanni Lupatoto (VR)
Phone:+390458774809 - Fax:+390458779023
Mobile:+393400884433
marco.mongu...@exorint.it - www.exorint.net - www.exorint.it
ATTENZIONE: Privacy Policy – D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica sono di
carattere privato e confidenziale ed esclusivamente rivolte al destinatario
sopra indicato. Nel caso aveste ricevuto questo messaggio di posta elettronica
per errore, vi comunichiamo che ai sensi del suddetto decreto è vietato l’uso,
la diffusione, distribuzione o riproduzione da parte di ogni altra persona.
Siete pregati di segnalarlo immediatamente rispondendo al mittente e di
distruggere quanto ricevuto (compresi i file allegati) senza farne copia o
leggerne il contenuto.
This e-mail transmission contains information that is confidential and may be
privileged. It is intended only for the addressee(s) named above. If you
receive this e-mail in error, please do not read, copy or disseminate it in any
manner. If you are not the intended recipient, any disclosure, copying,
distribution or use of the contents of this information is prohibited. Please
reply to the message immediately by informing the sender that the message was
misdirected. After replying, please erase it from your computer system. Your
assistance in correcting this error is appreciated.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Help in building an ad-hoc qte image
On Tuesday 29 May 2012 12:25:27 marco.mongu...@exorint.it wrote:
let me rephrase for the sake of clearness.
This part of recipe:
RDEPENDS_${PN}-base_ANOTHERBOARD = \
libqt-embeddedphonon4 \
qt4-embedded-plugin-phonon-backend-gstreamer \
has the ultimate goal of adding phonon + gstreamer backend
for ANOTHERBOARD only to the rootfs.
It appears ok. We normally do not get indeed phonon + gstreamer backend.
The issue is that we get contents of
meta\recipes-multimedia\gstreamer\gstreamer_0.10.36.bb
(see original post for listing) in the rootfs and do not get what pull
them in.
Ah, right, now I understand the question. So you've asked for task-qt4e-xyz-
base to be installed, and task-qt4e-xyz-base for ANOTHERBOARD RDEPENDS upon
qt4-embedded-plugin-phonon-backend-gstreamer. The missing link is that in
do_package we have some code to analyse shared libraries (.so) that are going
into a package in order to detect which other shared libraries they need, and
if any are found we look to see which package provides them and automatically
add that package to RDEPENDS. Thus we look at the .so files in qt4-embedded-
plugin-phonon-backend-gstreamer and determine from them that gstreamer is
required, thus gstreamer (along with libgstaudio and libgstvideo) is added to
RDEPENDS. See classes/package.bbclass if you want to see the code for this
(look for shlibdeps).
Note that sometimes this highlights problems with package granularity - I
don't know enough about gstreamer to know if any of the files currently in the
gstreamer package could actually be separated out if they aren't desired in
some installations. Occasionally as a result we do split packages further to
avoid unnecessary files being installed for all situations.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Help in building an ad-hoc qte image
On Tue, May 29, 2012 at 12:56 PM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
On Tuesday 29 May 2012 12:25:27 marco.mongu...@exorint.it wrote:
let me rephrase for the sake of clearness.
This part of recipe:
RDEPENDS_${PN}-base_ANOTHERBOARD = \
libqt-embeddedphonon4 \
qt4-embedded-plugin-phonon-backend-gstreamer \
has the ultimate goal of adding phonon + gstreamer backend
for ANOTHERBOARD only to the rootfs.
It appears ok. We normally do not get indeed phonon + gstreamer backend.
and btw this doesn't look right to me.
maybe you meant
RDEPENDS_${PN}-base_append_ANOTHERBOARD = \
Finally, it looks like you could easily workaround your problem by
defining a specific recipe for ANOTHERBOARD.
Regards
Andrea
P.S.: try bitbake -g XYZ or bitbake -g -u depexp XYZ to quickly
inspect dependencies
The issue is that we get contents of
meta\recipes-multimedia\gstreamer\gstreamer_0.10.36.bb
(see original post for listing) in the rootfs and do not get what pull
them in.
Ah, right, now I understand the question. So you've asked for task-qt4e-xyz-
base to be installed, and task-qt4e-xyz-base for ANOTHERBOARD RDEPENDS upon
qt4-embedded-plugin-phonon-backend-gstreamer. The missing link is that in
do_package we have some code to analyse shared libraries (.so) that are going
into a package in order to detect which other shared libraries they need, and
if any are found we look to see which package provides them and automatically
add that package to RDEPENDS. Thus we look at the .so files in qt4-embedded-
plugin-phonon-backend-gstreamer and determine from them that gstreamer is
required, thus gstreamer (along with libgstaudio and libgstvideo) is added to
RDEPENDS. See classes/package.bbclass if you want to see the code for this
(look for shlibdeps).
Note that sometimes this highlights problems with package granularity - I
don't know enough about gstreamer to know if any of the files currently in the
gstreamer package could actually be separated out if they aren't desired in
some installations. Occasionally as a result we do split packages further to
avoid unnecessary files being installed for all situations.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to use Software support layers such as meta-browser in a yocto image?
Hello, all! Who can tell me how could I use the /Software support layers /that provided by http://www.openembedded.org/wiki/LayerIndex into my own yocto image? For example, how could I use meta-browser during image building? Thanks! ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to use Software support layers such as meta-browser in a yocto image?
On 05/29/2012 04:07 PM, jack wrote: Hello, all! Who can tell me how could I use the /Software support layers /that provided by http://www.openembedded.org/wiki/LayerIndex into my own yocto image? For example, how could I use meta-browser during image building? Thanks! ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto Hello, Clone it into your ./poky/ directory, alongside the other meta directories in ./poky/, and reference it in ./build/conf/bblayers.conf file, BBLAYERS variable (after you sourced oe-init-build-env). Happy baking! -- Mihai Lindner ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to use Software support layers such as meta-browser in a yocto image?
On Tuesday 29 May 2012 21:07:30 jack wrote: Who can tell me how could I use the /Software support layers /that provided by http://www.openembedded.org/wiki/LayerIndex into my own yocto image? For example, how could I use meta-browser during image building? There are two steps needed here, both are covered in the documentation. First you need to add the layer to your bblayers.conf: http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#enabling-your-layer Then you need to add the desired package to your image: http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to use Software support layers such as meta-browser in a yocto image?
On 2012-05-29 07:25, Mihai Lindner wrote: On 05/29/2012 04:07 PM, jack wrote: Hello, all! Who can tell me how could I use the /Software support layers /that provided by http://www.openembedded.org/wiki/LayerIndex into my own yocto image? For example, how could I use meta-browser during image building? Thanks! Hello, Clone it into your ./poky/ directory, alongside the other meta directories in ./poky/, and reference it in ./build/conf/bblayers.conf file, BBLAYERS variable (after you sourced oe-init-build-env). Happy baking! Note: layers can be anywhere, so there's no need to put it into your poky tree. Just specify the full path in your bblayers.conf -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [opkg-utils][PATCH 0/2] opkg-utils fix for python-2.6 and fix for missing getopts
The following changes since commit 44df9dd3dc411ca1255cb4b23bde7eb71aed4778: opkg-make-index: disable filelist by default (2012-04-26 11:39:42 +0100) are available in the git repository at: git://github.com/shr-project/opkg-utils jansa/pull https://github.com/shr-project/opkg-utils/tree/jansa/pull Chris Diamand (1): Changed call to subprocess.check_output which isn't compatible with Python 2.6 Ondics Githubler (1): Option C ist shown in usage() and implemented, but was missing in getopts. Added C. opkg-build |2 +- opkg-make-index |2 +- 2 files changed, 2 insertions(+), 2 deletions(-) -- 1.7.8.6 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [opkg-utils][PATCH 1/2] Option C ist shown in usage() and implemented, but was missing in getopts. Added C.
From: Ondics Githubler github...@ondics.de Signed-off-by: Martin Jansa martin.ja...@gmail.com --- opkg-build |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/opkg-build b/opkg-build index 012afd3..485897a 100755 --- a/opkg-build +++ b/opkg-build @@ -160,7 +160,7 @@ outer=ar noclean=0 opkext=0 usage=Usage: $0 [-c] [-C] [-O] [-o owner] [-g group] pkg_directory [destination_directory] -while getopts cg:ho:vO opt; do +while getopts cCg:ho:vO opt; do case $opt in o ) owner=$OPTARG ogargs=--owner=$owner -- 1.7.8.6 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Building linux-yocto kernel for BeagleBone
Thank you Sanyaade. That's what I tried and I probably should have added some more detail to my first e-mail. Here it is: I create at beaglebone.conf machine configuration with this content: #@TYPE: Machine #@NAME: BeagleBone machine #@DESCRIPTION: Machine configuration for the http://beagleboard.org/boneboard PREFERRED_PROVIDER_virtual/xserver = xserver-xorg XSERVER = xserver-xorg \ xf86-input-evdev \ xf86-video-fbdev # Only has DVI connector for external screen GUI_MACHINE_CLASS = bigscreen # Ship all kernel modules by default MACHINE_EXTRA_RRECOMMENDS = kernel-modules # Allow for MMC booting (required by the NAND-less Beagleboard XM) EXTRA_IMAGEDEPENDS += u-boot x-load # Uncomment the following line to enable the hard floating point abi. Note that # this breaks some binary libraries and 3D (neither of which ship with # meta-yocto). For maximum compatibility, leave this disabled. #DEFAULTTUNE ?= cortexa8hf-neon SOC_FAMILY = ti33x require conf/machine/include/soc-family.inc require conf/machine/include/tune-cortexa8.inc IMAGE_FSTYPES += tar.bz2 jffs2 EXTRA_IMAGECMD_jffs2 = -lnp # 2.6.37 and later kernels use OMAP_SERIAL, ttyO0 SERIAL_CONSOLE = 115200 ttyO0 PREFERRED_PROVIDER_virtual/kernel ?= linux-yocto PREFERRED_VERSION_linux-yocto ?= 3.0% KERNEL_IMAGETYPE = uImage UBOOT_MACHINE = am335x_evm_config UBOOT_ENTRYPOINT = 0x80008000 UBOOT_LOADADDRESS = 0x80008000 MACHINE_FEATURES = apm usbgadget usbhost vfat alsa I created a linux-yocto_3.0.bbappend with this content: KMACHINE_beaglebone = yocto/standard/beagleboard SRCREV_machine_beaglebone ?= 8fd5a8eb4067c7032389e82d54f0e54e1e27f78c COMPATIBLE_MACHINE_beaglebone = beaglebone Then I am trying to boot the BeagleBone with the kernel: reading uImage 3016584 bytes read ## Booting kernel from Legacy Image at 8200 ... Image Name: Linux-3.0.24-yocto-standard Image Type: ARM Linux Kernel Image (uncompressed) Data Size:3016520 Bytes = 2.9 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... And this is where the boot process hangs. One suggestion here is that machine id of uBoot and the kernel to not match. I am using MLO and u-boot.img from the SD that shipped with the BBone. And I set UBOOT_MACHINE = am335x_evm_config in beaglebone.conf which is what uBoot should be using. I also tried a plain BeagleBoard kernel and MLO and u-boot.img created by Yocto and it did not work. Any suggestions would be appreciated. Rudi On Sun, May 27, 2012 at 12:34 PM, Sanyaade Adekoya sanya...@gmail.comwrote: Hi, According to Ti, BeagleBone is just a small BeagleBoard in a small factor so a common base like a bare build for BeagleBoard should run on BeagleBone. I think the is same for OMAP family. God blesses!!! Best regards, Sanyaade On 25 May 2012 23:52, Rudolf Streif rudolf.str...@linux.com wrote: Has anyone tried to build a linux-yocto kernel for the BeagleBone? I understand that there is the meta-ti layer to build an image for the BBone but the recipes are not utilizing the Yocto Project kernels. I know that the OMAP3 CPU of the BBoard is different form the AM355x CPU on the BBone. However, can the yocto/standard/beagleboard branch be leveraged to start off? Thanks, Rudi ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Help in building an ad-hoc qte image
Hi Paul and Andrea
thanks for your reply. I did some testing (including splitting task recipe
per each target and including PACKAGE_ARCH = ${MACHINE_ARCH})
but with no success.
Even removing this from task recipes:
RDEPENDS_${PN}-base_append_ANOTHERBOARD = \
libqt-embeddedphonon4 \
qt4-embedded-plugin-phonon-backend-gstreamer \
pulls in gstreamer. I guess some other qt lib (other than phonon
gstreamer plugin) do introduce some shlibdeps to gstreamer
as Paul indicated.
thanks for your help. Regards.
Marco Monguzzi
RD Department
Exor International S.p.A.
Via Monte Fiorino,9
I-37057 San Giovanni Lupatoto (VR)
Phone:+390458774809 - Fax:+390458779023
Mobile:+393400884433
marco.mongu...@exorint.it - www.exorint.net - www.exorint.it
ATTENZIONE: Privacy Policy – D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica sono di
carattere privato e confidenziale ed esclusivamente rivolte al destinatario
sopra indicato. Nel caso aveste ricevuto questo messaggio di posta elettronica
per errore, vi comunichiamo che ai sensi del suddetto decreto è vietato l’uso,
la diffusione, distribuzione o riproduzione da parte di ogni altra persona.
Siete pregati di segnalarlo immediatamente rispondendo al mittente e di
distruggere quanto ricevuto (compresi i file allegati) senza farne copia o
leggerne il contenuto.
This e-mail transmission contains information that is confidential and may be
privileged. It is intended only for the addressee(s) named above. If you
receive this e-mail in error, please do not read, copy or disseminate it in any
manner. If you are not the intended recipient, any disclosure, copying,
distribution or use of the contents of this information is prohibited. Please
reply to the message immediately by informing the sender that the message was
misdirected. After replying, please erase it from your computer system. Your
assistance in correcting this error is appreciated.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Building linux-yocto kernel for BeagleBone
On 05/29/2012 12:11 PM, Rudolf Streif wrote: KMACHINE_beaglebone = yocto/standard/beagleboard Sorry, they are not _that_ close. Any suggestions would be appreciated. meta-ti has support for DM37x and for AM335x. You can observe the differences there. On Sun, May 27, 2012 at 12:34 PM, Sanyaade Adekoya sanya...@gmail.com mailto:sanya...@gmail.com wrote: Hi, According to Ti, BeagleBone is just a small BeagleBoard in a small factor so a common base like a bare build for BeagleBoard should run on BeagleBone. I think the is same for OMAP family. Yes, an AM335x uses the base OMAP family mach-omap2 but a binary kernel for the AM/DM35/37 won't work on it. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Broken SDK
On Tue, May 29, 2012 at 2:03 AM, Navani Srivastava
navani.srivast...@gmail.com wrote:
ln -s
/opt/poky/1.0/sysroots/arm-poky-linux-gnueabi/usr/share/qtopia/mkspecs
mkspecs
| ln: creating symbolic link `mkspecs': File exists
as it says it seems file is there already. So make sure the preexisting file
is correct if so then you can check first if file exists before creating symlink
if the file is incorrect then just use ln -sf to create the symlink
On commenting out
(cd ${SDK_OUTPUT}/${QT_TOOLS_PREFIX}/..; ln -s
${SDKTARGETSYSROOT}/usr/share/qtopia/mkspecs mkspecs;)
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [ANNOUNCEMENT] Cedar Trail with PowerVR for Edison 6.0.1
On (23/05/12 20:47), Saxena, Rahul wrote: Please see section 1.4 of the bsp-guide (http://www.yoctoproject.org/docs/latest/bsp-guide/bsp-guide.html) including the following text: Note Pre-compiled images are bundled with a time-limited kernel that runs for a predetermined amount of time (10 days) before it forces the system to reboot. This limitation is meant to discourage direct redistribution of the image. You must eventually rebuild the image if you want to remove this restriction. seems like fruits and veggies which get stale after 10 days ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 0/2][KERNEL] new chiefriver BSP metadata
On 12-05-25 5:48 PM, tom.zanu...@intel.com wrote: From: Tom Zanussitom.zanu...@intel.com This patchset implements the initial kernel side of the chiefriver BSP. It also adds a 'temporary' feature needed for turning on rc6 support from recipe-space. The code contained in the rc6 feature is already upstream and this feature will be dropped in the next yocto kernel, but is needed for now in 3.2 - this is the most flexible way to add it while giving ourselves an easy way to drop it if it causes problems. Please pull into linux-yocto 3.2, and also create a new standard/default/common-pc-64/chiefriver branch for it. branch created, and meta changes are merged. I've pushed these to the 3.2 kernel tree now. I've also staged them in the upcoming 3.4 kernel. I'll update SRCREVs in master myself later, but you can use them immediately. Bruce Thanks, Tom The following changes since commit 49f931bc294d5b6be60502bbd448cff5aa766235: Tom Zanussi (1): meta/fishriver: remove redundant features and options are available in the git repository at: git://git.yoctoproject.org/linux-yocto-2.6.37-contrib.git tzanussi/chiefriver.v2 http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/chiefriver.v2 Tom Zanussi (2): chiefriver: create initial BSP infrastructure meta: add tmp/rc6 feature .../bsp/chiefriver/chiefriver-preempt-rt.scc | 12 +++ .../bsp/chiefriver/chiefriver-standard.scc | 11 +++ .../cfg/kernel-cache/bsp/chiefriver/chiefriver.cfg | 35 + .../cfg/kernel-cache/bsp/chiefriver/chiefriver.scc |7 ++ .../features/tmp/rc6/rc6-kernel-params.patch | 81 meta/cfg/kernel-cache/features/tmp/rc6/rc6.scc |5 + .../tmp/rc6/snb-disable-rc6p-fix-precedence.patch | 26 ++ .../features/tmp/rc6/snb-disable-rc6p.patch| 39 ++ .../features/tmp/rc6/snb-enable-rc6.patch | 54 + 9 files changed, 270 insertions(+), 0 deletions(-) create mode 100644 meta/cfg/kernel-cache/bsp/chiefriver/chiefriver-preempt-rt.scc create mode 100644 meta/cfg/kernel-cache/bsp/chiefriver/chiefriver-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/chiefriver/chiefriver.cfg create mode 100644 meta/cfg/kernel-cache/bsp/chiefriver/chiefriver.scc create mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/rc6-kernel-params.patch create mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/rc6.scc create mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/snb-disable-rc6p-fix-precedence.patch create mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/snb-disable-rc6p.patch create mode 100644 meta/cfg/kernel-cache/features/tmp/rc6/snb-enable-rc6.patch ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 0/6][linux-yocto-3.2] fri2: update BSP configuration
On 12-05-25 6:20 PM, Darren Hart wrote: The following changes since commit 49f931bc294d5b6be60502bbd448cff5aa766235: meta/fishriver: remove redundant features and options (2012-05-14 17:10:36 -0500) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-2.6.37-contrib dvhart/meta/fri2 http://git.yoctoproject.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=dvhart/meta/fri2 Darren Hart (6): fri2: Configuration update (usb, wifi, i2c) iwlwifi: Add a feature for iwlwifi iwlagn: Correct a comment typo fri2 update: drop NETDEVICE, e1xxx, usb-mass-storage, add iwlwifi feature fri2: add usb-mass-storage to standard and preempt-rt fri2: update base config I've pushed these to the 3.2 kernel tree now. They are on top of the 3.2.18 stable update. I've also staged them in the upcoming 3.4 kernel. I'll update SRCREVs in master myself later, but you can use them immediately. Bruce meta/cfg/kernel-cache/bsp/fri2/fri2-preempt-rt.scc |1 + meta/cfg/kernel-cache/bsp/fri2/fri2-standard.scc |1 + meta/cfg/kernel-cache/bsp/fri2/fri2.cfg| 21 +-- meta/cfg/kernel-cache/bsp/fri2/fri2.scc|7 ++--- meta/cfg/kernel-cache/features/iwlagn/iwlagn.scc |2 +- meta/cfg/kernel-cache/features/iwlwifi/iwlwifi.cfg |6 + meta/cfg/kernel-cache/features/iwlwifi/iwlwifi.scc |6 + 7 files changed, 28 insertions(+), 16 deletions(-) create mode 100644 meta/cfg/kernel-cache/features/iwlwifi/iwlwifi.cfg create mode 100644 meta/cfg/kernel-cache/features/iwlwifi/iwlwifi.scc ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 0/1] [KERNEL] Cedartrail Add Kernel features
On 12-05-25 1:44 PM, kishore.k.bo...@intel.com wrote: From: Kishore Bodkekishore.k.bo...@intel.com Add Power Management and move kernel features to Cedartrail Machine branch. Please pull into linux-yocto-3.0/meta. Merged and pushed to the linux-yocto-3.0 tree (on top of 3.0.32). Bruce Thanks Kishore. The following changes since commit 34e0d2b4b4e9778b31f9ea99ca43f0dc71a7ee23: meta: Clean up BSPs kernel config (2012-04-17 16:01:19 -0400) are available in the git repository at: git://git.pokylinux.org/linux-yocto-2.6.37-contrib kishore/cedartrail http://git.pokylinux.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=kishore/cedartrail Kishore Bodke (1): meta: Add cedartrail kernel features .../bsp/cedartrail/cedartrail-pvr-merge.scc|4 1 file changed, 4 insertions(+) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, May 29, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US Canada).
Attendees: Beth, Richard, Dave, Paul, Joshua, Michael, Jefro, Darren, Tom, Denys, Bruce, Jeff, Mark, ScottR, Sahad, Sean, Ross, Song New member - Ross Burton: Joined Yocto Project yesterday, joined Intel 4 years ago. Worked on moblin, meego, tizen, worked on Poky when I was with Openhand. Agenda * Opens collection - 5 min (Song) * 1.2.1 update - 10 min (ScottG) - 30 fixed, 18 remaining - pull request for the first batch sent, RP is planning merging them today or tomorrow. * 1.1.2 update - 10 min (Josh/Beth) - Not a lot of changes last week, pull request sent, should be merged in a couple of days according to Richard. - Build ETA, the end of this week. * Yocto 1.3 status - 10 min (Song/team) - 1.3 feature list: https://wiki.yoctoproject.org/wiki/Yocto_1.3_Features - 1.3 schedule: https://wiki.yoctoproject.org/wiki/Yocto_1.3_Schedule - 1.3 status: https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.3_Status - Made some progress last week. Probably some items on the scheduled have not been updated due to the holiday yesterday. There are a couple of issues with items still in scheduled stage, will check with the team. - The bug count is a high, US UK team (some of you probably busy last week on 1.2.1 bugs) should pay more attention to bugs. Romania team and the PRC team is in the mode of transitioning this week. - Items still in 'scheduled' stage: 2396 (Bruce): p1, Bruce will look into this. Beth completed 3 items for m1, still 4 left on the M1 schedule. 2 of them are P1s. Beth will look into them. Some of them may slip into M2. - Master status (Beth): 2 failures in poky-tiny. Additional targets added for nightly (5 and 1/2 hour with sstate for nightly to 11 hours without), meta-intel build (ETA, today), update of AB infrastructure in the last weekend. Weekly build this week for QA is on track. - Go over the high bugs: 8 high bugs, 2 scheduled for M1, 1 still needs a target milestone. Mark will look into 2420. * SWAT team rotation: Beth - Paul * Opens - 5 min - RP: status of pull requests for oe-core. Last week concerned about master. There has been some changes in master, fixes, package update, doing testing over the weekend to make sure master is stable. Mark's patch and Nitin's are still outstanding, will be merged soon. Expect to see some other patches going into master in the next few days. - Michael: requests to enable http for git repos. Requests from the community, have trouble using git protocol to pull source code, asked to enable http. RP: sounds fine. Http access will be read-only. There are some technical issues with using https for pull requests (RP/Michael). - Jefro: conferences: check if anyone submitted any talks for any conf, if you have, please let jeff know: Mark has one for LinuxCon. Sean considering submit same topic for elce from elc. Dave: it's good to talk about your work, Dave will have an overview talk for the LinuxCon. - Josh: QA forum for the yocto project: Jefro: still on the plan, looking for a piece software compatible with Drupal. We have quote to build it. Still at the late design phase. * Team sharing - 20 min - Sean: nothing this week. - Sahad: nothing this week. - ScottR: last week some testing on 1.2.1, completed that. Will work on bug fixing for 1.3 m4. - Mark: working on prelink issues, something we have for x32 seems to have some problem, working on it. Integrating patches from mentor also. - Jeff: nothing this week - Bruce: Was out last week. Still catching up. Will work on 1.3 items. - Denys: was out last week. - Tom: working on getting 1.2 meta-intel BSPs released. Waiting for some kernel things to appear from Bruce (Bruce already know this). Then will move on to 1.3. - Darren: more time on fish-II. Accelerometer driver will turn into a much larger effort, working with maintainers. Worked on zigbee with Scott Garman also. This week finishing up meta-intel work. Move on to 1.3 work. - Michael: last week update bugzilla requests. There was an email sent out to the mailing list on the preview. Will make it alive if there is no objection. Gerneal AB work, some work on package.yoctoproject.org. - Paul: out 3 days last week. Submit and merged 2044.that threw out some other issues. Working on fixing them. Will be out whole week next week. - Richard: merging patches last week, submit some fixes, working through some bugs, reviewed patches. This week more of the same. Out next week for UK holiday. - Beth: AB upgrade, bugzilla upgrade, AB development cluster to test the things (will announce it in the mailing list). Working with an intern. Met him last weekend, trying to get him situated in Portland. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Project Technical Team Meeting - Tuesday, May 29, 2012 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US Canada).
Attendees: Beth, Richard, Dave, Paul, Joshua, Michael, Jefro, Darren, Tom, Denys, Bruce, Jeff, Mark, ScottR, Sahad, Sean, Ross, Song New member - Ross Burton: Joined Yocto Project yesterday, joined Intel 4 years ago. Worked on moblin, meego, tizen, worked on Poky when I was with Openhand. Agenda * Opens collection - 5 min (Song) * 1.2.1 update - 10 min (ScottG) - 30 fixed, 18 remaining - pull request for the first batch sent, RP is planning merging them today or tomorrow. * 1.1.2 update - 10 min (Josh/Beth) - Not a lot of changes last week, pull request sent, should be merged in a couple of days according to Richard. - Build ETA, the end of this week. * Yocto 1.3 status - 10 min (Song/team) - 1.3 feature list: https://wiki.yoctoproject.org/wiki/Yocto_1.3_Features - 1.3 schedule: https://wiki.yoctoproject.org/wiki/Yocto_1.3_Schedule - 1.3 status: https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.3_Status - Made some progress last week. Probably some items on the scheduled have not been updated due to the holiday yesterday. There are a couple of issues with items still in scheduled stage, will check with the team. - The bug count is a high, US UK team (some of you probably busy last week on 1.2.1 bugs) should pay more attention to bugs. Romania team and the PRC team is in the mode of transitioning this week. - Items still in 'scheduled' stage: 2396 (Bruce): p1, Bruce will look into this. Beth completed 3 items for m1, still 4 left on the M1 schedule. 2 of them are P1s. Beth will look into them. Some of them may slip into M2. - Master status (Beth): 2 failures in poky-tiny. Additional targets added for nightly (5 and 1/2 hour with sstate for nightly to 11 hours without), meta-intel build (ETA, today), update of AB infrastructure in the last weekend. Weekly build this week for QA is on track. - Go over the high bugs: 8 high bugs, 2 scheduled for M1, 1 still needs a target milestone. Mark will look into 2420. * SWAT team rotation: Beth - Paul * Opens - 5 min - RP: status of pull requests for oe-core. Last week concerned about master. There has been some changes in master, fixes, package update, doing testing over the weekend to make sure master is stable. Mark's patch and Nitin's are still outstanding, will be merged soon. Expect to see some other patches going into master in the next few days. - Michael: requests to enable http for git repos. Requests from the community, have trouble using git protocol to pull source code, asked to enable http. RP: sounds fine. Http access will be read-only. There are some technical issues with using https for pull requests (RP/Michael). - Jefro: conferences: check if anyone submitted any talks for any conf, if you have, please let jeff know: Mark has one for LinuxCon. Sean considering submit same topic for elce from elc. Dave: it's good to talk about your work, Dave will have an overview talk for the LinuxCon. - Josh: QA forum for the yocto project: Jefro: still on the plan, looking for a piece software compatible with Drupal. We have quote to build it. Still at the late design phase. * Team sharing - 20 min - Sean: nothing this week. - Sahad: nothing this week. - ScottR: last week some testing on 1.2.1, completed that. Will work on bug fixing for 1.3 m4. - Mark: working on prelink issues, something we have for x32 seems to have some problem, working on it. Integrating patches from mentor also. - Jeff: nothing this week - Bruce: Was out last week. Still catching up. Will work on 1.3 items. - Denys: was out last week. - Tom: working on getting 1.2 meta-intel BSPs released. Waiting for some kernel things to appear from Bruce (Bruce already know this). Then will move on to 1.3. - Darren: more time on fish-II. Accelerometer driver will turn into a much larger effort, working with maintainers. Worked on zigbee with Scott Garman also. This week finishing up meta-intel work. Move on to 1.3 work. - Michael: last week update bugzilla requests. There was an email sent out to the mailing list on the preview. Will make it alive if there is no objection. Gerneal AB work, some work on package.yoctoproject.org. - Paul: out 3 days last week. Submit and merged 2044.that threw out some other issues. Working on fixing them. Will be out whole week next week. - Richard: merging patches last week, submit some fixes, working through some bugs, reviewed patches. This week more of the same. Out next week for UK holiday. - Beth: AB upgrade, bugzilla upgrade, AB development cluster to test the things (will announce it in the mailing list). Working with an intern. Met him last weekend, trying to get him situated in Portland. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Web Hob 1.3 requirements
Hi Jim, Do you have any update on the progress of UI/process design about the webhob design? Thanks, Dongxiao From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Jim Kosem Sent: Tuesday, May 08, 2012 6:50 PM To: yocto@yoctoproject.org Subject: [yocto] Yocto Web Hob 1.3 requirements Hi, We in the Yocto London team have put together user requirements and ideas around what we think Web Hob should be. https://wiki.yoctoproject.org/wiki/Yocto_Webhob_1.3 Any contributions, help and comments are appreciated. Thanks. - Jim Kosem ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
