summaryrefslogtreecommitdiffstats
path: root/meta/recipes-kernel
Commit message (Collapse)AuthorAgeFilesLines
* linux-yocto/3.10: intel BSP configuration updatesBruce Ashfield2014-04-103-3/+3
| | | | | | | | | | | | | | Updating the SRCREV for the following configuration changes: 7df9ef8ee47d minnow: Add minnow-drivers-extra fragment 4f12b62002ca meta: smp.scc: increase default NR_CPUS to 64 de70ccd19f86 intel-common: change intel-corei7064-preempt-rt-scc filename e3780cd93809 meta: mohonpeak: remove branch 'mohonpeak' (From OE-Core rev: 20625df0f88b1948bfc05be0d2cbdaa201c3b2f0) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.14: beagleboard black: USB, DRM config tweaksBruce Ashfield2014-04-102-2/+2
| | | | | | | | | | | | | Importing the meta SRCREV to pick up the following two fixes: 928d7b2ddad0 beaglebone: enhance USB support and enable MUSB modules fbe38387ac61 beaglebone: enable DRM for HDMI output (From OE-Core rev: c95ae50dc0817fee291ca981c41cb556bf7db582) Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.14: intel configuration fixesBruce Ashfield2014-04-102-2/+2
| | | | | | | | | | | | | | | | Importing the intel configuration fixes from Darren Hart: a82ccc635e7a meta: Purge retired BSPs chiefriver, sys940x, and atom-pc b50ba1e37c26 x86: Drop X86_32 configs 8aa0a946f528 x86: Move MTRR config into x86 common fragments ddae217aefee common-pc: Remove SMP from common-pc*-cpu fragments f3ad83aa4c39 x86: Consolidate common x86* CPU features (From OE-Core rev: 399d3d51f35fd8782367e82c7b6e641f32396f80) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: intel-common: Add preempt-rt ktype targetsBruce Ashfield2014-04-103-3/+3
| | | | | | | | | | | Updating the meta SRCREV to incorporate the intel common preempt-rt kernel support. (From OE-Core rev: 63de385a2dce1727d6d4b42dfdf8cb38d8ae5792) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: v3.10.35 and emenlow boot fixesBruce Ashfield2014-04-103-16/+16
| | | | | | | | | | Updating the 3.10 SRCREVs to pick up 3.10.35 and a LTSI cherry pick that fixes a boot issue with the emenlow. (From OE-Core rev: f0990363aaeb3f8f7a8e02fc2acb0af2171e4eba) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: update to v3.4.85Bruce Ashfield2014-04-103-15/+15
| | | | | | | | | Updating the SRCREVs to integrate the latest korg -stable update. (From OE-Core rev: c6fe4b287c204d31a9ab86e3f38336d8828903ee) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: Fix sysroot option to CC handlingRichard Purdie2014-04-101-0/+12
| | | | | | | | | | | | | | | | | | | | | | If you build perf in tree /xxx/treea, then cleansstate perf and build it in /xxx/treeb having deleted treea, the build will fail, unable to find libc. The problem is that the --sysroot option passed in through CC is missing. This works fine if the default sysroot is ok, if it isn't, things will fail. In 1.7 we'll start poisoning the default sysroot in gcc to catch this kind of issue however that doesn't fix the problem with perf. The problem is that various Makefiles set CC = $(CROSS_COMPILE)gcc. The easist fix for now is to sed out the problematic Makefile lines. Its worth noting the tools/lib/traceevent Makefile has a much more funky way of setting CC which works for us and may be the way we need to fix the other Makefiles upstream. This fixes build failures we're occasionally seen on the autobuilders. (From OE-Core rev: d9bd1ac6d91de932dd3e2fcac9da77e0a7c09f55) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernelshark/trace-cmd: fix syntax error of shellChong Lu2014-04-104-1/+63
| | | | | | | | | | | | | Delete "<<<" syntax of bash in Makefile, else we would get following error: Syntax error: redirection unexpected [YOCTO #6112] (From OE-Core rev: c2892fa27d9918aa4ce00a106a254ddfd44aa0f1) Signed-off-by: Chong Lu <Chong.Lu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemtap: Move to current HEADTom Zanussi2014-04-051-1/+1
| | | | | | | | | | | | This moves the systemtap recipe to the current HEAD commit, in order to get users past some bugs affecting ppc and arm. Fixes [YOCTO #6016] (From OE-Core rev: efac179f243459c53d0431fbcce92a3561b40956) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kmod: fix O_CLOEXEC not supported on old kernelRobert Yang2014-04-012-0/+39
| | | | | | | | | | | | | | | O_CLOEXEC is introduced from Linux 2.6.23, so old kernel doesn't have it, we need check before use. This patch is much more like a workaround, since it may need fcntl() use FD_CLOEXEC to replace. (From OE-Core rev: 44c441222002ee0177100be0431adf91984e90d5) Signed-off-by: Ting Liu <b28495@freescale.com> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemux86-64: re-enable paravirt guest, bring it in sync with qemux86Stefan Stanacar2014-04-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Seems wrong that qemux86 has this enabled and qemux86-64 doesn't. Also this will allow people to use kvm with -cpu=host. Right now, runqemu qemux86-64 kvm uses -cpu=kvm64 because without this feature you can't use cpu=host on newer host kernels (>= 3.8). This basically reverts poky e6149ec6c4c14d3a939022cdc29ac94dced836dd / oe-core 64749308fadabb4aa7c39f360c6395827bc5eb3a The reason of that commit (which is more than a year old) was that on the AB running old kernels (2.6.37) we would see occasional shutdown failures. (but if memory serves me right the fix might have been just a coincidence). I've tested this change with by: - run tests on runqemu qemux86-64 (without kvm) (300 seconds) - run tests on runqemu qemux86-64 kvm (which uses by default cpu=kvm64) - (tests took 20 seconds) - run tests on runqemu qemux86-64 kvm with cpu=host - (tests took 18 seconds) [ YOCTO #5956 ] (From OE-Core rev: 4b09a1869895e4cd18e82b7d190fbfea3c7922af) Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: remove 3.10 recipeBruce Ashfield2014-03-314-154/+0
| | | | | | | | | | | 3.14 is now the reference for libc-headers. After building and booting 3.x based BSPs against the 3.14 headers, we can safely remove the old version and patches that are now part of the mainline kernel. (From OE-Core rev: ade26bc63fdf89f297bec5f67bfff108e90438fc) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: add 3.14 libc headersBruce Ashfield2014-03-311-0/+7
| | | | | | | | | | | | | Introduce the 3.14 linux-libc-headers recipe, now that the 3.14 kernel is available, and the default for the qemu reference BSPs. The three patches which were required for the previous 3.10 libc-headers are not required for 3.14 and can be ignored. (From OE-Core rev: 6b25918ecce6d555632d9576e16ad443b5d1780a) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: make compression format configurableBruce Ashfield2014-03-311-1/+3
| | | | | | | | | | | | As of the 3.13 kernel bz2 compressed tarballs are not available. To support older header tarballs, and newer ones that require the 'xz' compressed bundles, we can break out a variable that allows versioned libc headers to select the archive format that works. (From OE-Core rev: 116228fceca7fc2a7b557133b1f8f28f41af1ee5) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.14: introduce versioned recipesBruce Ashfield2014-03-312-0/+58
| | | | | | | | | | The release kernel for Yocto 1.6 is the 3.14 kernel, so we introduce the versioned recipes here. (From OE-Core rev: 92776093766d4b0bb2613214274fa28dc59b6126) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: fix qemuarm build failureBruce Ashfield2014-03-301-1/+1
| | | | | | | | | | The v3.10.24 merge created a merge conflict, which was not properly resolved. Fixing the merge conflict and fixing the build of qemu arm. (From OE-Core rev: 2116e326d9d7039aac4ec6c7ae5d2a2bedfb4a74) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-ust: add python to lttng-ust's RDEPENDSHongxu Jia2014-03-301-0/+1
| | | | | | | | | | | | | | | | | | | | | | Note: adding Smart RPM DB channel | | Note: to be installed: run-postinsts@x86_64 kernel-modules@qemux86_64 packagegroup-core-boot@qemux86_64 lttng-ust@x86_64 | Loading cache... | Updating cache... ######################################## [100%] | | Computing transaction...error: Can't install lttng-ust-2:2.3.0-r0.0@x86_64: no package provides /usr/bin/python | | Saving cache... | | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_rootfs (log file is located at tmp/work/qemux86_64-wrs-linux/wrlinux-image-glibc-small/1.0-r1/temp/do_rootfs/log.do_rootfs.13619) (From OE-Core rev: 0360a49f0c216b3f35c4bffabab3406c31589fd3) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.8: remove versioned recipesBruce Ashfield2014-03-303-95/+0
| | | | | | | | | | | Yocto 1.6 will support the LTSI 3.4/3.10 kernels and the 3.14 kernel. As such, we remove the 3.8 linux-yocto recipes to keep our number of supported kernels at three. (From OE-Core rev: 940137ed36e1274bcb4e6b246b69c8c9172cabf7) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: fix drm build failureBruce Ashfield2014-03-303-10/+10
| | | | | | | | | | | | | | | | | | | | | | | Andrea Adami reported the following build failure: .../drm/drm_mm.h:105:2: error: implicit declaration of function 'BUG_ON' [-Werror=implicit-function-declaration] | BUG_ON(!hole_node->hole_follows); | ^ | CC drivers/pci/setup-res.o | CC drivers/gpu/drm/i915/i915_drv.o | cc1: some warnings being treated as errors | make[6]: *** [drivers/gpu/drm/ttm/ttm_agp_backend.o] Error 1 | make[5]: *** [drivers/gpu/drm/ttm] Error 2 Cherry picking mainline commit 86e81f0e6 [drm/mm: include required headers in drm_mm.h] fixes the build problems. cc: Andrea Adami <andrea.adami@gmail.com> (From OE-Core rev: 42c0eba4fac6b8bd28b58ec04574d04b0ab0c457) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: update intel common meta dataBruce Ashfield2014-03-303-3/+3
| | | | | | | | | | | | Bumping the meta branch SRCREV for the following two commits: df3aa753c882 intel-common: Add media-all to the standard builds 4b0d57269dae intel-common: Add mohonpeak BSP (From OE-Core rev: 821b1c03db3793609e3ae564358de10e23591604) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: update to v3.10.34Bruce Ashfield2014-03-303-16/+16
| | | | | | | | | Updating to the latest korg -stable release. (From OE-Core rev: 4d636396435f1165481cb103512026a8660ca8b2) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: add valleyisland ioBruce Ashfield2014-03-303-3/+3
| | | | | | | | | | Updating the 3.10 meta SRCREV to include the valleyisland IO .scc and configuration files. (From OE-Core rev: 5adccadee00ac4408d3b3d4e6a0b7ee7c84cba97) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: update to v3.10.33Bruce Ashfield2014-03-303-13/+13
| | | | | | | | | Updating to the latest -stable release. (From OE-Core rev: 9acc956c23ea161d0af691ff4685b472d3eff086) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: update EFI configurationBruce Ashfield2014-03-303-3/+3
| | | | | | | | | | | | Importing the following two meta data changes for EFI configuration: 284e9589436a meta: efi.cfg/efi-ext.cfg: add EFIVAR_FS to default efi fragment 0a8c4971e2d9 meta: update efi config fragment to include EFI_STUB by default (From OE-Core rev: ec6ff275ba44ec183c00910f47e5b8916e58ab14) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: update mohonpeak.cfg for SATA, SMBus, LPC, WDT, crypto & ↵Bruce Ashfield2014-03-303-3/+3
| | | | | | | | | | | highmem64g Updating the meta SRCREV with the latest configuration updates. (From OE-Core rev: 8e98af96a4b2b725724cd97276168c03e95aa99d) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: intel-core*/common configuration updatesBruce Ashfield2014-03-303-3/+3
| | | | | | | | | | | | | | | Importing the following configuration changes to support the latest intel common BSPs: 6e0e756d5137 intel-common: Remove GMA500 support 226c3b7a2b82 intel-core*: Add baytrail soc support 25df7acf2cc4 baytrail: Add feature/soc/baytrail 8715856ab617 meta: input: add CONFIG_INPUT dependency (From OE-Core rev: 88d2bb9c5959a9b1e744bb517c26a322cd537023) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-dummy: provide kernel-modules (empty) packageMatthieu Crapet2014-03-211-6/+12
| | | | | | | | | Like it is done in kernel.bbclass (From OE-Core rev: 5df4e63e747028c3ce89f1f9ae01a766ae34dc3d) Signed-off-by: Matthieu Crapet <Matthieu.Crapet@ingenico.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: add libexec and traceevent to packagesBruce Ashfield2014-03-211-1/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Recent versions of perf may install files into /usr/libexec/perf-core and in /usr/lib/traceevent. To avoid packaging QA errors, we add these two directories to the FILES variables. We also add: INHIBIT_PACKAGE_DEBUG_SPLIT="1" to avoid the following issue (due to a trailing / being removed): ERROR: debugedit failed with exit code 256 ... debugedit: canonicalization unexpectedly shrank by one character And finally, we must ensure that the traceevent libraries are installed to the proper multilib library path. If building some multlibs, the incorrect library path will be selected by perf, since it triggers via: ifeq ($(ARCH),x86_64) (or similiar mechanism per arch). In a 32 bit build, with a 64 bit multilib, the arch won't match and the detection of a 64 bit build (and library) are not exected. To ensure that libraries are installed to the correct location, we can make the substitution in the config/Makefile. For non multilib builds, this has no impact. (From OE-Core rev: c1b5a262c0201faf2c6bf545d6acb32dfe383ba3) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: don't use oe.path.relativeRoss Burton2014-03-071-4/+4
| | | | | | | | | | | Instead of using oe.path.relative, use the Python Standard Library function os.path.relpath. (From OE-Core rev: 01f640f2e878ef86db4138f422fdf74f5f41c8c5) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-ust: Disable doc/examples in the buildTom Zanussi2014-03-072-0/+19
| | | | | | | | | | | Don't build the doc examples - we don't need them and in fact they never successfully built in previous iterations of the lttng-ust recipe anyway. (From OE-Core rev: d798bd1d25ae0e57b65758c54f033afda96c14e1) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-modules: Fix 3.14 bio tracepointsTom Zanussi2014-03-072-1/+158
| | | | | | | | | | The mainline 3.14 commit 'block: Astract out bvec iterator' broke the lttng-modules tracepoints. Fix them here. (From OE-Core rev: c11b29ff4f24af0445c3c6a694b8dc2037dcd7e4) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-modules: Exclude armTom Zanussi2014-03-071-0/+3
| | | | | | | | | | | lttng-modules and gcc-4.8 don't mix, according to the lttng ML 'current_thread_info() not respecting program order with gcc 4.8.x', so remove it from arm builds. (From OE-Core rev: ccf687de7b856dbe6f347956743f07ff05c2533a) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-ust: Add version 2.4.0Tom Zanussi2014-03-071-0/+31
| | | | | | | | | | This updates lttng-ust to 2.4.0, codenamed Époque Opaque, needed for interoperability with lttng-modules and the 3.14 (dev) kernel. (From OE-Core rev: b4ae73a86ccf62a508faa76dc349bbab02540c37) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-tools: Add version 2.4.0Tom Zanussi2014-03-072-0/+86
| | | | | | | | | | This updates lttng-tools to 2.4.0, codenamed Époque Opaque, needed for interoperability with lttng-modules and the 3.14 (dev) kernel. (From OE-Core rev: da5aaafa8c47d9daadb34adbddc93e0f18ec6259) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-modules: Add version 2.4.0Tom Zanussi2014-03-071-0/+34
| | | | | | | | | | This updates lttng-modules to 2.4.0, codenamed Époque Opaque, needed for interoperability with the 3.14 (dev) kernel. (From OE-Core rev: bc9a310f920ae17330c749f2263f884423e9b050) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes: bump PRsMartin Jansa2014-03-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * resolves following warnings: WARNING: Use of PRINC 17 was detected in the recipe meta-openembedded/meta-systemd/recipes-core/systemd/systemd-machine-units_1.0.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe meta-openembedded/meta-gpe/recipes-support/fbreader/fbreader_0.12.10.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe meta-openembedded/meta-gpe/recipes-support/fbreader/fbreader_git.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe meta-openembedded/meta-multimedia/recipes-multimedia/sox/sox_14.4.0.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe meta-openembedded/meta-oe/recipes-multimedia/mplayer/mplayer-common.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe meta-smartphone/meta-android/recipes-bsp/chroot-script/chroot-script_1.0.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-connectivity/avahi/avahi-ui_0.6.31.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-connectivity/bind/bind_9.8.1.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-core/systemd/systemd-serialgetty.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-extended/screen/screen_4.0.3.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-extended/shadow/shadow-securetty_4.1.4.3.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-extended/shadow/shadow_4.1.4.3.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-graphics/libsdl/libsdl_1.2.15.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-graphics/packagegroups/packagegroup-core-x11-xserver.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-kernel/modutils-initscripts/modutils-initscripts.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-multimedia/libsndfile/libsndfile1_1.0.25.bb (or one of its .bbappends) WARNING: Use of PRINC 1 was detected in the recipe openembedded-core/meta/recipes-support/libcap/libcap_2.22.bb (or one of its .bbappends) WARNING: Use of PRINC 11 was detected in the recipe openembedded-core/meta/recipes-bsp/keymaps/keymaps_1.0.bb (or one of its .bbappends) WARNING: Use of PRINC 11 was detected in the recipe openembedded-core/meta/recipes-core/systemd/systemd-compat-units.bb (or one of its .bbappends) WARNING: Use of PRINC 12 was detected in the recipe openembedded-core/meta/recipes-core/initscripts/initscripts_1.0.bb (or one of its .bbappends) WARNING: Use of PRINC 13 was detected in the recipe openembedded-core/meta/recipes-core/base-files/base-files_3.0.14.bb (or one of its .bbappends) WARNING: Use of PRINC 2 was detected in the recipe meta-openembedded/meta-oe/recipes-navigation/navit/navit_svn.bb (or one of its .bbappends) WARNING: Use of PRINC 2 was detected in the recipe meta-openembedded/meta-oe/recipes-support/lvm2/lvm2_2.02.97.bb (or one of its .bbappends) WARNING: Use of PRINC 2 was detected in the recipe openembedded-core/meta/recipes-connectivity/portmap/portmap_6.0.bb (or one of its .bbappends) WARNING: Use of PRINC 2 was detected in the recipe openembedded-core/meta/recipes-extended/pam/libpam_1.1.6.bb (or one of its .bbappends) WARNING: Use of PRINC 2 was detected in the recipe openembedded-core/meta/recipes-graphics/packagegroups/packagegroup-core-x11.bb (or one of its .bbappends) WARNING: Use of PRINC 3 was detected in the recipe meta-openembedded/meta-efl/recipes-efl/efl/entrance_svn.bb (or one of its .bbappends) WARNING: Use of PRINC 3 was detected in the recipe meta-openembedded/meta-oe/recipes-multimedia/mplayer/mplayer2_git.bb (or one of its .bbappends) WARNING: Use of PRINC 3 was detected in the recipe openembedded-core/meta/recipes-bsp/formfactor/formfactor_0.0.bb (or one of its .bbappends) WARNING: Use of PRINC 3 was detected in the recipe openembedded-core/meta/recipes-connectivity/avahi/avahi_0.6.31.bb (or one of its .bbappends) WARNING: Use of PRINC 3 was detected in the recipe openembedded-core/meta/recipes-connectivity/dhcp/dhcp_4.2.5-P1.bb (or one of its .bbappends) WARNING: Use of PRINC 3 was detected in the recipe openembedded-core/meta/recipes-core/init-ifupdown/init-ifupdown_1.0.bb (or one of its .bbappends) WARNING: Use of PRINC 3 was detected in the recipe openembedded-core/meta/recipes-graphics/xinput-calibrator/pointercal-xinput_0.0.bb (or one of its .bbappends) WARNING: Use of PRINC 5 was detected in the recipe meta-openembedded/meta-oe/recipes-core/meta/distro-feed-configs.bb (or one of its .bbappends) WARNING: Use of PRINC 5 was detected in the recipe openembedded-core/meta/recipes-connectivity/bluez/bluez4_4.101.bb (or one of its .bbappends) WARNING: Use of PRINC 6 was detected in the recipe openembedded-core/meta/recipes-core/packagegroups/packagegroup-base.bb (or one of its .bbappends) WARNING: Use of PRINC 6 was detected in the recipe openembedded-core/meta/recipes-core/packagegroups/packagegroup-core-boot.bb (or one of its .bbappends) WARNING: Use of PRINC 6 was detected in the recipe openembedded-core/meta/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bb (or one of its .bbappends) WARNING: Use of PRINC 7 was detected in the recipe meta-openembedded/meta-oe/recipes-navigation/gpsd/gpsd_3.7.bb (or one of its .bbappends) WARNING: Use of PRINC 7 was detected in the recipe openembedded-core/meta/recipes-core/udev/udev-extraconf_1.0.bb (or one of its .bbappends) (From OE-Core rev: c6825ec6e92e20bb64a051d1576f363c16e98d68) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oprofile: Partially fix separate builddir supportRichard Purdie2014-03-051-1/+1
| | | | | | | | | It doesn't make separate build completely work but its worth merging as one step in the right direction. (From OE-Core rev: 2c4942ab36d66de9c189e8c116195f67f2894a08) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto-dev: bump to v3.14-rc4Bruce Ashfield2014-02-281-1/+1
| | | | | | | | | | Updating the version of linux-yocto-dev to reflect the integration of the 3.14-rc4 kernel. (From OE-Core rev: 9c5734b91c274be85200a9790202326dd6debfc1) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autotools-brokensep: Mark recipes with broken separate build dir supportRichard Purdie2014-02-284-4/+4
| | | | | | | | | | | | This patch goes through the OE-Core recipes and marks those which use autotools but don't support a separate build directory (${S} != ${B}). A new class, autotools-brokensep is used for this purpose. This doesn't introduce any change in behaviour in its own right. (From OE-Core rev: 006b8a7808a58713af16c326dc37d07765334b12) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: integrate latest LTSI changesBruce Ashfield2014-02-283-10/+10
| | | | | | | | | | Integrating the latest 3.10 LTSI changes into the yocto tree. (From OE-Core rev: 19e9dded1761e09ed713c72c7153501e625a3859) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: update to v3.4.82 and latest LTSIBruce Ashfield2014-02-283-15/+15
| | | | | | | | | | | Updating the 3.4 tree to the 3.4.82 -stable update, and integrating the latest LTSI changes. (From OE-Core rev: 97518da4d03cdc6a3a9ddfce0475d2f6189dc390) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: update to v3.10.32Bruce Ashfield2014-02-283-16/+16
| | | | | | | | | | | Integrating the latest korg -stable update for the 3.10 series of kernels. (From OE-Core rev: 66d976af752708579d86a505b899854abc111a19) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: enable CONFIG_FHANDLE for standard and preempt-rt kernelsBruce Ashfield2014-02-143-3/+3
| | | | | | | | | | | | | | | CONFIG_FHANDLE is now a requirement for systemd support: http://cgit.freedesktop.org/systemd/systemd/commit/README?id=c2cb7cbbd526e572b1caa1d7f70be68195b513a9 So we add it into our default standard and preempt-rt kernel types, the overhead is small and having this always configured allows init system switching, without a kernel rebuild. (From OE-Core rev: 63d5be8f7fec74a7e4bac36b28e93071119cdf6d) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: add minnow-io feature to LTSIBruce Ashfield2014-02-143-13/+13
| | | | | | | | | | | | | The initial merge of the LTSI 3.10 content was missing the minnow-io feature. This has now been added to standard/ltsi and merged to all branches in the tree. We also update the meta branch to ensure that the existing feature will not attempt to apply patches to the tree, since they have now been integrated. (From OE-Core rev: 8569e2488e45fc7cabbdafe240ca404b2b2e8519) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: arbitrary write with CONFIG_X86_X32 (CVE-2014-0038)Bruce Ashfield2014-02-143-10/+10
| | | | | | | | | Integrating the upstream commit for CVE-2014-0038. (From OE-Core rev: 9073969d7b7d5d20377ab0c1a49f8e5bb051601b) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: update to v3.10.28Bruce Ashfield2014-02-143-13/+13
| | | | | | | | | | Updating the 3.10 kernel SRCREVs to integrate the v3.10.27, 27 and 28 -stable releases. (From OE-Core rev: 91fb7cfaeb8ea1c05a15a0be8a56ac50b95fd6e4) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemtap_git: update to newer version to fix a build issueNitin A Kamble2014-02-141-2/+2
| | | | | | | | | | | | | | | | | | This build issue was observed with the 2.4+git version of the systemtap. .../x86_64-linux/systemtap-native/2.4+gitAUTOINC+9190b3acfe-r0/git/tapsets.cxx: In function 'void validate_module_elf(Dwfl_Module*, const char*, base_query*)': .../x86_64-linux/systemtap-native/2.4+gitAUTOINC+9190b3acfe-r0/git/tapsets.cxx:1998:10: error: 'EM_AARCH64' was not declared in this scope .../x86_64-linux/systemtap-native/2.4+gitAUTOINC+9190b3acfe-r0/git/tapsets.cxx: In constructor 'sdt_uprobe_var_expanding_visitor::sdt_uprobe_var_expanding_visitor(systemtap_session&, int, const string&, const string&, const string&, stap_sdt_probe_type, const string&, int)': .../x86_64-linux/systemtap-native/2.4+gitAUTOINC+9190b3acfe-r0/git/tapsets.cxx:5613:31: error: 'EM_AARCH64' was not declared in this scope This is a known issue, and it is already fixed in the upstream tree. Updating the recipe to get the commit which fixes the issue. (From OE-Core rev: 5170f58f4a46edead40d98f302ba3294e078c113) Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: Use PACKAGE_ARCH in build dirDarren Hart2014-02-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The current linux-yocto build dir (B) includes MACHINE. This has been appropriate as kernels are typically built machine-specific. We have recently introduced an intel-common type kernel which can be shared across multiple machines sharing a common base (intel-core2-32, intel-corei7-64). In these cases, the kernel is built for a something more generic than MACHINE, and the current mechanism results in something like this when building for MACHINE=sys940x (using intel-common): tmp/work/core2-32-intel-common-poky-linux/linux-yocto-dev/ \ 3.13++gitAUTOINC+e5d23e7879_889c6bec6b-r0/linux-sys940x-noemgd-standard-build Note the descrepancy between core2-32-intel-common and linux-sys940x-noemgd-standard-build. This becomes counterintuitive at the very least when switching to another machine and attempting to reuse this build. This patch swaps MACHINE for PACKAGE_ARCH (which is typically MACHINE_ARCH for linux-yocto), resulting in the following build path: tmp/work/core2-32-intel-common-poky-linux/linux-yocto-dev/ \ 3.13++gitAUTOINC+e5d23e7879_889c6bec6b-r0/linux-core2-32-intel-common-standard-build The impact to existing MACHINEs is a replace of - with _ if MACHINE contains one or more - charachters. (From OE-Core rev: 54590cdb940b6145ac92729ebf9bb7e7e537f5e2) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: add powermanagement config to 32 bit common-pcBruce Ashfield2014-02-113-3/+3
| | | | | | | | | | | The introduction of LTSI has exposed a missing dependency on cpufreq being enabled. To fix the build, we enable power management in the 32 bit BSP, which aligns it with 64 bit. (From OE-Core rev: e859ebf08e73091640bd4d7329bbbe44270c4bf0) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: integrate LTSIBruce Ashfield2014-02-113-10/+10
| | | | | | | | | | | | | | Updating the SRCREVs of the 3.10 tree to reflect the integration of of commit 68054859 from: git://git.linuxfoundation.org/ltsi-kernegit://git.linuxfoundation.org/ltsi-kernel.git Build and boot tested on all qemu architectures. (From OE-Core rev: 41a6b620f6e00d9222989058b3620cadc940ac21) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-05-25 01:53:36 +0000