summaryrefslogtreecommitdiffstats
path: root/meta/recipes-kernel
Commit message (Collapse)AuthorAgeFilesLines
* kernel-yocto: allow multiple / shared kernel feature directoriesBruce Ashfield2013-02-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To promote the reuse and sharing of configuration fragments this change allows any kernel-yocto based recipe to have multiple alternate git repositories which provide kernel feature directory trees listed on the SRC_URI. These feature directories are in addition to any in-tree kernel meta data branches that may be available (described via the KMETA variable in linux-yocto recipes). Features found within these directories can be used from recipes via the KERNEL_FEATURES variable. Features found within a feature directory are free to include any other features that are available in any directories. In both cases the path to a feature description (a .scc file) is relative to the root of a given feature directory (which is how existing .scc files work) The search order for features is determined by the order that repositories appear on the SRC_URI. Normal SRC_URI rules apply to any repository that is added as a kernel feature container. A SRCREV must be supplied and it must be unpacked to a unique directory, which is controlled via the "destsuffic" url parameter. In addition to these standard requirements, any kernel feature repository reference should identify itself via the "type=kmeta" url parameter. If type=kmeta is not supplied, the repository will not be processed for kernel features. As an example, the following in a linux-yocto bbappend makes two additional feature directories available to KERNEL_FEATURES and fragments. SRC_URI += "git://git.yoctoproject.org/yocto-kernel-cache;protocol=git;branch=master;type=kmeta;name=feat1;destsuffix=kernel-cache/" SRC_URI += "git://${KSRC_linux_yocto_3_4};protocol=file;branch=meta;name=feat2;type=kmeta;destsuffix=kernel-features-experimental/" SRCREV_feat1 = "${AUTOREV}" SRCREV_feat2 = "${AUTOREV}" (From OE-Core rev: 02ad603a104b70ab74548c8018e738bfbb3c59db) 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>
* update-modules: remove recipe from oe-coreLaurentiu Palcu2013-02-043-574/+0
| | | | | | | | | | | update-modules is not used anymore. Any references to it have been removed, some time ago, from all recipes/bbclasses. It stayed in oe-core in case anybody still wanted to use it. Time for it to go. (From OE-Core rev: b8c5f1facd9f9878e137f803b45e99d4e7214d20) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemux86-64: Disable paravirt guest, causes test failure on older kernelsDarren Hart2013-02-011-1/+1
| | | | | | | | | | | The 2.6.37 kernel on the AB occasionally fails dmesg and shutdown tests with general protection faults. (From OE-Core rev: 64749308fadabb4aa7c39f360c6395827bc5eb3a) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oprofile: remove AX_KERNEL_VERSION from acinclude.m4Tom Zanussi2013-02-011-19/+0
| | | | | | | | | | | | | | | | | | | | | | The version of this macro in acinclude.m4 is preventing the correct version in the package's kernelversion.m4 from being used. Since the version in acinclude.m4 includes the obsolete config.h, any test that uses it with newer (> 2.6.19) kernels fails. In the case of oprofile it means that perf_events support is never detected and thus 'legacy oprofile' is always built. Fixing this allows the new perf_events 'operf' support to be built. Fixes [YOCTO #3447] (From OE-Core rev: 3f7f17894c097ebaa81055c8449c543b734df541) (From OE-Core rev: 6fac31c7930e228efe5fed978964885e37a4da80) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oprofile: add kernel dependencyTom Zanussi2013-02-011-0/+2
| | | | | | | | | | | | | | oprofile-0.9.8 adds 'operf' which depends on the kernel's perf_events subsystem to be present when building, which adds the kernel dependency that we specify in a new DEPENDS for oprofile-0.9.8. (From OE-Core rev: d4dd1eaf75ef3d494d16ed2561e3ff4f5928a428) (From OE-Core rev: 16bc366877a2e02d96adb91b90e30710777e6f09) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oprofile: avoid processing files under .pcTing Liu2013-02-011-2/+2
| | | | | | | | | | | | | | | Fix the below issue: | DEBUG: Executing shell function do_configure | sed: can't read ./.pc/opstart.patch/doc/opstop.1.in: Permission denied | sed: can't read ./.pc/opstart.patch/doc/opstart.1.in: Permission denied | sed: can't read ./.pc/opstart.patch/utils/opstart.c: Permission denied | ERROR: Function failed: do_configure (From OE-Core rev: d1003ea86543ce5d09c163db95e9e723aa1adc10) Signed-off-by: Ting Liu <b28495@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* blktrace: add back do_install methodSaul Wold2013-01-221-1/+7
| | | | | | | | | | | The recent change to blktrace removed the do_install method, since this recipe does not use autotools it needs to specifiy a do_install activity. (From OE-Core rev: f8832d969746fb879e63d1b28e6beef5ab82a39d) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oprofile: backport patches to fix ppc build issuesMatthew McClintock2013-01-215-2/+357
| | | | | | | | | | | | | | | | | | | Fixes: | operf_utils.cpp: In function 'bool _op_get_event_codes(std::vector*)': | operf_utils.cpp:151:21: error: 'pfm_initialize' was not declared in this scope | operf_utils.cpp:151:26: error: 'PFM_SUCCESS' was not declared in this scope | operf_utils.cpp:166:45: error: 'PFM_PLM3' was not declared in this scope | operf_utils.cpp:166:55: error: 'PFM_OS_NONE' was not declared in this scope | operf_utils.cpp:166:72: error: 'pfm_get_os_event_encoding' was not declared in this scope | operf_utils.cpp:167:14: error: 'PFM_SUCCESS' was not declared in this scope [YOCTO #3717] (From OE-Core rev: 121cb96964fe2f374d814bf39036119bd63b9589) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oprofile: set correct kernel pathBogdan Marinescu2013-01-201-2/+2
| | | | | | | | | | | oprofile's "configure" was always looking at the configuration of the host kernel, not the target kernel. This patch instructs oprofile to use the target kernel to configure itself. (From OE-Core rev: 5892db9a34c188b8a9bdaa86e19ba62a7f4793b5) Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: update intel graphics features/configsBruce Ashfield2013-01-203-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | Updating the meta branch to import the following commits that cleanup and reorganize the features that make up the graphics features of the Intel BSPs c0b3904 meta: add config fragment for gma600 graphics driver f41638f meta: add config fragment for gma500 graphics driver ff8ad3e meta: sys940x: drop vesa fragment from bsp config fcb82ac meta: sys940x: remove emgd config from bsp config c1677bb meta: fri2: drop vesa fragment from bsp config 7324440 meta: fri2: remove emgd config from bsp config dd435c6 meta: emenlow: drop vesa fragment from bsp config 243b515 meta: emenlow: remove emgd config from bsp config 3e1be82 meta: crownbay: drop vesa fragment from bsp config fc5ed4e meta: crownbay: remove emgd config from bsp config d46236b meta: drm-emgd.cfg: add configs for dependent routines db4bc5e meta: relocate git-merge of emgd branch (From OE-Core rev: 8d0074ef2b61bf022ed1bb3b5f1afe526d8c921b) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: update to 3.4.26 and 3.4.25-rt37Bruce Ashfield2013-01-203-15/+15
| | | | | | | | | | Updating the yocto 3.4 kernel tree to the 3.4.25 and 3.4.26 -stable updates as well as refreshing the preempt-rt branches to 3.4.25-rt37. (From OE-Core rev: da536703bdcf31c8c2ef17f5a49d06280fe77600) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: integrate LTSI-3.4Bruce Ashfield2013-01-183-9/+9
| | | | | | | | | | | | | | | | | | | | | | Updating the linux-yocto-3.4 SRCREVS to activate the merge of the 3.4.25-ltsi tree: http://git.linuxfoundation.org/?p=ltsi-kernel.git;a=tag;h=refs/tags/v3.4.25-ltsi The pristine patch queue can be seen on the "ltsi" branch in the repository. This branch has been merged into the standard/base branch of linux-yocto-3.4 and to all BSP branches in the tree. LTSI based BSPs or features are not activated as part of this commit, they are controlled by the meta branch of the kernel repository and are activated in separate patches. [YOCTO #2396] (From OE-Core rev: 8f03ebe9b164e0c0493c56d9eb2e7d0b039832f1) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/routerstationpro: enable GPIO_SYSFSBruce Ashfield2013-01-183-3/+3
| | | | | | | | | | | | | We had a request to enable GPIO_SYSFS to allow easy use of the available GPIOs in the board out of the box. This is a simple / contained config item to enable, so there's no reason not to. [YOCTO #3519] (From OE-Core rev: 9a5948ff07b62f54d6215d37e9028384d3b430da) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/meta: update include statements to explicit .scc formatBruce Ashfield2013-01-183-3/+3
| | | | | | | | | | | | | | The kernel tooling can support a "shorthand" method of including other features that doesn't require the full filename ending in .scc. This format is confusing when compared to the source tree, and is inconsitently use. This commit updates all shorthand includes to a full "include <foo>.scc" format. [YOCTO #3418] (From OE-Core rev: acf015f079907da8a4f1b80e44bb64bc7696a6ad) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: normalize repository naming and SRC_URI optionsBruce Ashfield2013-01-182-2/+2
| | | | | | | | | | | linux-yocto-tiny and linux-yocto had minor differences from the rest of the linux-yocto recipes. After this commit, all the recipes are using bareclone=1 and repository names that end with .git. (From OE-Core rev: 1acf3ad17bbc1cdcad31c243b7b50daaea99ee7a) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* modutils-initscripts: improve modutils.shLaurentiu Palcu2013-01-181-9/+25
| | | | | | | | | | | | | | | | | | | | | | | modutils.sh reads /etc/modules to load the listed modules at boot time. /etc/modules is generated by update-modules which scans /etc/modules-load.d directory. However, update-modules became obsolete because the files it generates are not used by modprobe anymore. Hence, change modutils.sh to scan also /etc/modules-load.d/*.conf and load the modules listed there. Basically, the behavior is this: * if /etc/modules exists, load those modules; * if the directory /etc/modules-load.d exists, load the modules listed in the .conf files but ignore those already loaded (from /etc/modules); [YOCTO #3598] (From OE-Core rev: f2d6e84cb1694e2365beca331439bb2d23843a5b) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: use LICENSEs which can actually be parsedChristopher Larson2013-01-181-7/+6
| | | | | | | | | : is an invalid character for our license format. (From OE-Core rev: adb06f5907e8c28c7ee08aeb7c9ca40a1a98cf5f) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oprofile: add AArch64 supportMarcin Juszkiewicz2013-01-162-1/+33
| | | | | | | (From OE-Core rev: 169b9afcf2d357fdcf254a380d21d17701685834) Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-ust: bump PETom Zanussi2013-01-161-0/+1
| | | | | | | | | | | | | | | | The previous lttng-ust had a PE of "1" - that recipe was removed and replaced with the lttng2-ust recipe, which was renamed back to lttng-ust. The new recipe had didn't define a PE so got the default PE of 0 - this adds the PE back and gives it a value of "2", which reflects the history and fixes the following error: ERROR: Package version for package lttng-ust went backwards which would break package feeds from (1:0.16-r1 to 0:2.1.0-r0) (From OE-Core rev: 2fbfb2708fc7c0082b85ef964d850f8520b841d6) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes-kernel/lttng-2.0: rename to recipes-kernel/lttngTom Zanussi2013-01-165-0/+0
| | | | | | | | | | | | | recipes-kernel/lttng was removed by a previous patch, which also removed the naming conflict that caused the lttng-2.0 version of lttng to be named recipes-kernel/lttng-2.0. Since the naming conflict has disappeared, we can go back to the simpler naming. (From OE-Core rev: 2027fd1bbfc2c136672d5054ba722e9d9d80451d) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng2-ust: rename to lttng-ustTom Zanussi2013-01-162-1/+6
| | | | | | | | | | | | | | recipes-kernel/lttng/lttng-ust was removed by a previous patch, which also removed the naming conflict that caused the lttng-2.0 version of lttng-ust to be named lttng2-ust. lttng2-ust was the only lttng-2.0 recipe to be named in this way and since that was entirely due to the conflict, we can go back to the consistent naming for it. (From OE-Core rev: 3c927c39502061bdf3ef9fba1f0f6e7080f6c3cd) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng: remove 'legacy' lttngTom Zanussi2013-01-164-137/+0
| | | | | | | | | | | | | | | This removes 'legacy' lttng - it hasn't actually worked for awhile now, and has been replaced by equivalent functionality in recipes-kernel/lttng-2.0 (which will be renamed to lttng in a follow-up patch). Fixes [YOCTO #3303]. (From OE-Core rev: 920b4c292f6c704cfe32666a3e1de5bce19043b5) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: fix headers install in long path name environmentsBruce Ashfield2013-01-102-0/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If a build is started in a deep directory structure, or in a path with long directory names the installation of linux-libc-headers will fail with: | make[2]: execvp: /bin/sh: Argument list too long | make[2]: *** >From within the kernel Makefiles themselves. The solution is to patch the kernel build rules with the following change: [ scripts/Makefile.headersinst: install headers from scratch file If headers_install is executed from a deep/long directory structure, the shell's maximum argument length can be execeeded, which breaks the operation with: | make[2]: execvp: /bin/sh: Argument list too long | make[2]: *** By dumping the input files to a scratch file and using xargs to read the input list from the scratch file, we can avoid blowing out the maximum argument size and install headers in a long path name environment. ] Until this change, or a similar one, is merged into the mainline kernel, this change should be applied to any 3.7 or greater libc-headers build. Upstream-status: Pending (From OE-Core rev: 1e63a3b7b7915d40bb59976a02b9f53968997ed3) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-2.0: components updated to version 2.1.0Bogdan Marinescu2013-01-103-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | lttng2-ust, lttng-modules and lttng-tools were updated to version 2.1.0. Since these should be changed together, the changes are grouped into a single patch. The text for the lttng-tools LICENSE file has these lines changed (according to the license text, these shouldn't impact the actual licensing terms of the package): ================================================================= -) include/lttng/* -) src/lib/lttng-ctl/* We have some tests LGPL but should not impact anything even if we change them in the future to GPL. ================================================================= The text for the lttng-modules LICENSE files contains a minor change in the MIT section (a reference to the mit-license.txt file): ================================================================= These files are licensed under an MIT-style license. See mit-license.txt for details. ================================================================= (From OE-Core rev: 6f3397b4d5b32e31ed3ba832f48e35fdb1f5b6ab) 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>
* linux-libc-headers: make 3.7 the default and remove older libc-header recipesBruce Ashfield2013-01-073-19/+0
| | | | | | | | | | | | Switch the default libc-headers to the 3.7 version. At the same time, remove older versions of the headers to keep things simple and clear. All userspace and kernel combinations should build and boot against this single lib-headers version. (From OE-Core rev: e7c9706d6a6777326a62e73bffdbb0f940792ff4) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: add 3.7 versionMarcin Juszkiewicz2013-01-071-0/+4
| | | | | | | | (From OE-Core rev: 7f1672f9513f05a98197632fe24279ecf8a58505) Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: update to v3.4.24Bruce Ashfield2013-01-073-15/+15
| | | | | | | | | Updating the 3.4 recipes to v3.4.24 stable version. (From OE-Core rev: c3e97905f423e2bab2a0aadf5099ef445f0dd138) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: integrate v3.4.21, v3.4.22, v3.4.23Bruce Ashfield2013-01-073-15/+15
| | | | | | | | | Updating the SRCREVs to integrate the korg -stable updates. (From OE-Core rev: 88856144bf97630f4c43fd7c984343caf287a435) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oprofile: updated to 0.9.8Bogdan Marinescu2013-01-075-93/+27
| | | | | | | (From OE-Core rev: e8150e3941a471bf7e6d375595c15d54b809b15c) Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oprofile: use dynamic root home directoryKang Kai2012-12-262-9/+15
| | | | | | | | | | | Use stub "ROOTHOME" to replace "/home/root" in oprofile-root.patch, then we can substitute it with configured root home directory. (From OE-Core rev: 584fc5abe4ea08a92eff691af42300b5a26d2755) Signed-off-by: Kang Kai <kai.kang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* blktrace: essentially rework the recipe, obey LDFLAGSFahad Usman2012-12-263-65/+97
| | | | | | | | | | | | | | (From OE-Core rev: 8d5fa8f26e4cc366ac566d3682bd74eb4578cc6d) Signed-off-by: Christopher Larson <chris_larson@mentor.com> the patch was imported from meta-mentor layer on yoctoproject git server http://git.yoctoproject.org/cgit/cgit.cgi/meta-mentor as of commit id aed463414e2e2bf8ca44ba54ee5973e7ed599e57 Signed-off-by: Fahad Usman <fahad_usman@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-firmware: split out ralink driversAnders Darander2012-12-171-2/+8
| | | | | | | | | | | To reduce disk usage on systems using the ralink driver, split out the ralink firmware to a separate package. (From OE-Core rev: 732d7ba613835c1e2bd5e03f3f8dd0179cd47648) Signed-off-by: Anders Darander <anders@chargestorm.se> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* iperf: pass in target path varsFahad Usman2012-12-171-0/+11
| | | | | | | | | | | | | | | | (From OE-Core rev: accbcea94091800a90df0f5141990c110ff35ee5) Signed-off-by: Christopher Larson <chris_larson@mentor.com> the patch was imported from meta-mentor layer on yoctoproject git server http://git.yoctoproject.org/cgit/cgit.cgi/meta-mentor as of commit id 71748b54694f4ffe2d598da71f641969df1417c0 slightly modified the patch to apply it on .bb file instead of .bbappend Signed-off-by: Fahad Usman <fahad_usman@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: pass CFLAGS and LDFLAGSFahad Usman2012-12-171-1/+9
| | | | | | | | | | | | | | (From OE-Core rev: 373371432b72cb19600a45e741afdfcb9662ecfb) Signed-off-by: Christopher Larson <chris_larson@mentor.com> the patch was imported from meta-mentor layer on yoctoproject git server http://git.yoctoproject.org/cgit/cgit.cgi/meta-mentor as of commit id 9d698004137c1a888d40d6a4808d94afa22387e7 Signed-off-by: Fahad Usman <fahad_usman@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: kill -WerrorFahad Usman2012-12-171-1/+5
| | | | | | | | | | | | | | | | | | this fails to build using a recent sourcery toolchain due to unused-but-set-variable (From OE-Core rev: dce7918a818bf86fcc11f561af3eacaf281403d4) Signed-off-by: Christopher Larson <chris_larson@mentor.com> the patch was imported from meta-mentor layer on yoctoproject git server http://git.yoctoproject.org/cgit/cgit.cgi/meta-mentor as of commit ids 82e96b3baa1c64d03412871fce56d496a338f167 and ae325d011bd50501fe677c8b37295ae83030c526 Signed-off-by: Fahad Usman <fahad_usman@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Update the SRC_URI in systemtap recipeMaxin B. John2012-12-141-1/+1
| | | | | | | | | | | The SRC_URI in systemtap recipe uses 'sources.redhat.com' which redirects to 'sourceware.org'. This causes random fetch failures. Updating the recipe to use the direct link. (From OE-Core rev: 340841f8a5c8225ccb77b628f55a668c9d1097ec) Signed-off-by: Maxin B. John <Maxin.John@enea.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* babeltrace: upgrade to 1.0.0Constantin Musca2012-12-061-4/+4
| | | | | | | | | | | | | | | | | | | License checksum change due to diff: 15a16,22 > > * LGPLv2.1 > > The file include/babeltrace/list.h is licensed under LGPLv2.1. It only > contains trivial static inline functions and macros, and, therefore, > including it does not make babeltrace a derivative work on this header. > Please refer to the LGPLv2.1 license for details. (From OE-Core rev: 275ea500809e70ba2e432b950311678b2ff4aef6) Signed-off-by: Constantin Musca <constantinx.musca@intel.com> Signed-off-by: Radu Moisan <radu.moisan@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: inform the fetcher if the meta branch changesBruce Ashfield2012-12-061-1/+1
| | | | | | | | | | | | | | | The meta data branch for the kernel can be varied by changing the KMETA variable, but that change wasn't reflected in the SRC_URI, which means that the fetcher won't check for changes on that branch and is a potential source of errors. Making the meta branch specification KMETA vs meta solves the problem. (From OE-Core rev: 5bfc678aeb65b50710384e93b64add3a62146908) 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>
* linux-yocto/3.4: emenlow: switch from psb to emgd graphicsBruce Ashfield2012-12-063-3/+3
| | | | | | | | | | | | | | | | | | | Updating the meta branch SRCREVs for the following commit: [ meta/emenlow: use emgd instead of psb graphics driver This commit essentially does just this: Remove all the references of psb patches for emenlow BSP. Change the emenlow scc files to use emgd instead of psb. ] (From OE-Core rev: 06a2b9eb087d1d90213d67dc8fe14c53201afe37) Signed-off-by: Nitin A Kamble <nitin.a.kamble@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>
* linux-yocto/3.4: merge v3.4.19, v3.4.20Bruce Ashfield2012-12-063-15/+15
| | | | | | | | | | | Updating the linux-yocto-3.4 trees to incorporate both 3.4.19 and 3.4.20 from the kernel.org -stable team. (From OE-Core rev: 8ac0c82bb8fe4fe17b6a32b18e57546d21b4d5ef) 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>
* oprofile: Include config.h before bfd.hKhem Raj2012-12-062-2/+68
| | | | | | | | | | | oprofile uses bfd.h from binutils which now in 2.23+ expects config.h so lets include it (From OE-Core rev: cd7aa7440103284a47b96ec176cace8685f720bb) 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>
* latencytop: add missing signed-off-by and re-add upstream statusJack Mitchell2012-12-031-5/+9
| | | | | | | | | | | When I made a change to this patch in git commit 1b41a4660d0 I accidently removed the Upstream Status line and also didn't add the required signed-off-by tag. (From OE-Core rev: b76878810d39310d1061c637a6bb8f4aa9600054) Signed-off-by: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: move PREEMPT_NONE to beagleboard standard kernel onlyBruce Ashfield2012-12-033-3/+3
| | | | | | | | | | | | | | | | | | | A recent report of the preempt-rt beagleboard kernel not enabling full -rt preemption out of the box revealed that the existing fix for SD boot issues (which were fixed by disabling preemption) was the root cause for the options not being enabled. Although the fix for the SD card detection issues is still valid, it also doesn't make sense to apply it to a kernel type that only exists to support enhanced preemption. Since many variants of the board boot with preemption enabled, opening the possibility of a boot problem is acceptable, given that it allows the -rt kernel to be used. (From OE-Core rev: 1732197b53ba77a49792600c4c8385f4e44fe0bc) 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>
* sysprof: Fixes undefined  reference to `rmb'Noor Ahsan2012-11-261-0/+1
| | | | | | | | | | | * Recipe already contains a patch for mips arch but not for mips64. For mips64 arch 'mips' was not available in OVERRIDES, rather mips64 was there. So added the same patch for mips64 arch using mips64. (From OE-Core rev: 5fa9f9b626daed83c8d31755040574c13ad25459) Signed-off-by: Noor Ahsan <noor_ahsan@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kern-tools: report missing config fragments by nameBruce Ashfield2012-11-241-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | If a configuration fragment was missing, the previous error output was not clear about the error: | [INFO] doing kernel configme | [INFO] Configuring target/machine combo: "standard/atom-pc" | [INFO] collecting configs in ./meta/meta-series | ERROR: could not sanitize configuration fragments | errors are logged in ... linux/meta/cfg/standard/atom-pc/config.log but we know the name of the missing fragment and can improve the error message to be this: | [ERROR] kernel configuration fragment fragment 'virto.cfg' cannot be found | ERROR. A meta series could not be created for branch yocto/standard/common-pc/atom-pc | ERROR. Could not locate meta series for atom-pc | ERROR. Could not apply patches for atom-pc. | Patch failures can be resolved in the devshell (bitbake -c devshell linux-yocto) [YOCTO #3473] (From OE-Core rev: 8e5dc511ffce4f4b512457dbc5d3dd510f6e4a95) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto-3.4: gcc optimization config featureBruce Ashfield2012-11-241-1/+1
| | | | | | | | | | | | | | | | Updating the meta SRCREV to include a x86 gcc optimization feature, and its use by several BSPs: 1c59807 meta: rangeley: Remove the shortcut path b5477d0 meta: crystalforest: Enable GCC inline compiler option ab2b874 meta: rangeley: Enable GCC inline compiler option 8287750 meta: Add New feature for GCC optimizing (From OE-Core rev: b042d1cce535fe88dd6f5b5c0cd1a608a27afbd6) Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "kern-tools: report missing config fragments by name"Richard Purdie2012-11-221-1/+1
| | | | | | | This reverts commit 46cc0d0a2f1486bf541c1a1b11075de3da396cc2 since the revision in question isn't in the repository. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kern-tools: report missing config fragments by nameBruce Ashfield2012-11-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | If a configuration fragment was missing, the previous error output was not clear about the error: | [INFO] doing kernel configme | [INFO] Configuring target/machine combo: "standard/atom-pc" | [INFO] collecting configs in ./meta/meta-series | ERROR: could not sanitize configuration fragments | errors are logged in ... linux/meta/cfg/standard/atom-pc/config.log but we know the name of the missing fragment and can improve the error message to be this: | [ERROR] kernel configuration fragment fragment 'virto.cfg' cannot be found | ERROR. A meta series could not be created for branch yocto/standard/common-pc/atom-pc | ERROR. Could not locate meta series for atom-pc | ERROR. Could not apply patches for atom-pc. | Patch failures can be resolved in the devshell (bitbake -c devshell linux-yocto) [YOCTO #3473] (From OE-Core rev: 46cc0d0a2f1486bf541c1a1b11075de3da396cc2) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: uprobes: reinstate config options for 'uprobe' featureBruce Ashfield2012-11-223-3/+3
| | | | | | | | | | | | | | | | | bumping the meta SRCREV to import the following fix: [ uprobes: reinstate config options for 'uprobe' feature commit 17ec51adfff (meta: cleanup invalid/obselete 3.4 CONFIG options) removed the uprobes config options, this restores them. ] (From OE-Core rev: 8c637986e063fcb087babecfc0192f96d3981515) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.0: fix virtio configuration typoBruce Ashfield2012-11-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | The recent tools updates in master exposed a typo that has existed in the 3.0 kernel meta data and that breaks the build for boards still using the 3.0 kernel. Bumping the meta SRCREV to pickup the following fix: [ commit fa9b8c24e84bb9d75d08d197c84c50ce4f99c424 Author: Bruce Ashfield <bruce.ashfield@windriver.com> Date: Wed Nov 21 09:24:46 2012 -0500 meta: fix typo in virtio.scc virtio.scc was referring to an invalid/incorrect virto.cfg. Fixing this typo fixes the build for boards still using the 3.0 kernel. ] (From OE-Core rev: b16d72a749ac73a2bd0434f36102c00f6c476bc1) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-11 18:03:55 +0000