summaryrefslogtreecommitdiffstats
path: root/meta/recipes-kernel
AgeCommit message (Collapse)Author
2013-07-02lttng-modules: allow building without tracepoints enabled in kernelPaul Eggleton
Avoid a QA failure and instead produce a sensible warning message if no modules were built. Fixes [YOCTO #4791]. (From OE-Core rev: 3ef5b19cbd7a90e11fc61223737b0b8e0e60b1a3) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-07-02linux-firmware: fix ralink license file namePaul Eggleton
LICENCE not LICENSE and -firmware not _firmware. (Upstream seems totally inconsistent with these filenames, unfortunately). (From OE-Core rev: 1c6fd89967a949903a5ebffa9c4df7b5c06d32d1) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-07-02linux-firmware: be consistent with license package namingPaul Eggleton
Much as I prefer en_GB spelling, we need to be consistent with the other package names in this recipe. Thanks to Trevor Woerner for pointing this out. (From OE-Core rev: f8e4e91de69d5e2f92a122a596d7241546034386) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-28linux-yocto-dev: bump version to 3.10+Bruce Ashfield
The linux-yocto-dev kernel is at 3.10-rcX, so we should bump the version to reflect reality. (From OE-Core rev: 8be4d1314a1334f5218e4eb46d3f8b734d5516f5) 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-06-28linux-yocto/3.4: ltsi: sync to LTSI commit 5f05247edBruce Ashfield
Updating the 3.4 branches to the latest LTSI baseline. (From OE-Core rev: f53de5834559ed24b05f6bec8aaccdfc36f0a806) 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-06-28linux-yocto/3.8: add USB screen configuration and net sched optionsBruce Ashfield
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> (From OE-Core rev: 722f949f7defef62c4d258716cebc77c55edbbe2) 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> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-28linux-yocto/3.4: allow kernel feature _appends to be overridenBruce Ashfield
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. (From OE-Core rev: 3bd592e832c6ce10947882f37564c12f4fa7f8e2) 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-06-25systemtap: Systemtap can not be build w -O0 optimizationMark Hatle
Systemtap will fail with: ../usr/include/features.h:330:4: error: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Werror=cpp] | # warning _FORTIFY_SOURCE requires compiling with optimization (-O) Use the same technique that eglibc uses to catch and correct the optimization level, changing to -O2. (From OE-Core rev: 9ceebb966e5294a270222475ab6317dcae2952fa) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-25linux-firmware: Package some iwlwifi firmware separatelyRichard Purdie
Taken from meta-intel, might as well merge this into the core recipe. (From OE-Core rev: bb3201b9c21b29604eb06b03e935d53210a7b762) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-24Sync with PRINC removal from meta-intelRichard Purdie
PRINC usage is removed from meta-intel, bump core PR values to ensure no version regressions. (From OE-Core rev: c6108ebe116eafaf0a22b5f22a3eec87c86859f4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-18linux-yocto/3.8: fix gcc 4.8 ARM boot issuesBruce Ashfield
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] (From OE-Core rev: 8ef393bc08a20053765ad58c1ebd9ab621cdd704) 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-06-13latencytop: Deprecate tracing_enabled for tracing_onRoy.Li
tracing_enabled should not be used, it is heavy weight and does not do much in helping lower the overhead. see commmit (Deprecate tracing_enabled for tracing_on 6752ab4a9c30d5411b2dfdb251a3f1cb18aae48) in kernel (From OE-Core rev: ee95048cf0c79dc52857dbc0e5da9363f2ad8b9b) Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-11trace-cmd: backport three patchesRoy.Li
Backport three patches to fix running issues. (From OE-Core rev: c00f67b5cd84adda7566505ec9372e11ad812ca1) Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-31linux-yocto: remove 3.2 kernel recipesBruce Ashfield
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. (From OE-Core rev: b8d53d8f91bd1b165016ea1063868c8b15f07ce0) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-31kern-tools: expand kernel features that point to a directory nameBruce Ashfield
Updating the kern-tools SRCREV to pick up the following fix: When a feature is passed to the kernel configuration scripts, and that feature is a directory name, it is a shortcut for: $DIR/$DIR.scc This expansion is not commonly used, and should be avoided. But for the purposes of backwards compatibility, updateme can expand the feature into a .scc file before passing it to the next set of configuration scripts. (From OE-Core rev: bec0a48c34695827d70cbbde7795b5a56fc13d56) 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 Ashfield
Updating the -stable linux-yocto trees to the latest korg -stable releases. (From OE-Core rev: 00e0ec6c1441815a7605753e8888e45244900b63) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-24linux-firmware: Split 'ar3k' in a linux-firmware-ar3k packageOtavio Salvador
(From OE-Core rev: ea6a8c9b0dee89b0b25d341ac57666cf090d6ed3) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-17linux-yocto/3.8: set qemumips64 SRCREVsBruce Ashfield
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. (From OE-Core rev: 6c94a53f7c1b674927486fdbf81613b2832bae40) 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 Ashfield
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. (From OE-Core rev: 0b4187fac16f78a1f9ba1c696edbc8c2aa189cb1) 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> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-16kern-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] (From OE-Core rev: 681bcd2783e100dd2882273f28f16ef118161e89) 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-12Upstream-Status: Correct CapitalizationSaul Wold
(From OE-Core rev: 43b2a2f375e2201be7a9bb6a9c5c0a9fc61f3361) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-12kexec-tools: upgraded to 2.0.4Bogdan Marinescu
(From OE-Core rev: 4e559881b4dd56e47762770acfab45e43f95fe45) Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-09powertop: inherit gettextSaul Wold
powertop uses gettext during config time and at build time to generate the messages, so really should inherit gettext [YOCTO #4470] (From OE-Core rev: 9eb94ba3d98bf6196eb779590f2fb842ec664177) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-09classes/recipes/lib: Fix various python whitespace issuesRichard Purdie
There are some left over tab characters in the python functions. This removes them and resolves python 3 errors. (From OE-Core rev: fafeb381c48291fa65c634c01c244843c8d7fad3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-09oprofileui(-server): upgraded to GIT revision f168b8bfBogdan Marinescu
'obsolete_automake_macros.patch' is not needed anymore, because it was integrated in the specified commit. (From OE-Core rev: 4c7120a24cef2ff6b9df821c69153363c938ac77) Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-08linux-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 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-08linux-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 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-08kern-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 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-08linux-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 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-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 ] (From OE-Core rev: e20c3bf6ce0d8ab5653739dd02555186b78b8912) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-28linux-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 rev: fc7fafcb3bb5c12bad07e12c15ac3a489bd0291f) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-22powertop: add 2.3Marcin Juszkiewicz
With all tweaks from 1.13: - uclibc buildable - libncurses instead of libncursesw Changes from v3: - proper update-alternatives path (From OE-Core rev: 188862de64bc2b61f8510082c8a6e5929d2b79d1) Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-22lttng: updated lttng-ust to 2.1.2Maxin B. John
lttng-ust: upgrade to the latest version 2.1.2 Also updated HOMEPAGE and BUGTRACKER. (From OE-Core rev: d18cec89e7afd05473232e587893334c4f921b41) Signed-off-by: Maxin B. John <maxin.john@enea.com> Signed-off-by: Saul Wold <sgw@linux.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] (From OE-Core rev: 578937213c6db9fa99981778ce61210e391b19a7) 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. (From OE-Core rev: c04f611aa4bf77867fe78a005d09434226feb62c) 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. (From OE-Core rev: 2d7b2478a3d48a5686afde790c378ee2f69b8e59) 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
(From OE-Core rev: 6af6df6c6507cae61dbd9d6994ff4162b54df451) 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. (From OE-Core rev: ddce9f375c626ef2c86f48612b3d7a24e3111b0b) 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. (From OE-Core rev: 4170e458e0f700319f4e1023c0c6c2d803449566) 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. (From OE-Core rev: 0271dec64591c4d91933b3a8db875a374a63640b) 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. (From OE-Core rev: b7b7ebe57bd6fd248e80be0b7e517a3ceb7cfd11) 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] (From OE-Core rev: 3d88f61b59f0a07e199306bf3a15ab023e77e17d) 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. (From OE-Core rev: 961ab0ac53de317c22409d90244a313998959714) 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. (From OE-Core rev: 1e20b3cbc8da3e6729d3825c62422c0dd82e1577) 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] (From OE-Core rev: 9f3ff1f907a0cf65d8aff82134463c4321d4b1e2) 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] (From OE-Core rev: 3570cf11b7dfa6991c43bb041abb9d47cc6f0d70) 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. (From OE-Core rev: f2a2256f08287baac9cf1f9fd58b5b8244c09610) 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. (From OE-Core rev: 644dfe0b13f68a04bdde67b5f1bf210bbe8ab918) 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> (From OE-Core rev: ab6630df4d100ff501b33a1c7ec9d1e6a2d4f0ee) 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. (From OE-Core rev: 750a9554e1b85d9bd23d18e0630723c3c193c604) Signed-off-by: Chase Maupin <Chase.Maupin@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>