[yocto] [meta-intel][PATCH] linux-yocto: Add a patch to resolve undefined RUSAGE_SELF for perf.
From: Noor Ahsan
* Perf gived compilation error
CC builtin-sched.o
builtin-sched.c: In function ‘get_cpu_usage_nsec_parent’:
builtin-sched.c:399:16: error: storage size of ‘ru’ isn’t known
* Added a patch from linux kernel git repo commit id
7b78f13603c6fcb64e020a0bbe31a651ea2b657b which include resource.h
file in builtin-sched.c.
Signed-off-by: Noor Ahsan
---
.../linux/linux-yocto/linux-yocto_3.0.bbappend | 23
.../recipes-kernel/linux/linux-yocto_3.0.bbappend |8 +--
2 files changed, 29 insertions(+), 2 deletions(-)
diff --git
a/meta-cedartrail/recipes-kernel/linux/linux-yocto/linux-yocto_3.0.bbappend
b/meta-cedartrail/recipes-kernel/linux/linux-yocto/linux-yocto_3.0.bbappend
new file mode 100644
index 000..440cd77
--- /dev/null
+++ b/meta-cedartrail/recipes-kernel/linux/linux-yocto/linux-yocto_3.0.bbappend
@@ -0,0 +1,23 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+
+SRC_URI_cedartrail =
"git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;bareclone=1;branch=${KBRANCH},meta,yocto/pvr;name=machine,meta,pvr"
+
+SRC_URI_cedartrail-nopvr =
"git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta"
+
+COMPATIBLE_MACHINE_cedartrail = "cedartrail"
+KMACHINE_cedartrail = "cedartrail"
+KBRANCH_cedartrail = "yocto/standard/cedartrail"
+KERNEL_FEATURES_append_cedartrail += "bsp/cedartrail/cedartrail-pvr-merge.scc"
+KERNEL_FEATURES_append_cedartrail += "cfg/efi-ext.scc"
+
+COMPATIBLE_MACHINE_cedartrail-nopvr = "cedartrail"
+KMACHINE_cedartrail-nopvr = "cedartrail"
+KBRANCH_cedartrail-nopvr = "yocto/standard/cedartrail"
+KERNEL_FEATURES_append_cedartrail-nopvr += " cfg/smp.scc"
+
+SRCREV_machine_pn-linux-yocto_cedartrail ?= "${AUTOREV}"
+SRCREV_meta_pn-linux-yocto_cedartrail ?= "${AUTOREV}"
+SRCREV_pvr_pn-linux-yocto_cedartrail ?= "${AUTOREV}"
+
+SRCREV_machine_pn-linux-yocto_cedartrail-nopvr ?= "${AUTOREV}"
+SRCREV_meta_pn-linux-yocto_cedartrail-nopvr ?= "${AUTOREV}"
diff --git a/meta-cedartrail/recipes-kernel/linux/linux-yocto_3.0.bbappend
b/meta-cedartrail/recipes-kernel/linux/linux-yocto_3.0.bbappend
index 440cd77..6797eeb 100644
--- a/meta-cedartrail/recipes-kernel/linux/linux-yocto_3.0.bbappend
+++ b/meta-cedartrail/recipes-kernel/linux/linux-yocto_3.0.bbappend
@@ -1,8 +1,12 @@
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-SRC_URI_cedartrail =
"git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;bareclone=1;branch=${KBRANCH},meta,yocto/pvr;name=machine,meta,pvr"
+SRC_URI_cedartrail =
"git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;bareclone=1;branch=${KBRANCH},meta,yocto/pvr;name=machine,meta,pvr
\
+file://linux-yocto_3.0.bbappend \
+"
-SRC_URI_cedartrail-nopvr =
"git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta"
+SRC_URI_cedartrail-nopvr =
"git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta
\
+file://linux-yocto_3.0.bbappend \
+"
COMPATIBLE_MACHINE_cedartrail = "cedartrail"
KMACHINE_cedartrail = "cedartrail"
--
1.7.9.5
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] a wiki page on packagegroups -- now correct, I think :-)
total redesign of a page i lashed together in about 45 minutes to explain packagegroups since i feel it got short shrift in the yocto dev manual: http://www.crashcourse.ca/wiki/index.php/OE_package_groups note: my wiki pages are typically terse and consist mostly of ripping code out of OE or elsewhere since i find this handy for explaining concepts to students -- i actually bring up a wiki page and start scrolling through it, explaining the code bit by bit, but i don't add a lot of editorializing since *that's* what takes forever to write. but it's real easy to just copy and paste and build an informative wiki page in minutes that i can spend an hour explaining. :-) and one question while i'm here -- i notice the definition of a number of package groups in core-image.bbclass: ... snip ... PACKAGE_GROUP_x11 = "packagegroup-core-x11" PACKAGE_GROUP_x11-base = "packagegroup-core-x11-base" PACKAGE_GROUP_x11-sato = "packagegroup-core-x11-sato" PACKAGE_GROUP_tools-debug = "packagegroup-core-tools-debug" ... snip ... is that simply an equivalent way to include a package group into your (core-image-based) build? to use IMAGE_FEATURES? as opposed to simply referring to the packagegroup recipe file directly? thanks. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-ti with yocto
Hello,
Any help will be appreciated..
Following the steps at site
*http://maniacbug.wordpress.com/2012/08/03/pandayocto/* with minor
changes.
Not using poky-denzil-7.0 instead using latest version as of 12/22/12 (see
below). Did not git checkout 30fb40ebc13614a74c2e237927c60ac43e01d1bc
instead used version that was 07/09/12 which follows oe-core to v5.0. The
changes described were modified (see below diff local.conf &
local.conf.installed ) since quotes were needed for MACHINE & BBMASK. I
also tried with a build using Angstrom which fails but does create a kernel
uImage using linux-omap4-3.1.0-r1a. The meta-ti with yocto is fetching
linux-omap4-3.1.0-r0 which fails at do_fetch. This was fixed with a manual
fetch (see below on steps to download the kernel). Now the problem is
getting the pandaboard to boot.
Does a build with yocto and meta-ti require an initrd file? Does anyone
have a working uEnv.txt for the pandaboard?
Build system Fedora17 x86_17
cd /home/vidal/POKY/build122912_panda/
git clone git://git.yoctoproject.org/poky.git
cd poky
git clone *https://github.com/Angstrom-distribution/meta-ti.git*
/home/vidal/POKY/build122912_panda/poky
commit 4a36a32567ecfbc7ce7b967803e6e23314953ef5
Author: Martin Jansa http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel>>
Date: Sat Dec 22 17:24:20 2012 +0100
libpng: fix packaging
* PN-LIBV is not needed, was used to package libpng12 from libpng3 build
now only libpng15 is built.
* if you're not using OEBasicHash + PRserv you need to rebuild and
reinstall a lot of packages to upgrade to libpng-1.5 correctly
(From OE-Core rev: 69bbce0176183b0dc14eda21e4f6b601443060f0)
Signed-off-by: Martin Jansa http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel>>
Signed-off-by: Saul Wold http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel>>
Signed-off-by: Richard Purdie http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel>>
/home/vidal/POKY/build122912_panda/poky/build/conf/local.conf
*
--new text--
MACHINE ?= "pandaboard"
BBMASK = "meta-ti/recipes-misc"
--new text--
--additional text--
--modified text--
BB_NUMBER_THREADS = "8"
--modified text--
--additional text--
--modified text--
PARALLEL_MAKE = "-j 8"
--modified text--
--additional text--
--modified text--
DL_DIR ?= "/home/vidal/POKY/linux_sr_dnloads_panda/downloads"
--modified text--
--additional text--
*
/home/vidal/POKY/build129112_panda/poky/build/conf/bblayers.conf
*
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "6"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/home/vidal/POKY/build122912_panda/poky/meta \
/home/vidal/POKY/build122912_panda/poky/meta-yocto \
/home/vidal/POKY/build122912_panda/poky/meta-ti \
/home/vidal/POKY/build122912_panda/poky/meta-yocto-bsp \
"
BBLAYERS_NON_REMOVABLE ?= " \
/home/vidal/POKY/build122912_panda/poky/meta \
/home/vidal/POKY/build122912_panda/poky/meta-yocto \
"
*
/home/vidal/POKY/build129112_panda/poky/meta-ti/conf/machine/pandaboard.conf
*
#@TYPE: Machine
#@NAME: Pandaboard
#@DESCRIPTION: Machine configuration for the OMAP4430 Panda
require conf/machine/include/omap4.inc
UBOOT_MACHINE = "omap4_panda_config"
GUI_MACHINE_CLASS = "bigscreen"
IMAGE_FSTYPES += "tar.bz2"
SERIAL_CONSOLE = "115200 ttyO2"
MACHINE_EXTRA_RRECOMMENDS = " kernel-modules"
MACHINE_FEATURES = "kernel26 wifi bluetooth alsa apm ext2 screen
touchscreen usbgadget usbhost vfat"
*
/home/vidal/POKY/build122912_panda/poky/meta-ti/conf/machine/include/omap4.inc
*
SOC_FAMILY = "omap4"
require conf/machine/include/soc-family.inc
require conf/machine/include/tune-cortexa9.inc
PREFERRED_PROVIDER_virtual/kernel = "linux-omap4"
PREFERRED_PROVIDER_virtual/bootloader = "u-boot"
PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg"
XSERVER = "xserver-xorg \
xserver-xorg-extension-dri \
xserver-xorg-extension-dri2 \
xserver-xorg-extension-glx \
xf86-input-evdev \
xf86-video-fbdev"
# Increase this everytime you change something in the kernel
MACHINE_KERNEL_PR = "r1"
KERNEL_IMAGETYPE = "uImage"
UBOOT_ENTRYPOINT = "0x80008000"
UBOOT_LOADADDRESS = "0x80008000"
EXTRA
Re: [yocto] How to include RPM database into target image?
Hi Alex, On Saturday 29 December 2012 19:05:05 Alex J Lennon wrote: > I'm building a distro based on Yocto for a Raspberry Pi but I don't seem > to have the RPM database / sample feeds installed on the target image. > > Having hunted around and googled I can't spot the environment variable or > recipe I presumably need to set/include. You only need to ensure that "package-management" is present in IMAGE_FEATURES. You can do this from local.conf by adding the following to it: EXTRA_IMAGE_FEATURES += "package-management" This will ensure the package manager's database (RPM if you've selected RPM packaging) is preserved, but won't set up any sample feeds. The latter would need to be done manually or via ROOTFS_POSTPROCESS_COMMAND. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
