summaryrefslogtreecommitdiff
path: root/meta/recipes-kernel
AgeCommit message (Collapse)AuthorFiles
2013-07-05dtc: Update to 1.4.0 Git TagSaul Wold2
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-05babeltrace: Update to 1.1.1 based releaseOtavio Salvador1
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-05lttng-ust: Update to 2.2.0 based releaseOtavio Salvador2
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-05lttng-modules: Update to 2.2.0 based releaseOtavio Salvador2
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-05lttng-tools: Update to 2.2.0 based releaseOtavio Salvador1
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-02lttng-modules: allow building without tracepoints enabled in kernelPaul Eggleton1
Avoid a QA failure and instead produce a sensible warning message if no modules were built. Fixes [YOCTO #4791]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-02linux-firmware: fix ralink license file namePaul Eggleton1
LICENCE not LICENSE and -firmware not _firmware. (Upstream seems totally inconsistent with these filenames, unfortunately). Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-02linux-firmware: be consistent with license package namingPaul Eggleton1
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. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.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-25systemtap: Systemtap can not be build w -O0 optimizationMark Hatle1
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. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-25linux-firmware: Package some iwlwifi firmware separatelyRichard Purdie1
Taken from meta-intel, might as well merge this into the core recipe. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-24Sync with PRINC removal from meta-intelRichard Purdie3
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-06-13latencytop: Deprecate tracing_enabled for tracing_onRoy.Li2
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 Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-10trace-cmd: backport three patchesRoy.Li4
Backport three patches to fix running issues. Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
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-31kern-tools: expand kernel features that point to a directory nameBruce Ashfield1
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. 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-24linux-firmware: Split 'ar3k' in a linux-firmware-ar3k packageOtavio Salvador1
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Saul Wold <sgw@linux.intel.com>
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-16kern-tools: refresh and make dash compliantBruce Ashfield1
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-12Upstream-Status: Correct CapitalizationSaul Wold1
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-05-12kexec-tools: upgraded to 2.0.4Bogdan Marinescu1
Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-05-09powertop: inherit gettextSaul Wold1
powertop uses gettext during config time and at build time to generate the messages, so really should inherit gettext [YOCTO #4470] 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 Purdie2
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-09oprofileui(-server): upgraded to GIT revision f168b8bfBogdan Marinescu3
'obsolete_automake_macros.patch' is not needed anymore, because it was integrated in the specified commit. 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 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-08kern-tools: anchor and delimit regexsBruce Ashfield1
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> 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-28linux-firmware: Look for RTL license in the right directoryDarren Hart1
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> Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-22powertop: add 2.3Marcin Juszkiewicz3
With all tweaks from 1.13: - uclibc buildable - libncurses instead of libncursesw Changes from v3: - proper update-alternatives path Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-04-22lttng: updated lttng-ust to 2.1.2Maxin B. John1
lttng-ust: upgrade to the latest version 2.1.2 Also updated HOMEPAGE and BUGTRACKER. Signed-off-by: Maxin B. John <maxin.john@enea.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-04-18perf: Ensure license is handled correctlyRichard Purdie1
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 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-15kern-tools: fix custom repository BSP generationBruce Ashfield1
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 Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-12kern-tools: fix non-local patch/config locationBruce Ashfield7
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 Ashfield1
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 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-10kern-tools: fix excluded configuration processingBruce Ashfield1
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 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>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-23 19:29:21 +0000