summaryrefslogtreecommitdiff
path: root/meta/recipes-kernel
AgeCommit message (Collapse)AuthorFiles
2015-10-01linux-yocto_{3.14,3.19,4.1}: qemuarm enable virtio driversAníbal Limón3
We are experimenting segfault in qemu arm SCSI driver because it's broken [1][2] so enable virtio drivers to use as default. [YOCTO #8060] [1] https://lists.gnu.org/archive/html/qemu-devel/2007-03/msg00093.html [2] https://lists.nongnu.org/archive/html/qemu-devel/2010-07/msg01473.html Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-10-01lttng-tools: Drop KERNELDIR referenceRichard Purdie1
The source makes no reference to KERNELDIR any more and this make the recipe machine specific. Simply drop the unused reference. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-10-01kern-tools: fix multi-layer patch applicationBruce Ashfield1
Updating the kern-tools SRCREV to import the following fix: kgit-meta: resume after last applied patch When the auto-resume (resume point detection) was removed from the processing of a meta-series, it ignored the fact that a single patch series may in fact be processed a number of times. Two layers patching a kernel will generate two different runs on the same branch, which always start at patch one. This will obviously break with duplicate patches. To avoid this, we simply track the last patch applied, and explicitly tell the patch scripts where to start. This gets us resume functionality, without the overhead of resume point detection. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-10-01linux-yocto/4.1: braswell bug fixesBruce Ashfield3
Updating the 4.1 SRCREVs to integrate the following DRM backports: a8abc111a96d drm/i915: Only wait for required lanes in vlv_wait_port_ready() 81354180432b Revert "drm/i915: Hack to tie both common lanes together on chv" d660fc117731 drm/i915: Work around DISPLAY_PHY_CONTROL register corruption on CHV 0e797e9cb717 drm/i915: Implement chv display PHY lane stagger setup Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-10-01linux-yocto/4.1: update to 4.1.8 -stableBruce Ashfield3
There are some important fixes and CVEs in 4.1.8, so we update the SRCREVs to integrate the -stable changes. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-10-01linux-yocto-rt/4.1: integrate axxia BSPBruce Ashfield1
As part of the axxia preempt-rt integration, the preempt-rt branch now becomes standard/preempt-rt/base, to allow proper branch inheritance as: standard/preempt-rt/axxia/base. No functional changes happen to the base -rt, just the default KBRANCH changes. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-10-01meta: fix build with gettext 0.16.1Robert Yang2
The gettext 0.16.1 doesn't install any m4 files to sysroot, please see the following commit: commit 9e10db5bdfe77c0ef2aff2f1cf89958b62c294a1 Author: Christopher Larson <kergoth@gmail.com> Date: Mon Mar 17 18:10:54 2014 +0000 gettext-0.16.1: kill target m4 macros from sysroot This is aim for using gettext-native's macros(gettext-native-0.19.4), but when we set: PREFERRED_VERSION_gettext = "0.16.1" And build the recipes like pcmanfm, we would get errors when do_configure: configure:5164: error: possibly undefined macro: AM_NLS This is because autotools_copy_aclocals doesn't copy the native macros for target unless they're direct dependencies. Add gettext-native to DEPENDS will fix the problem. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-29classes/meta: Add DISTRO_FEATURES check for gtk+/gtk3+Richard Purdie3
If you currently do a DISTRO_FEATURES_remove = "x11" with OE-Core, you see failures due to dependency problems. The work in resolving this was partially completed a while back. This adds in the markup mainly for gtk/gtk3+ recipes and means "bitbake world" will work successfully. Rather than code the gtk/gtk+ specific distro features into each recipe, a shared variable is used. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-28linux-yocto/4.1: rt update to 4.1.x-rt8Bruce Ashfield3
The -rt build suffered the same breakage in master as the standard kernel builds: due to a bad git history merge, existing patches were dropped from branches. This meant that we were missing the -rt changes, which re-introduced some failures with linux-yocto-rt. With these SRCREV updates, we have the latest 4.1.x-rt and all architectures build. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-28linux-yocto/4.1: common-pc-drivers: add CONFIG_PATA_SCHBruce Ashfield3
Updating the meta SRCREVs to integrate the following config change: Author: Saul Wold <sgw@linux.intel.com> Date: Tue Sep 22 07:23:06 2015 -0700 common-pc-drivers: add CONFIG_PATA_SCH The NUC uses this hardware and should still operate correctly with a genericx86 Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-23kmod: Change SRCREV to fix return code in error pathAníbal Limón1
Systemd is failing trying to load kdbus [1] because kmod have an error in return code when try to insert module [2]. This change of SRCREV is a MINOR one only include the fix described. [YOCTO #8377] [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=8377#c0 [2] http://lists.freedesktop.org/archives/systemd-devel/2015-July/033549.html Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-22linux-yocto/4.1: hid, bluetooth, aufs and yaffs2 updatesBruce Ashfield3
Setting the SRCREVs to import the following changes in the 4.1 kernel tree: 79a31b9d23db hid-core: Avoid uninitialized buffer access 121593d3a0a4 aufs: call mutex.owner only when DEBUG_MUTEXES or MUTEX_SPIN_ON_OWNER is defined efa7952a190f Bluetooth: Delay check for conn->smp in smp_conn_security() 69428ec43bd9 cc2520: set the default fifo pin value from platform data ee0ddf37f3d6 fs/yaffs2: Fix a judgement logic for ACL operations fff29e47f5c4 yaffs2: remove read and write methods b3b9d030ad84 yaffs2: replace f_dentry to f_path.dentry Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-21linux-yocto: depend on libgcc for nios2Marek Vasut1
Make nios2 kernel depend on libgcc. In arch/nios2/Makefile, it adds LIBGCC to libs-y: LIBGCC := $(shell $(CC) $(KBUILD_CFLAGS) -print-libgcc-file-name) libs-y += $(LIBGCC) In file Makefile in top directory, libs-y is assigned to to var KBUILD_VMLINUX_MAIN. It uses script link-vmlinux.sh to link vmlinux.o, and when execute function vmlinux_link() in link-vmlinux.sh, KBUILD_VMLINUX_MAIN is passed to ${LD}. If build without libgcc, the value of LIBGCC is just libgcc.a without parent directory. linux-yocto fails to build: | LD vmlinux.o | nios2-poky-linux-ld.bfd: cannot find libgcc.a: No such file or directory Add libgcc to nios2 kernel dependency. Signed-off-by: Marek Vasut <marex@denx.de> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-21lttng-tools: sessiond: disable: match app event by nameLi Zhou2
Get upstream patch from lttng-tools github: <https://github.com/lttng/lttng-tools> <commit:700c5a9d4dc7b552926b8ddcbba91cc13312aba0>, for solving the filtered tracepoint disabling error. The use of a simple lookup and match on event name is insufficient to identify the corresponding ust app event. Signed-off-by: Li Zhou <li.zhou@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-21linux-yocto/4.1: hid-core: Avoid uninitialized buffer accessBruce Ashfield3
Updating the 4.1 SRCREVs to integrate the following commit: hid-core: Avoid uninitialized buffer access hid_connect adds various strings to the buffer but they're all conditional. You can find circumstances where nothing would be written to it but the kernel will still print the supposedly empty buffer with printk. This leads to corruption on the console/in the logs. Ensure buf is initialized to an empty string. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> [dvhart: Initialize string to "" rather than assign buf[0] = NULL;] Cc: Jiri Kosina <jikos@kernel.org> Cc: linux-input@vger.kernel.org Cc: stable@vger.kernel.org Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-19kern-tools: optimize patching peformanceBruce Ashfield1
Updating the kern-tools SRCREV to integrat the following commit: patching: only validate user supplied patches by default Previously the patching tools would consider both system and user supplied patches in the same manner .. they are simply a series of patches to be applied to a branch, and that the scripts should determine where in the series to start (based on what is already on the branch). This detection was causing a few problems: - time consuming - starting in the middle of a series when intermediate patches were merged to a branch. To solve both the performance and start detection, we instead simply note the transition from system (i.e. already defined features and series) and user/recipe supplied patches. When the transition is noted, the system will start pushing ALL patches without doing autoresume detection. Control in keeping the series up to date is passed to the user, and consistent behaviour/performance is achieved. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-19linux-yocto/4.1: aufs, yaffs2 and driver fixesBruce Ashfield3
Updating the 4.1 SRCREVs to integrate the following changes: f830ab33799d aufs: call mutex.owner only when DEBUG_MUTEXES or MUTEX_SPIN_ON_OWNER is defined 87df2e93ed65 Bluetooth: Delay check for conn->smp in smp_conn_security() b09c3eab3e50 cc2520: set the default fifo pin value from platform data 62b01c325d42 fs/yaffs2: Fix a judgement logic for ACL operations 1d19c4e95cfc yaffs2: remove read and write methods 2c822dbc43b9 yaffs2: replace f_dentry to f_path.dentry Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-16perf: mkdir ${B} -> mkdir -p ${B}Robert Yang1
${B} is the default cwd of tasks, so there might be race issues such as: | mkdir: cannot create directory `/path/to/work/qemux86-poky-linux/perf/1.0-r9/perf-1.0/': File exists [snip] NOTE: recipe perf-1.0-r9: task do_configure: Failed Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-16cryptodev-tests: don't use STAGING_KERNEL_DIR, fix re-packaging in ↵Denys Dmytriyenko1
multi-machine builds Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-16linux-firmware: package Broadcom BCM4354 firmwareRomain Perier1
Signed-off-by: Romain Perier <romain.perier@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-16perf: fix the install-python_ext on upstream kernelRoy Li1
The Perf source code between Yocto and upstream are different, like below commit is not in upstream, so broaden the "--root" replacement to Makefile* commit 33e96fb1e2d77541e81eb341ccd3fbe9419e4c9a Author: Tom Zanussi <tom.zanussi@intel.com> Date: Tue Jul 3 13:07:23 2012 -0500 perf: change --root to --prefix for python install Otherwise we get the sysroot path appended to the build path, not what we want. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Roy Li <rongqing.li@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-16kmod: fix link creation when base_bindir != /binJoshua Lock1
If base_bindir is not a direct child of / the link creation in do_install_append creates incorrect relative links. Instead pass a full path to the link source too the lnr script to create a relative link. Signed-off-by: Joshua Lock <joshua.lock@collabora.co.uk> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-12meta: Fix Upstream-Status statementsRoss Burton2
Fix a variety of problems such as typos, bad punctuations, or incorrect Upstream-Status values. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-12kexec-tools: Pass -r directly to linkerKhem Raj2
-r is understood by gcc but not by clang, anyway its a linker option so pass it straight to linker by using -Wl explicitly Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-12latencytop: Fix build with clangKhem Raj2
Clang is stricter with syntax checking and flags the functions return values if they dont match with function signatures, Fixed thusly Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-12perf: fix the install-python_extRoy Li1
1. $(grep xxx xxx) never returns 0, it maybe return empty or string, and can not compare with 0, this fixes that python module never are installed. 2. python library is installed into /usr/lib/ by default, but we expect it is installed into ${libdir}, so add --install-lib parameter for python setup.py to set the library dir; this fixes not shipped warning, since python modules are installed into /usr/lib/, but FILE_${PN}-python expects it is under ${libdir}, which is /usr/lib64/ for 64bit machine 3. the makefile target install-python_ext is moved from Makefile to Makefile.perf from linux v3.13, so match install-python_ext in Makefile.* and --root='/\$(DESTDIR_SQ)' before linux v3.13 will install the target python library to native sysroot, so replace it with --prefix as after linux 3.13; this fixes not shipped warning, and install target files to native dir, like below: ERROR: QA Issue: perf: Files/directories were installed but not shipped in any package: /home /home/pokybuild /home/pokybuild/yocto-autobuilder /home/pokybuild/yocto-autobuilder/yocto-worker /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr/lib /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7 /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages/perf.so /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages/perf-0.1-py2.7.egg-info Signed-off-by: Roy Li <rongqing.li@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-09linux-yocto/3.14: fix edgerouter (octeon) buildBruce Ashfield3
Upating the SRCREVs to import the following commit: Author: Kevin Hao <kexin.hao@windriver.com> Date: Mon Aug 31 19:34:48 2015 +0800 mips: octeon: use ll/sc for the atomic ops for all the predecessor of octeon2 Even the octeon plus has the support of the 'saa' instruction, but we don't have a way to distinguish between octeon and octeon plus at compile time and pass "-march=octeon" to all the predecessor of octeon2. So it will cause the following error when trying to assemble the "saa" instruction with option "-march=octeon": {standard input}: Assembler messages: {standard input}:360: Error: Unrecognized opcode `saa $2,($4)' scripts/Makefile.build:308: recipe for target 'arch/mips/cavium-octeon/executive/cvmx-lap.o' failed Forcing to use the "ll/sc" for the atomic ops for all the predecessor of octeon2 to fix this issue. Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-06oprofileui: Use inherit gettextSaul Wold1
oprofileui uses gettext during the configuration task so should be inherit gettext. This issue appears when an older version of gettext is used do to pinning to the older non-gplv3 version. [YOCTO #7795] Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-30linux-yocto-3.14: Use a revision thats on the branch for qemuppcRichard Purdie1
At a guess, Bruce's scripts have mixed up the -rt and on -rt versions of the qemuppc branches. Set this to a revision on the standard/qemuppc branch. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-30linux-yocto/3.14/4.1: fix ARM boot with gcc 5.xBruce Ashfield4
Booting qemuarm when the kernel was built with gcc 5.x would result in a boot hang (or at least no visible output). Updating the SRCREVs for the following change: Author: Jianchuan Wang Email: jianchuan.wang@windriver.com Subject: Omit to optimize vsprintf.c/kasprintf.c Date: Wed, 26 Aug 2015 13:54:57 +0800 Add "-O0" for vsprintf.c/kasprintf.c Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com> While this may not be the final fix (it still has to go usptream and be better explained), it gets us booting, so is good enough for the time being. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-30linux-yocto-dev: update to 4.2-rcBruce Ashfield1
The -dev kernel is now tracking 4.2 content, so we update the linux-yocto-dev recipes PV to match. (From OE-Core rev: fc22f6ee38731e60b2bc15640fa697e5af663422) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-30linux-yocto/4.1: CIRRUS config and quark thermal supportBruce Ashfield3
Updating the meta SRCREVs for the following changes: 92977854ff52 graphics: disable CIRRUS DRM for qemumips and qemuppc 57f4dc4dfe16 intel-quark: Enable thermal support (From OE-Core rev: 5c9d414fc8e88cd5ef8e7e530ba4c5e788e03bb7) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-30linux-yocto/4.1: enable DRM_CIRRUS_QEMU and EXT4_USE_FOR_EXT23Bruce Ashfield3
Updating the meta SRCREV to enable cirrus graphics emulation and wider compatibility for the ext4 driver. [YOCTO: #7348] [YOCTO: #6667] (From OE-Core rev: 530c51e5354d5cd233b7015a3d0dfe94cb9cbaa1) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-30linux-yocto/4.1: update to v4.1.6 and v4.1.6-rt5Bruce Ashfield3
Bumping the SRCREVs to import the latest 4.1-stable and 4.1-rt changes. (From OE-Core rev: 21fd4093bbd0177453a1e749d825cf510746f201) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-30linux-yocto/3.14: cleanups and gcc5 ARM build fixesBruce Ashfield3
Updating the 3.14 SRCREVs to match the latest kernel meta data updates and also to merge four patches Richard Purdie located that fix the gcc 5.x ARM build (we still have boot issues, but building is the first step). (From OE-Core rev: 24a888ddd04e44f8a069364bfbde06871ad33ae8) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-30linux-yocto/4.1: quark configuration and thermal supportBruce Ashfield3
Updating the 4.1 SRECREVs to reflect the following changes: 74159a303c21 thermal: intel Quark SoC X1000 DTS thermal driver 833214b33303 intel-quark-tiny: Add tiny KTYPE .scc file 45ecab18d462 amd.cfg: Add X86_AMD_PLAFORM_DEVICE to default 9a31d2cbc251 intel-quark-standard: add mass storage and boot live support 4ea43922558a bsp: add coretemp to intel-common-drivers (From OE-Core rev: e1aa475dd362d3545911b0677404ced644e394eb) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-30linux-yocto/3.19/4.1: add coretemp to intel-common-driversBruce Ashfield5
Updating the 3.19 and 4.1 meta SRCREVs to pull in the coretemp configuration values. Partial fix for [YOCTO #8107]. (From OE-Core rev: 4511961afca854d8006c0d058f46f8ba46f277c4) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-30linux-yocto/4.1: fix qemuarm preempt-rt configurationBruce Ashfield1
With the recent changes to the kernel meta data handling and the removal of BSP branches, we need to shuffle some patches around to match. This prevents patches from being applied twice, and the qemuarm BSP can be configured for preempt-rt. [YOCTO: #8122] (From OE-Core rev: b6b7a80440521a8e82cfe6c56dddedf061de6208) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-30oprofile: 1.0.0 -> 1.1.0Robert Yang4
* Remove backport patch filemode-fix.patch. * Update --with-kernel=${STAGING_DIR_HOST}/${prefix} to find kernel headers (linux/*.h) to fix the error: | checking kernel supports perf_events... unknown -- perf_event.h not found | ERROR: You requested to build oprofile with '--with-kernel=/buildarea/lyang1/test_f2/tmp/work-shared/qemux86/kernel-source', | but headers were not accessible at the given location. | Be sure you have run the following command from within your kernel source tree: | make headers_install INSTALL_HDR_PATH=<kernel-hdrs-install-dir> | Then pass <kernel-hdrs-install-dir> to oprofile's '--with-kernel' configure option. | configure: error: Unable to build oprofile. Exiting. (From OE-Core rev: b2200152deef0aec3cd8fe55bb73d6e8fccfe159) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-16libpfm4: Fix GNU_HASH warning.Noor2
* Add a patch which updated add LDFLAGS variable to SLDFLAGS in Makefile. Signed-off-by: Noor Ahsan <noor_ahsan@mentor.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-08-12perf: fix build breakage on kernels after 4.1Reinette Chatre1
A recent commit fixed perf build failures with a change that duplicates a fix that can be found in kernels after 4.1. Unfortunately there is a conflict between these two fixes and we see perf build failures when building perf in kernels that contain the fix already. The problem is that the fix from the recipe modifies the location of .config-detected to $(OUTPUT).config-detected. In a 4.2 kernel the location will be changed to $(OUTPUT)$(OUTPUT).config-detected. We change the recipe to require a space in the pattern to only change kernel sources that do not already place file in $(OUTPUT). The recent commit that introduced the build failure is: commit ea9016b60b47138bc58d84a06954b44527b20a19 Author: Richard Purdie <richard.purdie@linuxfoundation.org> Date: Sat Jul 25 14:37:58 2015 +0100 perf: Fix config file conflict with 4.1 kernels If you setup mutlitlibs and then: bitbake perf libb32-perf bitbake perf libb32-perf -c cleansstate bitbake perf libb32-perf you will see races where the two builds get confused about which directory they should be using and they corrupt each other. The issue is that .config-detected is created in ${S}, not $(OUTPUT). We can fix this by moving the file to $(OUTPUT). [YCOTO #8043] (From OE-Core rev: 00608cffffb586e8d2a2075117e710113c471448) (From OE-Core rev: 57df1ebd910e42af47a0039830a60f41a3bd29b6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> The commit in the kernel source that fixes the problem from kernel side is: commit 642273795fa81da11290ffa90bce6ff242f2a7bb Author: Aaro Koskinen <aaro.koskinen@nokia.com> Date: Wed Jul 1 14:54:42 2015 +0300 perf tools: Create config.detected into OUTPUT directory Create config.detected into OUTPUT directory instead of source directory. This fixes parallel builds that share the same source directory. Signed-off-by: Aaro Koskinen <aaro.koskinen@nokia.com> Acked-by: Jiri Olsa <jolsa@kernel.org> Cc: Paul Mackerras <paulus@samba.org> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> Link: http://lkml.kernel.org/r/1435751683-18500-1-git-send-email-aaro.koskinen@nokia.com Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com> Signed-off-by: Reinette Chatre <reinette.chatre@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-09oprofile: reorder SRC_URI lines to fix upstream version checkAlexander Kanavin2
The source tarball should be listed first. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-01kexec-tools: 2.0.9 -> 2.0.10Richard Purdie6
Drop patch merged upstream and part of x32 patch merged upstream. Refresh patches. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-07-31perf: add liblzma depdenencyBruce Ashfield1
With kernel commit 6c6f0f6164f [tools build: Add feature check for lzma library], perf now performs a test for lzma and adds functionality appropriately. This currently is a floating dependency that will sometimes be present, and sometimes not. The result is the following QA warning: WARNING: QA Issue: perf rdepends on liblzma, but it isn't a build dependency? [build-deps] By adding xz to the DEPENDS, we'll ensure that it is consistently in place. [YOCTO: #8045] Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-07-31linux-firmware: upgrade to commit 75cc3ef8ba6712fd72c073b17a790282136cc743Cristian Iorga1
- Intel copyright years changed; - Advanced Micro Devices copyright years changed; Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-07-25linux-yocto: introduce 4.1 versioned recipesBruce Ashfield3
Updating the linux-yocto kernel recipes to include a named/versioned 4.1 recipe. This will be the LTSI kernel, and the 3.14 and 3.19 kernels will be removed in subsequent commites (once reference boards have transitioned). Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-07-25kern-tools: standalone tree configurationBruce Ashfield1
Updating the kern-tools SRCREV to import the following changes: cbd4b7102668 patchme/updateme: unify meta directory handling b65075997152 configme: standalone operation The change of note is [configme: standalone operation], which makes the kernel configuration script free from dependencies on other parts of the kern-tools. With this change, we set the stage to extend kernel configuration fragments and auditing to arbitrary trees. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-07-25linux-yocto: split meta data from kernel repositoryBruce Ashfield6
The linux-yocto tree has always been a combined set of kernel changes and configuration (meta) data carried in a single tree. While this format is effective at keeping kernel configuration and source modifications synchronized, it isn't always obvious to developers on how to manipulate the meta data versus the source. With this change, we remove the meta data processing from the kernel-yocto class and use the external meta-data repository that has always been used to seed the linux-yocto meta branch. After this change, linux-yocto can no longer process combined trees, and is simplified as a result. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-07-25perf: Fix config file conflict with 4.1 kernelsRichard Purdie1
If you setup mutlitlibs and then: bitbake perf libb32-perf bitbake perf libb32-perf -c cleansstate bitbake perf libb32-perf you will see races where the two builds get confused about which directory they should be using and they corrupt each other. The issue is that .config-detected is created in ${S}, not $(OUTPUT). We can fix this by moving the file to $(OUTPUT). [YCOTO #8043] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-07-23linux-libc-headers: update to 4.1Bruce Ashfield3
Updating the libc-headers to match the 4.1 LTSI kernel version. We also tweak the logic in linux-libc-headers.inc to look in the 4.x subdirectory if a 4.x kernel is specified as the header source. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3 (git 2.25.1) at 2025-02-28 20:17:20 +0000