summaryrefslogtreecommitdiffstats
path: root/meta/recipes-kernel
Commit message (Collapse)AuthorAgeFilesLines
* linux-firmware: upgrade to git HEAD c530a75c1e6a472b0eb9558310b518f0dfcd8860Cristian Iorga2013-03-181-2/+1
| | | | | | | | (From OE-Core rev: 7b72b631a8fa52c48375916af0b42340996be8ba) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* babeltrace: Upgrade to v1.0.3Radu Moisan2013-03-181-1/+1
| | | | | | | | (From OE-Core rev: dbdb4ff0760cc01be0114b13b0c3ef1b0ae36cd6) 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>
* systemtap: Upgrade to v2.1Radu Moisan2013-03-182-19/+7
| | | | | | | | (From OE-Core rev: 7f572cecd89a992a7120c73f936c27d9fc030f57) 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.8: update EDF configurationBruce Ashfield2013-03-121-1/+1
| | | | | | | | | | | | The sched_deadline configuration fragmements were not optimal, so tweaking the meta data to make an enable-only configuration fragment avaiable and updating the options within that fragment. (From OE-Core rev: 43d2ae5695844d29ccad2c8a2760b803352d1f67) 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.8: bump kver to v3.8.1Bruce Ashfield2013-03-121-8/+8
| | | | | | | | | | | Updating the linux-yocto_3.8 SRCREVs to reflect the integration of the korg 3.8.1 -stable release. (From OE-Core rev: 75e247ed9a8a731480bef3ab0753fbad200469be) 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: update to v3.4.34 and LTSI refreshBruce Ashfield2013-03-123-15/+15
| | | | | | | | | | | Updating the 3.4 SRCREVs to incorporate the -stable release of 3.4.34 and the latest LTSI fixes up to [36a9caf 2 more fixes added]. (From OE-Core rev: e5602b0414fca0183d5aa90d9b462ac8e8401cbb) 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>
* perf: rename perf_3.4 to perfTom Zanussi2013-03-101-0/+0
| | | | | | | | | | | | | | | There's nothing kernel-version-specific about the perf_3.4 recipe, so it's actually misnamed and misleading now that it also gets used with the 3.8 kernel. Since the recipe isn't tied to a specific PV, and simply uses whatever's in STAGING_KERNEL_DIR, there's no reason to add anything else either to the bare PN, so just use that as the recipe name. (From OE-Core rev: 9a249e074f0329ad54848b84536e5b7cb117ee2c) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: rename perf.inc to perf-features.incTom Zanussi2013-03-102-1/+1
| | | | | | | | | | | | The contents of perf.inc are really specific to perf features and shouldn't use the generic perf.inc name, which implies common recipe code. It's always confusing to open up this file and find out that's not what it is. (From OE-Core rev: 4a98bd02ab8918e639353829b221b0c4b6c58165) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: disable PARALLEL_MAKETom Zanussi2013-03-051-0/+2
| | | | | | | | | | | | | | Autobuilder builds periodically and now more frequently have been failing because of a race between the perf build and the newly separated libtraceevent - perf tries to link libtraceevent.a, which hasn't finished building yet in those cases. This disables the parallel build to prevent that. (From OE-Core rev: cd1e98513016c01e32bdb175ec7225d7378d952c) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysprof: upgrade to 1.2.0Tom Zanussi2013-03-052-39/+2
| | | | | | | (From OE-Core rev: aef171f824659b255b0ed2f6430bb757fc26f9c2) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng: updated lttng-ust and lttng-modules to 2.1.1Bogdan Marinescu2013-03-052-4/+4
| | | | | | | | (From OE-Core rev: a895f5c535c9cbd71d2965c1197ffb31afd831a8) 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>
* oprofile: update patch for powerpc64Matthew McClintock2013-03-055-38/+374
| | | | | | | | | | | | | | | This is a more appropriate follow up patch from upstream. Also, only powerpc64 requires libpfm4 currently for this specific version of oprofile (x86, sparc can make use of libpfm but don't make use of it here) Additionally, this patch from upstream requires some more patches to be pulled into oprofile (From OE-Core rev: 2792e1f6a1d8969e0891334e6cd4e04f84f7e9ff) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libpfm4_4.3.0.bb: use compatible host to limit archesMatthew McClintock2013-03-051-0/+3
| | | | | | | | | | | | This is only test with powerpc64 currently, even though it should work on other arches such as x86 and sparc. When thos are testing and working this COMPATIBLE_HOST should be updated (From OE-Core rev: 09f57ae44e1f610e615463149fb45ccfab1d5135) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: remove 3.0 linux-yocto recipesBruce Ashfield2013-03-022-61/+0
| | | | | | | | | | | With the introduction of the 3.8 linux-yocto recipes, we remove the 3.0 variant. (From OE-Core rev: 6835f1ecd7012bd4616efa3129bcf03b5be542ca) 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: introduce 3.8 kernel recipeBruce Ashfield2013-03-021-0/+30
| | | | | | | | | | | | | | Introducing the linux-yocto 3.8 kernel recipe. The tools and branch structure of this tree are the same as the previous linux-yocto recipes, while the meta data and content have been updated for the 3.8 kernel. build and boot tested for qemu*. (From OE-Core rev: ecf287a80c5ace2c440f8d0089934d59d25dc3ec) 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-libc-headers: update to v3.8Bruce Ashfield2013-03-022-8/+8
| | | | | | | | | | | | | Now that the 3.8 kernel has been released we can bump the libc-headers to that version and remove the 3.7 variant. Userspace compatibility is maintained through kernel versions, we also make the single 3.8 version the toolchain default. (From OE-Core rev: 4f9ef639143d890e9d2e71fea3b461fcc8e3f678) 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>
* kern-tools: import configuration, controls and audit updatesBruce Ashfield2013-03-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Updating the kern-tools SRCREV to import the following fixes: commit 7f91d198d32fc90260e52724ef4aac0b997c1e8b kconf_check: fix new Kconfig detection One of the functions of the kernel configuration audit is to notify the user if Kconfig* files have been removed from the kernel, and also to notify of new Kconfig files. New Kconfig files should be classified as hardware or non-hardware to allow BSP audits to notify if boards are setting values that they shouldn't, hence why notifying about new "buckets" is important. commit c4f26a3296e0e1c3dbdd5ec8e2947d5443a9ffc2 updateme/scc: allow config fragment exclusion It is common to need the features (patches, git operations) of a branch, but not want the kernel configuration fragments of a given branch. To allow this, we provide a new include flag "nocfg". When this flag is used, all of the configuration fragments included by the targetted feature will not be applied to the current build, with one exception, a base/critical fragment can force it's config values, since without them, the system would not be functional. Example: include ktypes/standard/standard.scc nocfg commit c7ec19d55aca6c4b17073c5362fce5be61a89d82 scc: wrap git merge To allow for parameter validation and sanity checking, wrap "git merge" as a dedicated "merge" command instead of using the raw git fallback. This also makes it consistent with existing top level commands such as 'tag', 'branch', 'patch', etc. There are no changes to arguments, and existing 'git merge' commands continue to work with this change. [YOCTO #3419] [YOCTO #3421] (From OE-Core rev: faf042b2c87874153a6b689479ab86e49804af8c) 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>
* depmodwrapper-cross: Mark as machine specificRichard Purdie2013-03-021-0/+4
| | | | | | | | | | | The kernel and its staging directory are machine specific so the wrapper needs to be as well. Also take the opportunity to remove the default dependencies of the recipe since its a script and doesn't need the cross compiler. This gives the build a little more scheduing freedom. (From OE-Core rev: 1cc2ac769baae19b54184df5f43a3e77c1743c29) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: add bash dependencyTom Zanussi2013-03-021-1/+1
| | | | | | | | | | | | | | There are a number of scripts in the perf installation that use bash, so we need to add a run-time dependency on bash for them. If not, we can generate build errors like "no package provides /bin/bash". Fixes [YOCTO #3951]. (From OE-Core rev: 8169adeba67180f062fa7c0105fc4283da3103c6) 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>
* systemtap: add python and bash dependenciesTom Zanussi2013-03-021-0/+4
| | | | | | | | | | | | | | | There are a number of scripts in the systemtap installation that use python and bash, so we need to add run-time dependencies for them. If not, we can generate build errors like "no package provides /usr/bin/python". Fixes [YOCTO #3951]. (From OE-Core rev: 8a0d31af7008459d1affa0afe3ff193a78f9020d) 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>
* module.bbclass: Create a new depmodwrapper to assist cross-installsMark Hatle2013-03-011-0/+43
| | | | | | | | | | | | | | | | | Previously the build path to STAGING_KERNEL_DIR was being embedded into the package post install scripts. We avoid this behavior by generating a special depmodwrapper script. This script contains that hard-coded path, ensuring that re-use of the sstate-cache (and/or packages) will always run through the wrapper generated by the current build with a checksum that includes STAGING_KERNEL_DIR. [ YOCTO #3962 ] (From OE-Core rev: b18c61bae4d7161c087a004bba3c696006f7a2f6) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: remove cedartrail machineBruce Ashfield2013-03-013-3/+3
| | | | | | | | | | | | The cedartrail BSP is no longer support from yocto 1.4, so we remove it from the tree. (From OE-Core rev: a1ce9da1feb028bbfd861d075bc3b6fbe3300147) Signed-off-by: Kishore Bodke <kishore.k.bodke@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>
* lttng-ust: cannot find -llttng-ust-tracepointRobert Yang2013-02-262-1/+33
| | | | | | | | | | | | | | liblttng_ust.la should depend on liblttng-ust-tracepoint.la, otherwise there maybe a parallel build issue when building liblttng_ust.la: ld: cannot find -llttng-ust-tracepoint [YOCTO #3934] (From OE-Core rev: b947dbc72b3cd03901112c1bab6ac0b81f1b374f) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-dtc: Make KERNEL_DEVICETREE_FLAGS configurableAnders Roxell2013-02-221-1/+1
| | | | | | | | (From OE-Core rev: f46c5714bc23a50a207c03cc20c3a6aebe8c5df0) Signed-off-by: Anders Roxell <anders.roxell@enea.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oprofileui-server: replace obsolete automake macros with working onesMarko Lindqvist2013-02-222-2/+24
| | | | | | | | | | | | | Add obsolete_automake_macros.patch that replaces automake macros no longer supported by automake-1.13 with modern constructs. Removed AM_PROG_CC_STDC. AC_PROG_CC to replace it was already present. (From OE-Core rev: 254799258ead1b7a59c301ad2d3e3c7e5b9fb8db) Signed-off-by: Marko Lindqvist <cazfi74@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemtap: replace obsolete automake macros with working onesMarko Lindqvist2013-02-123-1/+29
| | | | | | | | | | | | | Add obsolete_automake_macros.patch that replaces automake macros no longer supported by automake-1.13 with modern constructs. Removed AM_PROG_CC_STDC. AC_PROG_CC to replace it was already present. (From OE-Core rev: 3a335af7da5a94249d2f0d49d89cf0c8f180776e) Signed-off-by: Marko Lindqvist <cazfi74@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: KERNEL_FEATURES should reference full scc filesBruce Ashfield2013-02-064-20/+18
| | | | | | | | | | | | | Some existing KERNEL_FEATURE references use a shorcut notation, but mapping these shortcuts to actual .scc files in the tree are not obvious. So we clarify where they are found by referencing the full .scc filename in the KERNEL_FEATURE addtions. (From OE-Core rev: 26c71c895e1d56d2f3576de833a576137e970fcc) 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: update to v3.4.28, 3.4.28-rt40Bruce Ashfield2013-02-063-15/+15
| | | | | | | | | | | Updating the linux-yocto_3.4 SRCREVs to pick up the 3.4.28 -stable update as well as the 3.4.28-rt40 refresh. (From OE-Core rev: f8619d777e734f3886b02bf87157761a6f78029b) 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/dev: linux-yocto development tree tracking recipeBruce Ashfield2013-02-061-0/+48
| | | | | | | | | | | | | | | | The linux-yocto-dev recipe uses the upstream tracking linux-yocto-dev repository. Since this tree is frequently updated, and periodically rebuilt, AUTOREV is used to track its contents. This recipe is just like other linux-yocto variants, with the only difference being that to avoid network access during initial parsing, static SRCREVs are provided and overridden if the preferred kernel provider is linux-yocto-dev. (From OE-Core rev: 378f99eeab070e2fcea84fb47f37cd7cb15caa90) 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: fix cross compile on powerpc and add libpfm4 depMatthew McClintock2013-02-062-2/+40
| | | | | | | | | | Fixes [YOCTO #3717] (From OE-Core rev: 88959e42411a40b15fe8907da00a97a7732a9cc1) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libpfm4_4.3.0.bb: add libpfm4 recipe needed by oprofile for ppcMatthew McClintock2013-02-061-0/+26
| | | | | | | | (From OE-Core rev: 52c94978992d9084d685d4999064a8cee35220d1) Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* 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>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-13 16:30:59 +0000