summaryrefslogtreecommitdiff
path: root/meta/recipes-kernel/linux
AgeCommit message (Collapse)AuthorFiles
2013-08-26linux-yocto: introduce v3.10Bruce Ashfield3
Introduce the 3.10 kernel. This is based on the 3.10.9 upstream kernel and replaces the 3.8 recipes, which will be removed once all reference boards have been updated. 3.10 also the latest LTSI and will be updated with that content when it becomes available. Other features of the 3.10 kernel include: - refreshed -rt support - refreshed yaffs2, aufs3 - cryptodev - bfs, edf, and OCF staged features - scrubbed and updated meta data for v3.10 - improved tools support for meta data updates and queue maintenance - patch carry forward from all previous linux-yocto kernels and configuration. This kernel has been built and boot tested on all qemu machines and architectures. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-20linux-dtb.inc: Fix dtb generation for kernels newer than 3.8Otavio Salvador1
The 3.8 kernel has change the default directory where the dtb file is stored. The change has been done at: ,----[ Quote of 3.8 kernel change ] | commit 499cd8298628eeabf0eb5eb6525d4faa0eec80d8 | Author: Grant Likely <grant.likely@secretlab.ca> | Date: Tue Nov 27 16:29:11 2012 -0700 | | ARM: dt: change .dtb build rules to build in dts directory | | The current rules have the .dtb files build in a different directory | from the .dts files. The only reason for this is that it was what | PowerPC has done historically. This patch changes ARM to use the generic | dtb rule which builds .dtb files in the same directory as the source .dts. | | Cc: Russell King <linux@arm.linux.org.uk> | Cc: Arnd Bergmann <arnd@arndb.de> | Acked-by: Olof Johansson <olof@lixom.net> | Cc: linux-arm-kernel@lists.infradead.org | Signed-off-by: Grant Likely <grant.likely@secretlab.ca> | [swarren: added rm command for old stale .dtb files] | Signed-off-by: Stephen Warren <swarren@nvidia.com> | Signed-off-by: Rob Herring <rob.herring@calxeda.com> `---- This change adds support for both places to backward and forward compatibility. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-08-19linux-yocto-3.8/meta: enable ALTIVEC for qemuppcBruce Ashfield3
As part of the qemuppc tuning activities, we are aligning on ppc74xx, and as a result we can enable ALTIVEC support in the base BSP config. [YOCTO #1914] Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-08-19linux-yocto-3.8/meta: update drm and intel power management settingsBruce Ashfield3
Updating the meta branch SRCREV to import the following config changes: f706bd4 drm-emgd.cfg: convert some config options from y to m 5995fa5 meta: features/power/intel.cfg Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-08-14linux-dtb: Use kernel build system to generate the dtb filesOtavio Salvador1
As the Linux kernel, unconditionally, builds the dtc application and it is the compatible version with the DeviceTree files shipped within the kernel it is better to use it and the kernel build system to generate the dtb files. Some DeviceTree files rely on CPP and kernel headers to be able to generate the dtb binary contents and it is harder to replicate it outside of Linux kernel build system so we /use/ it. To comply with these assumptions we need to use the dtb file when calling 'make' instead of pointing to the DeviceTree source file; the code has been made backward compatible but it is advised to move to the new definition to avoid warnings as: ,----[ Original definition ] | KERNEL_DEVICETREE = "${S}/arch/arm/boot/dts/imx6q-sabresd.dts" `---- Becomes: ,----[ New definition ] | KERNEL_DEVICETREE = "imx6q-sabresd.dtb" `---- Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-08-13linux-dtb.inc: Replace /boot/ with /${KERNEL_IMAGEDEST}/Mike Looijmans1
Devicetree files were installed hard-coded in /boot. When KERNEL_IMAGEDEST is anything else but "boot", the postinstall script and the file locations no longer match and the postinstall will fail. Replace "boot" with "${KERNEL_IMAGEDEST}" to fix this problem, and to allow the devicetree files to be installed in another location. Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-27linux-yocto/3.8: revert .gitignore: do not ignore meta directoryBruce Ashfield3
We made a change to allow meta branch/directory changes to be visible when working with the kernel tree. But without associated tool changes .gitignore is different between branches and hence causes errors when changing branches and processing the tree. The tools changes are not ready yet, so to avoid patching issues, temporarily reverting the change. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-18linux-yocto/3.8: restore qemumips64 SRCREVBruce Ashfield1
In commit 00e0ec6c [linux-yocto: v3.8.13 and v3.4.46], the qemumips64 SRCREV was inadvertently dropped. This patch restores the SRCREV and a booting qemumips64. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-18linux-yocto/3.4: mips: fix gcc 4.8 compilationBruce Ashfield3
Updating the SRCREVs to enable the following fix for gcc 4.8 mips compilation: Author: Steven J. Hill <sjhill@mips.com> Date: Fri Jul 6 21:56:01 2012 +0200 MIPS: Refactor 'clear_page' and 'copy_page' functions. Remove usage of the '__attribute__((alias("...")))' hack that aliased to integer arrays containing micro-assembled instructions. This hack breaks when building a microMIPS kernel. It also makes the code much easier to understand. [ralf@linux-mips.org: Added back export of the clear_page and copy_page symbols so certain modules will work again. Also fixed build with CONFIG_SIBYTE_DMA_PAGEOPS enabled.] Signed-off-by: Steven J. Hill <sjhill@mips.com> Cc: linux-mips@linux-mips.org Patchwork: https://patchwork.linux-mips.org/patch/3866/ Acked-by: David Daney <david.daney@cavium.com> Signed-off-by: Ralf Baechle <ralf@linux-mips.org> (cherry picked from commit c022630633624a75b3b58f43dd3c6cc896a56cff) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-18linux-yocto/3.8: update META srcrevBruce Ashfield3
Bumping the linux-yocto-3.8 meta branch SRCREV to pick up the following changes: 8ef9136 .gitignore: do not ignore meta directory f846f12 uvcvideo: a new config for a webcam device driver 02014ca v4l2: config fragment for enabling v4l2 interface to camera devices 71a5cc0 media-camera: a feature to enable camera infrastructure 2396656 drm-emgd.scc: remove config for non-existing driver aad8aa7 drm-emgd-1.18.scc: add a kernel feature for emgd-1.18 driver fcf81f8 meta: restore NAT Feature Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-09linux-yocto/3.4: update to v3.4.52Bruce Ashfield3
Updating the 3.4 kernel to the latest korg -stable release. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-27linux-yocto-dev: bump version to 3.10+Bruce Ashfield1
The linux-yocto-dev kernel is at 3.10-rcX, so we should bump the version to reflect reality. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-27linux-yocto/3.4: ltsi: sync to LTSI commit 5f05247edBruce Ashfield3
Updating the 3.4 branches to the latest LTSI baseline. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-27linux-yocto/3.8: add USB screen configuration and net sched optionsBruce Ashfield3
Bumping the meta branch SRCREV for the followiong commits: meta: enable additional NET_SCHED options This change turns on NET_ACT_MIRRED (packet redirecting and mirroring) and NET_CLS_U32 (universal 32bit comparisons w/ hashing classification). Signed-off-by: Michael Barabanov <michael.barabanov@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> meta: add BSP-specific touchscreen support Add touchscreen-composite support to machines based on common-pc and common-pc-64, along with several other Atom boards that don't inherit from those, thus providing those machines with the out-of-the-box ability to make use of the set of USB touchscreen devices supported by the composite USB driver. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> meta: add usb/touchscreen-composite feature Add support for the 'composite' USB touchscreen driver. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> meta: add features/input/touchscreen Add a feature enabling basic support for touchscreen input devices. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Michael Barabanov <michael.barabanov@windriver.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-27linux-yocto/3.4: allow kernel feature _appends to be overridenBruce Ashfield1
Updating the linux-yocto 3.4 recipe's feature flags to match the 3.8 recipe, which has the following change: 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: Saul Wold <sgw@linux.intel.com>
2013-06-24Sync with PRINC removal from meta-intelRichard Purdie2
PRINC usage is removed from meta-intel, bump core PR values to ensure no version regressions. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-18linux-yocto/3.8: fix gcc 4.8 ARM boot issuesBruce Ashfield3
Updating the linux-yocto-3.8 SRCREVs to fix a boot issue with ARM boards when gcc 4.8 is used. Without the following mainline backports: f200475 ARM: 7670/1: fix the memset fix 8215b0e ARM: 7668/1: fix memset-related crashes caused by recent GCC (4.7.2) optimizations The following trap will be seen on boot: [<c00fc3b8>] (kmem_cache_alloc_trace+0x54/0x210) from [<c039f074>] (con_insert_unipair+0xcc/0x11c) [<c039f074>] (con_insert_unipair+0xcc/0x11c) from [<c039fec8>] (con_set_default_unimap+0xfc/0x198) [<c039fec8>] (con_set_default_unimap+0xfc/0x198) from [<c07ee258>] (console_map_init+0x44/0x58) [<c07ee258>] (console_map_init+0x44/0x58) from [<c07ee738>] (vty_init+0x16c/0x1b0) [<c07ee738>] (vty_init+0x16c/0x1b0) from [<c07edb68>] (tty_init+0x108/0x148) [<c07edb68>] (tty_init+0x108/0x148) from [<c07eead0>] (chr_dev_init+0xb4/0xd8) [<c07eead0>] (chr_dev_init+0xb4/0xd8) from [<c0008a18>] (do_one_initcall+0x11c/0x18c) [<c0008a18>] (do_one_initcall+0x11c/0x18c) from [<c07d89d0>] (kernel_init_freeable+0x16c/0x254) [<c07d89d0>] (kernel_init_freeable+0x16c/0x254) from [<c05a3810>] (kernel_init+0x18/0x160) [<c05a3810>] (kernel_init+0x18/0x160) from [<c000e530>] (ret_from_fork+0x14/0x20) Code: e593a000 e35a0000 0a000020 e5943014 (e79a1003) ---[ end trace e6c62de166779f86 ]--- Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b Moderate stress and board testing shows the fix to hold, and it is good for broader testing. [YOCTO #4549] Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-31linux-yocto: remove 3.2 kernel recipesBruce Ashfield3
Moving forward we plan to support two kernels plus the development kernel. That leaves 3.2 as the next kernel to be dropped. Support for this version will be carried in the sustained/old releases. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-31linux-yocto: v3.8.13 and v3.4.46Bruce Ashfield6
Updating the -stable linux-yocto trees to the latest korg -stable releases. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-17linux-yocto/3.8: set qemumips64 SRCREVsBruce Ashfield1
When qemumips64 was enabled, its machine specific SRCREV was missed. Without it, qemumips64 builds from the wrong branch and we miss important oprofile/ftrace fixes that are required for boot. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-16linux-yocto: add qemumips64 compatibilityBruce Ashfield2
The 3.8 and linux-yocto-dev kernel trees carry qemumips64 support. Adding the board to the compatibility directly in the recipes is the first step to adding mips64 support to the broader set of packages. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-05-09classes/recipes/lib: Fix various python whitespace issuesRichard Purdie1
There are some left over tab characters in the python functions. This removes them and resolves python 3 errors. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-08linux-yocto/3.8: udpate to v3.8.11Bruce Ashfield3
Update the linux-yocto-3.8 SRCREVs to the korg 3.8.11 -stable release. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-05-08linux-yocto/3.4: update to v3.4.43, ltsi-65311d8 and v3.4.42-rt56Bruce Ashfield3
Updating the 3.4 kernel trees to the latest korg, LTSI and -rt stable releases. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-05-08linux-yocto/3.4: iwlwifi, ext4, brtfs warning and -rt fixesBruce Ashfield3
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 Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-05-08qemux86: disable paravirt guest in linux 3.4, causes test failuresRoss Burton1
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-16linux-yocto/3.8: Makefile: add -grecord-gcc-switches if using -mfentryBruce Ashfield3
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-12kern-tools: fix non-local patch/config locationBruce Ashfield6
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-11linux-yocto/3.8: qemumips boot fixes and netfilter kernel featuresBruce Ashfield3
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 Ashfield3
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 Ashfield3
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-10linux-yocto/3.8: atom-pc: Update atom-pc-preempt-rt.scc to reuse config from ↵Bruce Ashfield2
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 Ashfield2
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 Ashfield2
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 Hart1
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-04linux-dtb: fix whitespace in bash functionsChase Maupin1
* 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 Maupin1
* 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-yocto-rt: integrate 3.8.4-rt2Bruce Ashfield1
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 Ashfield2
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 Ashfield2
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 Ashfield2
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 Ashfield3
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-26linux-yocto/3.8: introduce v3.8.4-rt1Bruce Ashfield1
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 Ashfield1
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 Ashfield1
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-12linux-yocto/3.8: update EDF configurationBruce Ashfield1
The sched_deadline configuration fragmements were not optimal, so tweaking the meta data to make an enable-only configuration fragment avaiable and updating the options within that fragment. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-03-12linux-yocto/3.8: bump kver to v3.8.1Bruce Ashfield1
Updating the linux-yocto_3.8 SRCREVs to reflect the integration of the korg 3.8.1 -stable release. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-03-12linux-yocto/3.4: update to v3.4.34 and LTSI refreshBruce Ashfield3
Updating the 3.4 SRCREVs to incorporate the -stable release of 3.4.34 and the latest LTSI fixes up to [36a9caf 2 more fixes added]. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-03-02linux-yocto: remove 3.0 linux-yocto recipesBruce Ashfield2
With the introduction of the 3.8 linux-yocto recipes, we remove the 3.0 variant. 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-03-02linux-yocto: introduce 3.8 kernel recipeBruce Ashfield1
Introducing the linux-yocto 3.8 kernel recipe. The tools and branch structure of this tree are the same as the previous linux-yocto recipes, while the meta data and content have been updated for the 3.8 kernel. build and boot tested for qemu*. 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>
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-20 13:04:42 +0000