aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-kernel
AgeCommit message (Collapse)Author
2013-12-03kern-tools: use dylan branchBruce Ashfield
This switches the kern-tools to use the matched dylan branch that is maintained to work against the dylan release of yocto/oe-core. As part of this switch, we also update the SRCREV to match the latest fixes for the dylan kernel-tools. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2013-08-16systemtap: inherit pkgconfigMartin Jansa
* systemtap-native was failing with undefined AC_DEFINE configure.ac:56: error: possibly undefined macro: AC_DEFINE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. (From OE-Core master rev: 8026d9f84c6af3996ada906d39ff1e7a986a9b5a) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-07-08linux-firmware: Look for RTL license in the right directoryDarren Hart
The rtl-license package FILES was pointing to the wrong directory as it was removed from there in commit: acd3735 linux-firmware: Remove duplicaed license from rtlwifi subdir This resulted in a do_rootfs failure for core-image-sato-sdk for fri2 with ipk when the linux-firmware-dev package tried to install linux-firmware-rtl-license which wasn't created as it was empty. Tested on core-image-sato-sdk build for fri2 on dylan commit: 789b2b7e0cca404ff8ba8ed5ba823d215e6ba5b4 Cc: Saul Wold <sgw@linux.intel.com> Cc: Beth Flanagan <elizabeth.flanagan@intel.com> Cc: Otavio Salvador <otavio@ossystems.com.br> (From OE-Core master rev: fc7fafcb3bb5c12bad07e12c15ac3a489bd0291f) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-22kern-tools: refresh and make dash compliantBruce Ashfield
The separately packaged merge_config.sh in the kern-tools package was missing upstream fixes, and in particular a change that ensures it is dash compatible. By grabbing that upstream commit and rebasing the existing patches on top of the new baseline, we are up to date and working on systems where /bin/sh is dash. [YOCTO #4473] Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-05-20linux-yocto/3.8: udpate to v3.8.11Bruce Ashfield
Update the linux-yocto-3.8 SRCREVs to the korg 3.8.11 -stable release. (From OE-Core master rev: b60d04331f84e06fae6c074acab045c3e003929b) 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>
2013-05-20linux-yocto/3.4: update to v3.4.43, ltsi-65311d8 and v3.4.42-rt56Bruce Ashfield
Updating the 3.4 kernel trees to the latest korg, LTSI and -rt stable releases. (From OE-Core master rev: 98446039e210936a32e70559a379131e8e0d832f) 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>
2013-05-20kern-tools: anchor and delimit regexsBruce Ashfield
Updating the kern-tools SRCREV with the following fix: Updateme is responsible for updating an existing meta-series with new patches, configs and tree manipulations. To do this, it first checks for an existing board description and generates one if required. It then searches for features and fragments to be applied for the tree. There were two problems: - A top level board description is detected via the presence of "define" directives that indicate the board name, the arch and kernel type. The test for define would match on patches or fragments with 'define' in their name, and would incorrectly use that file as the top level board description. This is fixed by ensuring that only defines at the start of a line, or preceded by whitepace match. - When searching for features that were indicated as 'addon' or 'optional', the search would find, and apply, any feature with the passed name as substring versus an exact match. This is fixed by ensuring that the matched feature name is /<feature name> versus <feature name> (From OE-Core master rev: 57ae1e412a35d827f84bf9b1f48747bf703f84b7) 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>
2013-05-20linux-yocto/3.4: iwlwifi, ext4, brtfs warning and -rt fixesBruce Ashfield
Updating the yocto 3.4 SRCREVs for the following fixes: 206d4bb powerpc/perf: run irq-work under softirq context in rt 8a969f9 arm/perf: run irq-work under softirq context in rt 79ba946 iwlwifi: fix unused variable warning 59d93fa ext4: remove unused variable in ext4_update_super() 2385eee Btrfs: fix compile warnings in extent_io.c (From OE-Core master rev: 96113b28031583af1dd42fe7660a9d5ced36d1b6) 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>
2013-05-09powertop: inherit gettextRoss Burton
powertop uses gettext during config time and at build time to generate the messages, so really should inherit gettext. [YOCTO #4470] Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-08qemux86: disable paravirt guest in linux 3.4, causes test failuresRoss Burton
The shutdown sanity test that we previously saw on qemux86-64 in 2.6.37 have started to re-appear reproducably on qemux86 in 3.4 in the Danny series. Until this can be root-caused and fixed in the kernel, disable paravirtualisation across all kernels and all qemu machines. [ YOCTO #4196 ] Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-18perf: Ensure license is handled correctlyRichard Purdie
The do_populate_lic task has a race with the recipe since it relies on the kernel being populated in the sysroot. This patch adds in the explicit missing dependency. [YOCTO #3534] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-16linux-yocto/3.8: Makefile: add -grecord-gcc-switches if using -mfentryBruce Ashfield
Commit a2546fae [ftrace: Add -mfentry to Makefile on function tracer] adds support for using -mfentry when possible, whenever the ftrace CONFIG_FUNCTION_TRACER option is enabled. This unfortunately causes bogus dwarf debuginfo to be generated: gcc Bug 54793 - the location of a formal_parameter is not started from a function entry with -mfentry http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54793 This can be fixed by applying the gcc patch above, which will be present in gcc-4.8, but in the meantime, the problem is currently being worked around in different ways by various tools. One of those tools that we support in Yocto, Systemtap, requires the DW_AT_producer string contain -mfentry, which means that it's assuming record-gcc-switches is also used: SystemTap Bug 15123 - workaround for bad debuginfo for -mfentry http://sourceware.org/bugzilla/show_bug.cgi?id=15123 The lack of -grecord-gcc-switches and therefore a missing -mfentry string in Yocto leads to the following Yocto bug: Bug 4099 - Crosstap script check fails https://bugzilla.yoctoproject.org/show_bug.cgi?id=4099 Which is what this patch intends to fix. It only affects architectures that HAVE_FENTRY when CONFIG_FUNCTION_TRACER is turned on and in any case is just adding to the debuginfo, so there doesn't seem to be much risk to adding it. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-15kern-tools: fix custom repository BSP generationBruce Ashfield
Updating the SCRCREV to pick up the following fix updateme: use absolute path for generated BSP descriptions When a custom BSP is used, a top level BSP is generated by the tools and fed to the build system just as a user defined BSP would be located and passed. The location of the generated file is placed in the top_tgt file, which is used by subsequent stages. A relative path was being placed into top_tgt, which binds the build to a particular directory structure and working directory. The location of parts of the build have changed, and this relative path is no longer accurate. Changing it to an absolute path solve the build issues related to custom BSPs. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-12oprofile: Add Upstream-Status and description to patchRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-12kern-tools: fix non-local patch/config locationBruce Ashfield
A regression was introduced when implementing the ability to restrict configuration values via include directives. Only patch and config files that were local to a feature directory could be found. While this doesn't impact most users of the tools, it is an issue that needs to be fixed. Additionally, the regex that detected flags passed to includes was not specific enough, and unfortunately named feature files would match. This resulted in features like standard-nocfg.scc inhibiting all configuration items, even base configs. This change also bumps the linux-yocto 3.4 and 3.8 PR values to ensure that kernels will be rebuilt once this change is active. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-11kern-tools: fix conditional configuration itemsBruce Ashfield
Variables defined in .scc files have two purposes: - Documentation in the meta-series - Variables that can be tested in sub sections and other features The second part of this functionality was broken when fixing configuration for tiny/small systems. As a result, arch tests were failing and configs were dropped. This restores the existing functionality. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-11linux-yocto/3.8: qemumips boot fixes and netfilter kernel featuresBruce Ashfield
Updating the linux-yocto-3.8 recipes to fix two issues: 1) qemumips boot This is fixed by: Revert "Input: i8042-io - fix up region handling on MIPS" And by disabling ftrace for qemumips boards 2) netfilter options being dropped When KERNEL_EXTRA_FEATURES was introduced, and allowed to be inhibited, the variable was only applied to qemux86 machines. It should be applied ot all machine types (unless inhibited), so we restore that functionality. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10linux-yocto/3.8: qemumips graphical bootBruce Ashfield
Updating the meta SRCREV to fix and illegal instruction that is seen when launching X with USB pointing devices. meta/qemumips: build USB_UHCI_HCD into the kernel When booting qemumips and USB_UHCI_HCD built as a module, the following trace is seen, and then prevents X from starting: qemumips user.warn kernel: Call Trace: qemumips user.warn kernel: [<c0028000>] uhci_check_bandwidth+0x0/0x160 [uhci_hcd] qemumips user.warn kernel: [<c002e08c>] uhci_urb_enqueue+0xba4/0xc48 [uhci_hcd] qemumips user.warn kernel: [<8058092c>] usb_hcd_submit_urb+0xdc/0x848 qemumips user.warn kernel: [<805b8fbc>] wacom_open+0x44/0x8c qemumips user.warn kernel: [<805a1990>] input_open_device+0xac/0xec qemumips user.warn kernel: [<805a8cec>] evdev_open+0x188/0x1bc qemumips user.warn kernel: [<802331d8>] chrdev_open+0xc8/0x1c4 qemumips user.warn kernel: [<8022b338>] do_dentry_open+0x248/0x2e4 qemumips user.warn kernel: [<8022b418>] finish_open+0x44/0x68 qemumips user.warn kernel: [<8023e51c>] do_last.isra.29+0x2c0/0xcbc qemumips user.warn kernel: [<8023efd8>] path_openat+0xc0/0x52c qemumips user.warn kernel: [<8023f840>] do_filp_open+0x4c/0xbc qemumips user.warn kernel: [<8022cc3c>] do_sys_open+0x128/0x20c qemumips user.warn kernel: [<8010c07c>] stack_done+0x20/0x44 qemumips user.warn kernel: Code: (Bad address in epc) qemumips user.warn kernel: ---[ end trace 8a48c6046870f8c2 ]--- Building the module into the kernel fixes the problem, but the root cause is still under investigation. The pipelines around jumps to module addresses seem to be triggering invalid instructions. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10linux-yocto/3.8: aufs, config processing, tiny, mips boot fixesBruce Ashfield
Updating the SRCREVs to fix a number of bugs, boot issues and ktype support additions. standard/*: Aufs support was misplaced on the move from the -dev to release kernel, this commit restores the support. This is not active unless the aufs configuration items are enabled via the aufs-enable.scc feature. 11998bd aufs: core support f2ea9f4 aufs: standalone support bf529b6 aufs: aufs proc_map b6f0a04 aufs: aufs base support 55b0bc2 aufs: kbuild patch meta: The meta branch has updates for aufs enablement, tiny BSP configs, preempt-rt fixes and a wifi config audit fix. 4c567e0 meta/aufs: add -enable feature and patches 059fe88 meta/aufs: create aufs configuration fragment 7d672cd0 meta: add fri2 tiny BSP config. mti-malta32: This fixes the graphical boot of qemumips, the offending commit is breaking dynamic patching of ftrace on the simulation, so we revert the commit for now. 18c71ab Revert "ftrace/x86: Have x86 ftrace use the ftrace_modify_all_code()" mti-malta64: This enables the boot of qemumips64 by reverting the broken ftrace support for mips64 and by stubbing out inavlid oprofile register writes. 0ec615c Revert "ftrace/x86: Have x86 ftrace use the ftrace_modify_all_code()" bbefde3 oprofile/mips: do not set perf_irq for qemu mips 64 eb6cb79 Revert "MIPS: Function tracer: Fix broken function tracing" [YOCTO #4052] [YOCTO #4129] [YOCTO #2410] Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10kern-tools: fix excluded configuration processingBruce Ashfield
One of the features introduced early on in the 1.4 release cycle was the ability to include a kernel feature, but only get its patches and not configs (and vice versa). As it turns out, this only was exercised recently and once a single include with dropped configs was started, ALL configuration values following the commit were dropped. To fix the problem, the processing of kernel features has been split into two. Where the features are preprocessed and the assembled/complete file is used to generate the meta-series (which is later applied to the tree). The logic of the tools is the same, but the two phases of processing allows configuration values to be excluded properly and simply, while keeping the logic for modifying the tree in a separate step. All changes are invisible to the user, and are done within the existing scripts and build system bindings. Output series and manipulations to the tree are the same as they were before this change. Updating the kern-tools SRCREV to pickup the kern-tools changes for this. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10linux-yocto/3.8: atom-pc: Update atom-pc-preempt-rt.scc to reuse config from ↵Bruce Ashfield
common-pc Updating the meta branch SRCREV to pick up the following change: The atom-pc preempt-rt BSP was omitting the config from common-pc, resulting in very few drivers being built, including USB_STORAGE, preventing preliminary boot testing. Remove the "standard features" as those are covered by the common-pc scc files. 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>
2013-04-10linux-yocto/3.8: fix atom-pc config audit warningsBruce Ashfield
The atom-pc was referencing some invalid and unecessary config options that are causing kernel config audit warnings. With this SRCREV update, the configuration is clean against the 3.8 kernel. [YOCTO #3490] Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10linux/yocto: update AUTOFS configurationBruce Ashfield
When systemd is enabled, qemumips failed to boot with the following trace: Reserved instruction in kernel code[#1]: Cpu 0 $ 0 : 00000000 80232500 c0011000 80000000 $ 4 : c0017440 00000000 87032400 8704b000 $ 8 : 00000000 00000000 00000010 003fffff $12 : 00000000 7fafbab4 00000000 87d6fbb0 $16 : 87f98780 c0017440 c0017440 00000000 $20 : 8704a000 00000000 8704a000 00000000 $24 : 00000010 80480630 $28 : 87c22000 87c23e28 7fafbc00 80232408 Hi : 00000000 Lo : 00000000 epc : c0011000 autofs_mount+0x0/0x30 [autofs4] Not tainted ra : 80232408 mount_fs+0x68/0x200 Status: 1000a403 KERNEL EXL IE Cause : d0808028 PrId : 00019300 (MIPS 24Kc) Modules linked in: autofs4 Process systemd (pid: 1, threadinfo=87c22000, task=87c28000, tls=77787490) Stack : 809b3e28 802512bc 00000000 808b0da4 87f3d310 87936c38 87032400 8704b000 87f98780 c0017440 00000020 8704b000 87032400 87032480 00000000 80251a2c 00000006 8022f7fc 87032480 802507f0 00000000 87032400 8704b000 7fafba94 00000000 c0017440 8088275c 80253f40 7fafb9d0 00000016 38513fac 0051b2a8 8704b000 801df604 00000000 0000000a 87f5c000 801f5968 87f3d310 87936c38 ... Call Trace: [<c0011000>] autofs_mount+0x0/0x30 [autofs4] [<80232408>] mount_fs+0x68/0x200 [<80251a2c>] vfs_kern_mount+0x68/0x114 [<80253f40>] do_mount+0x218/0x9d0 [<8025479c>] sys_mount+0xa4/0xec [<8010c07c>] stack_done+0x20/0x44 The policy of building AUTOFS as a module is something that can be changed, since boot processes that use automounting can take advantage of the built in support to reduce complexity. The size increase of the base policy is small with this change, and users of the linux-yocto kernel can still override this value, which is exactly what the poky-tiny kernel does. Keeping the configuration consistent for all boards, and not adding and exception for qemumips makes sense in this case. [YOCTO #4129] Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-05linux-yocto-tiny: Add 3.8.4 recipeDarren Hart
Bring linux-yocto-tiny up to the latest linux-yocto 3.8.4 version. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-05linux-firmware: make the main package depend on all sub-packagesRoss Burton
Whilst splitting out specific large firmware blobs is a good move for space saving, it makes installing "all the firmware" tricky. Make linux-firmware depend on all of the separated packages so that installing that pulls in all of the sub-packages. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-04linux-dtb: fix whitespace in bash functionsChase Maupin
* Fix the whitespace in the base functions to use TAB instead of spaces. This is to address feedback from: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Chase Maupin <Chase.Maupin@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-04linux-dtb: Add simple DTB symlinks for devicetreeChase Maupin
* This is similar to the symlinks provided for the kernel image in the /boot directory of a file system. The goal is to have simply named symlinks in /boot that mirror the device tree name in the kernel sources. This is so that programs like U-Boot can easily find the default device tree binary in the /boot directory and use that when booting the kernel. * Use update-alternatives to handle proper creation and removal of the symlinks. Signed-off-by: Chase Maupin <Chase.Maupin@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-02linux-firmware: Add missing license information for wl12xxOtavio Salvador
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-02linux-firmware: Package vt6656, ath6k, ath9k and ar9170Otavio Salvador
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-02linux-firmware: Package Reaktek and Broadcom licensesOtavio Salvador
The licenses need to be included onto rootfs so we have a new package for license file when we have multiple packages for same vendor. This patch does this change for current packages in this specific case. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-02linux-firmware: Remove duplicaed license from rtlwifi subdirOtavio Salvador
The rtlwifi will is deployed onto /lib/firmware so we don't need to duplicate it inside of rtlwifi subdir. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-02linux-firmware: Remove 'Makefile' from packagesOtavio Salvador
The 'Makefile' should not be deployed in the packages as it is of no use for target and end user. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-02linux-yocto-rt: integrate 3.8.4-rt2Bruce Ashfield
Updating to 3.8.4-rt2 to fix the minor issues found with -rt1. >From the upstream commit log: changes since v3.8.4-rt1: - build fix for i915 (reported by "Luis Claudio R. Goncalves") - build fix for fscache (reported by tglx) - build fix for !RT (kernel/softirq.c did not compile) - per-cpu rwsem fixed for RT (required only by uprobes so far) - slub: delay the execution of the ->ctor() hook for newly created objects. This lowers the worst case latencies. Known issues: - SLxB is broken on PowerPC. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-02linux-yocto/3.8: update mips SA_RESTORER fixBruce Ashfield
During the 3.8.4 integration there was a build issue on MIPS due to SA_RESTORER changes. A solution was put in place for mips, but it didn't cover other impacted architectures. This is a backport of the proposed fix for the next 3.8-stable, since the full -stable might not be available in the right timeframe. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-26linux-yocto/3.8: qemuarm boot fixBruce Ashfield
The preempt-rt kernel was wasn't inheriting the standard kernel configuration and hence was not able to boot on qemuarm due to missing ABI options. Changing the main preempt-rt kernel include to inherit standard configuration again fixes this boot issue. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-26linux-yocto/3.8: fix perf host contaminationBruce Ashfield
Updating the 3.8 SRCREVs with the following fix: libtraceevent: Remove hard coded include to /usr/local/include in Makefile commit b9e8c37220c80e78289a1e87b50c09418eb59a7e upstream having /usr/local/include hardcoded into the makefile is not necessary as this is automatically included by GCC. It also infects cross-compile builds with the host systems includes. Signed-off-by: Jack Mitchell Acked-by: Namhyung Kim Cc: Ingo Molnar Cc: Paul Mackerras Cc: Peter Zijlstra Link: http://lkml.kernel.org/r/1362741712-21308-1-git-send-email-ml@communistcode.co.uk Signed-off-by: Arnaldo Carvalho de Melo This implements the fix I described in Yocto [BUG #3993][perf using host includes], now upstream. Integrated-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> [YOCTO #3993] Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-26linux-yocto/3.4: import v3.4.36 -stable fixesBruce Ashfield
Updating the 3.4 tree to import the korg -stable fixes for v3.4.36. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-26kern-tools: initialization and meta branch fixesBruce Ashfield
Bumping the kern-tools SRCREV to pickup the following fixes and documentation updates: d484e3f kgit-meta: remove hardcoded meta directory name affad20 yocto-kernel-tools: Typoes, "fragement", "depreciated" 142ed49 kgit-init: update tools list Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-26linux-yocto/3.8: introduce v3.8.4-rt1Bruce Ashfield
The -rt series has been updated for the 3.8 kernel. Updating the SRCREVs to reflet its import into the tree. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-26linux/yocto-3.4: update to v3.8.4Bruce Ashfield
Updating the base v3.8 kernel to the 3.8.4 -stable version. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-26linux-yocto/3.8: allow kernel feature _appends to be overridenBruce Ashfield
It was pointed out that the current way the KERNEL_FEATURES variable is appended in the base linux-yocto recipe doesn't allow the appended features to be prevented in a layer without using python code and a recipe finalize hook. To allow easier overriding of 'extra' or 'optional' features that are defined in the linux-yocto recipe, we create a KERNEL_EXTRA_FEATURES variable. This variable can be set in a layer to define extra features or cleared to prevent the recipe's extra features from being appended to the core functionality. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-25lttng: babeltrace: Update to upstream version 1.1.0Maxin B. John
Also updated the BUGTRACKER Signed-off-by: Maxin B. John <maxin.john@enea.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-23linux-firmware: Package Broadcom firmwaresOtavio Salvador
Adds specific packages for bcm4329, bcm4330 and bcm4334, including handling of symbolic link for the needed firmware filename. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-22babeltrace: Fix case where ${B} != ${S}Richard Purdie
Autotools need to run in ${S}. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-19perf: Fix parsing errorRichard Purdie
Due to the use of ${@...} the code will try and expand this when performing the initial parsing. If the sysroot doesn't exist with an existing kernel, this will fail at parsing time. Sinec we're already in python, just remove the ${@....} wrapping and then we execute at do_package time which is what we want. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-19perf: make PKGV match kernel versionTom Zanussi
Have perf grab and use the kernel version it's built from for PKGV, rather than the default perf recipe version, so the final packages get the kernel version instead of the default 1.0, which represents a backwards value from the previous recipe. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-18lttng-ust: remove the COMPATIBLE_HOST checkMaxin B. John
liburcu-0.7.6 supports MIPS. So, we can remove the COMPATIBLE_HOST check intended for MIPS. Signed-off-by: Maxin B. John <maxin.john@enea.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-18babeltrace: remove the COMPATIBLE_HOST checkMaxin B. John
liburcu-0.7.6 supports MIPS. So, we can remove the COMPATIBLE_HOST check intended for MIPS. Signed-off-by: Maxin B. John <maxin.john@enea.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-18lttng-tools: remove the COMPATIBLE_HOST checkMaxin B. John
liburcu-0.7.6 supports MIPS. So, we can remove the COMPATIBLE_HOST check intended for MIPS. Signed-off-by: Maxin B. John <maxin.john@enea.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-18lttng-modules: remove the COMPATIBLE_HOST checkMaxin B. John
liburcu-0.7.6 supports MIPS. So, we can remove the COMPATIBLE_HOST check intended for MIPS. Signed-off-by: Maxin B. John <maxin.john@enea.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-28 09:30:10 +0000