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>
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>
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>
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>
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>
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>
(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>
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>
(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>
(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>
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>
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>
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>
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>
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>
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 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>
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>
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>
* 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>
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>
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>
This reverts commit 46cc0d0a2f1486bf541c1a1b11075de3da396cc2 since
the revision in question isn't in the repository.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
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>
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>
Updating the SRCREV to import the following changes.
[updateme: find the board description with the highest score]
This removes the requirement that a custom linux-yocto .scc file have
define KTYPE <foo>, where <foo> is typically "standard". The tools can
now match on a .scc file that only matches the board, but will still
chose one that matches the board and kernel type, if available.
[updateme: allow for tabs or spaces in defines]
define KMACHINE<tab>$MACHINE was missed by the regex.
[scc/kgit-meta: detect and avoid duplicating patching]
To allow feature description to be included multiple times, they were
previously split into -enable and 'patch' descriptions. With this change
the patches will be detected as already included, and skipped
automatically. Removing the need to do this split. It also cleans up
the ability to warn about multiple includes.
[kconf_check: add "verify" configuration fragment type]
This adds the ability for a BSP to have a kernel configuration
fragment that lists options that must be present. If they are not
present it is a hard error. "required" is a similar fragment, but
it adds them to the build, and audits them at the end, but does
not abort the build if they are present. This is a minor distinction,
but one that is useful when creating flexible, shared kernel config
structures.
[kconf_check: improve kernel audit report formatting]
[kconf_check: perform validity checks on non-hardware options]
[kconf_check: cleanups and verbose flag]
The existing output was verbose and not always useful to the reader.
This change makes the output more compact, audits non-hardware options
and gives information
[invalid (54)]: meta/cfg/preempt-rt/common-pc/invalid.cfg
This BSP sets config options that are not offered anywhere within this kernel
(From OE-Core rev: 2d328dc0f7dd763c45444394b681d2726b4f6c83)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the kern-tools SRCREV to pickup the following change:
[
kconf_check: fix find warning
When searching for all available Kconfig files, kconf_check was using
$meta_dir instead of $META_DIR. This resulted in a truncated path and
the following warning:
find: warning: -path $oe-path/linux/ will not match anything because it ends with /.
Using the proper variable removes the warning and make sure that we
do actually search all relevant directories.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
[YOCTO #3226]
(From OE-Core rev: 5999ccebc7b071737f82709467e2a2ec152240f6)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The 3.2 kernel was lagging behind on kernel.org -stable and -rt
updates. Even though no 1.3 BSPs directly use this kernel, it should be
updated for those that may use it.
Sanity test on qemu* for -rt and standard builds.
(From OE-Core rev: 7ad1c853e252bea024043dc79d89405178393c09)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the linux-yocto/3.4 SRCREVs to incorporate the following updates:
- v3.4.17
- v3.4.18
- 3.4.18-rt29
Also incorporating the following meta branch config changes:
5bd6d0d rangeley: update include to use the new intel-dpdk feature
4b277c2 dpdk: Add feature Intel DPDK
3905e74 meta: rangeley: Enable Zlib Compression
194c5f1 meta: Add a new feature for Zlib
14cb04d meta: rangeley: Enable AES feature
8e4dbf6 meta: Add new feature for Ciphers
7e75c1f enable IPv6 Router Preference (RFC 4191) support
dfd56d1 Create IPv4 and IPv6 IPSec fragments
0a85061 rangeley: Add smp support
1190856 rangeley: Add efi support
b262e38 rangeley: Add PCI features
80c9084 rangeley: Add uio and hugetlb support
(From OE-Core rev: 7cc39567cc91955eb3014da6fdbafffa5c3148c7)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The -stable 3.4 kernel has updated versions, so we import 3.4.16 and
make that our new baseline.
(From OE-Core rev: c476046368ed87a400b3a2fd4344fc48aacc0dbc)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.4 SRCREVs to pick up the following two fixes:
218bd8d efi: Add patch to fix 32bit EFI service mapping (rhbz 726701)
b6d08f7 mmc: sdhci: Use DBG() instead of pr_warning() on large timeout
And the following meta branch config updates:
68a635b fri2: Disable GPIO_PCH for preempt-rt
2ec32d5 fri2: Add fri2-tiny support
a7b9607 fri2: Required boot config for fri2
bed2080 fri2: Remove graphics options from the core fri2 description
(From OE-Core rev: dbd49c9157f933fec9147280a48ce3cda7a697eb)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.4 meta branch with the following configuration changes
and additions:
0541ba5 meta: Rangeley Machine Created
9e3bdb7 meta: Add nfsd kernel features
da9b37d CrystalForest: Enable PCI extended config space for CrystalForest Machine.
628cbe9 meta: Add a new feature for PCI devices.
9c3a2b3 meta: fishriver: remove meta-data
(From OE-Core rev: c11bf4359697f654ff38a32bda5eae71b097d3b8)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The overrides virtclass-native and virtclass-nativesdk are deprecated,
which should be replaced by class-native and class-nativesdk.
[YOCTO #3297]
(From OE-Core rev: 7c7da0af592647be0ab9ab37a8ad2a7ce4890a46)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When DISTRO_FEATURES does not contain x11, disable GTK GUI and
also don't add gtk+ to the DEPENDS
(From OE-Core rev: 1b41a4660d0dd8f1863bb94d08562927cc108ee1)
Signed-off-by: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
commit b7e184508 (lttng-2.0: fix srcrev/pv to match the recipe
filenames) removed the
lttng-sycalls-protect-is_compat_task-from-redefiniti.patch from the
SRC_URI but forgot to remove the patch itself.
(From OE-Core rev: 6745b927a40e523cfda4ce2ca6422d69a6791e8a)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Somehow the recipe names got bumped, but the SRCREV and PVs in the recipes
didn't get updated, so they were still building old versions.
(From OE-Core rev: b3bffb0d34f99f31b65ddb886d80f71786120bbf)
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake uses PACKAGES_DYNAMIC as regexp
^ could make matching faster (and it will be more clear that we're expecting regexp not glob)
* made all those last '-' optional, use .* (or nothing)
(From OE-Core rev: 2f3ebdfa5f42dae51063b043cc4b0fbe20b40064)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This allows the files installed into /usr/libexec to be
relocated to ${libexecdir}. removed unneded prefix=/usr,
which would prevent ${prefix} relocation.
(From OE-Core rev: 10d28438c1e7d793bc398a0ad484782e5baa4877)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
THis change extends COMAPTIBLE_HOST matchings, which allows to include more
hosts with TARGET_OS like linux-gnuspe or linux-gnueabi etc.
(From OE-Core rev: 76138d4b183eff28c678ab13cb1a6da358be2340)
Signed-off-by: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
kexec-tools optionally looks for the lzma code provided by xz. Since this
is generally useful for lzma compressed kernels, add the dependency and
make builds determinstic.
(From OE-Core rev: accea64234124f25345a9288c0739c433de671f8)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Because lttng-tools installs files into /usr/lib/lttng/libexec, the test matches
and throws a false positive, so use INSANE_SKIP
(From OE-Core rev: 01300254d710c91b3dbcded9c42f6dcf21b75462)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
korg commit 42dcd1f4e [perf tools: Fix parallel build] fixes parallel
build issues that are being seen in the autobuilder.
We also have a fix from Tom:
[
perf annotate: replace 'expand' with equivalent sed expression
We don't have 'expand' in our userspace so we need to accomplish the
same thing using 'sed', which we do have.
]
So we apply it to all BSP branches and kernel types.
(From OE-Core rev: f06e7d38db35c56c71a42264361ec45fb3777a14)
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>
This recipe builds the "tiny" kernel type defined by the linux-yocto
meta-data. Support is defined for the qemux86 machine via
common-pc-tiny.scc in the linux-yocto meta branch. The resulting
kernel is 1.8 MB and boots to a serial console with with qemux86 and
core-image-minimal using the following command:
qemu -kernel tmp/deploy/images/bzImage-qemux86.bin -initrd tmp/deploy/images/core-image-minimal-qemux86.cpio.gz -append "root=/dev/ram0 console=ttyS0" -nographic
(From OE-Core rev: cf25f211ec420e1e8dd48c8e62f60deefe2c6d53)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta SRCREV to pickup the following change:
Ensure the qemux86 machine is defined in common-pc-tiny as it is
for -standard and -rt.
(From OE-Core rev: 1076910ac3cd55a3f87b5ca7a1db1e38c623480a)
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>
Updating the kernel configuration fragments to fix the following
issues:
- remove options that are no longer in the 3.4 kernel
- disable unused, but large kernel modules
- fix kconfig audit warnings for x86 BSPs
- make uprobes reusable by multiple fragments
The following meta branch commits are represented by this update:
3da1172 uprobes: split into enable and patch fragments
17ec51a meta: cleanup invalid/obselete 3.4 CONFIG options
b5cee42 meta: disable OCFS2 by default
efe937e meta: drm: tag DRM options as 'hardware'
10b5155 meta: emenlow: clean emenlow configuration warnings
a907b82 meta: add CONFIG_SHMEM to standard kernel config
(From OE-Core rev: a01bb3ec72c375c0f06006769969f63fed3ef566)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating to pickup a couple of configuration tweaks that were done
as part of a bump to the 3.4 linux-yocto tree for the beagleboard.
In particular, this updates DVI and USB settings to enable the
perhipherals out of the box.
(From OE-Core rev: 3c562b8360edf52aea6280849fa33e8a0f34742b)
Signed-off-by: Liang Li <liang.li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the machine and meta SRCREVs to the latest 3.4.x -stable
release.
See git whatchanged v3.4.10..v3.4.11 for the full changelog.
(From OE-Core rev: b164d9776802784a2fee01f2ab267dab4c2beafe)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the meta SRCREV to pickup a newer emgd for the fri2 and
sys940x.
(From OE-Core rev: abb23d987184f76fb922af15508f2e251399e3ed)
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>
Updating the meta SRCREVs to pickup the following configuration change:
594994c meta: use profiling and latencytop features in yocto bsps
(From OE-Core rev: df0197810e72337093ea6ced1c8b28eeeef8a7a8)
Signed-off-by: Tom Zanussi <tom.zanussi@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>
KVM, paravirtualization and virtio drivers are now activated
in runqemu using the kvm option flag for qemux86-64.
Host CPU features are also exported to guest OS (Yocto Linux).
Usage example: runqemu qemux86-64 core-image-x11 kvm
Implements [YOCTO #2550].
(From OE-Core rev: cbb6431b3ee9128ea15c9ae0a19e7d2998ffc561)
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>
KVM, paravirtualization and virtio drivers are now activated
in runqemu using the kvm option flag for qemux86.
Host CPU features are also exported to guest OS (Yocto Linux).
Usage example: runqemu qemux86 core-image-x11 kvm
Implements [YOCTO #2550].
(From OE-Core rev: a35d03e2eb905de4eadc9c7df5b50bff1fb7f897)
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>
uprobes depends on functionality provided by perf events. After
uprobes was enabled in the standard kernel the mpc8315 board showed
link errors due to missing perf event functions.
This problem isn't isolated to the board or powerpc arch, but all
other boards have PERF_EVENTS enabled. To fix this, we make UPROBE_EVENT
select PERF_EVENTS, and any new boards will be protected from the
same failure.
We also update the configuration fragments since CONFIG_UPROBES depends on
CONFIG_PERF_EVENTS being set, so PERF_EVENTS needs to be added whenever
uprobes are enabled.
[YOCTO #3111]
(From OE-Core rev: b681b74624d1c8c4c98b2a121828e010fc5c3a25)
Signed-off-by: Tom Zanussi <tom.zanussi@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>
Updating the meta branch SRCREV to pick up virtio and kvm guest
configuration fragments.
79947f1 meta: add paravirtualized KVM guest config fragment
3ed86ed meta: add MMIO support in virtio config fragment
(From OE-Core rev: b6b5b501fbe7158f190e887c3edc1214bb3671ed)
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>
It was reported that the kernel configuration checks for custom yocto
kernels had the following output:
NOTE: validating kernel configuration
grep: /meta-series: No such file or directory
grep: /meta-series: No such file or directory
WARNING: Can't find any BSP hardware or required configuration fragments.
WARNING: Looked at //cfg///hdw_frags.txt and //cfg///required_frags.txt in directory: //cfg//
NOTE: Tasks Summary: Attempted 375 tasks of which 367 didn't need to be rerun and all succeeded.
which is not inspire confidence in the output of the process.
Completely inhibiting the check is one option to remove the messages,
but that removes the ability see output, which can help move users to
a better or more fully configured linux-yocto based kernel.
To fix this, we have to ensure that the path to the meta-series is
always valid, and that the tools can deal with not all files existing
in the audit directory.
Since custom yocto kernels do not set KMETA (they don't have a meta branch),
we ensure that a default of 'meta' is passed to the audit ('meta' is always
valid), and that kconf_check itself can deal with an incomplete set of
input audit files.
The net result is output like this (using a defconfig with invalid options
for the kernel being built):
NOTE: validating kernel configuration
This BSP sets 19 invalid/obsolete kernel options.
These config options are not offered anywhere within this kernel.
The full list can be found in your kernel src dir at:
meta/cfg/standard/qemux86/invalid.cfg
There were 1 instances of config fragment errors.
The full list can be found in your kernel src dir at:
meta/cfg/standard/qemux86/fragment_errors.txt
The full list can be found in your kernel src dir at:
meta/cfg/standard/qemux86/missing_required.cfg
(From OE-Core rev: 4d1b7dae063ee4c35c426306d0e22f11ce112c72)
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>
This was noticed by the following warnings of files that should have been removed!
WARNING: QA Issue: kernelshark: Files/directories were installed but not shipped
/usr/share
/usr/share/trace-cmd
/usr/share/trace-cmd/plugins
/usr/share/trace-cmd/plugins/plugin_blk.so
/usr/share/trace-cmd/plugins/plugin_sched_switch.so
/usr/share/trace-cmd/plugins/plugin_kmem.so
/usr/share/trace-cmd/plugins/plugin_kvm.so
/usr/share/trace-cmd/plugins/plugin_function.so
/usr/share/trace-cmd/plugins/plugin_jbd2.so
/usr/share/trace-cmd/plugins/plugin_hrtimer.so
/usr/share/trace-cmd/plugins/plugin_mac80211.so
/usr/share/trace-cmd/plugins/.debug
/usr/share/trace-cmd/plugins/.debug/plugin_blk.so
/usr/share/trace-cmd/plugins/.debug/plugin_sched_switch.so
/usr/share/trace-cmd/plugins/.debug/plugin_kmem.so
/usr/share/trace-cmd/plugins/.debug/plugin_kvm.so
/usr/share/trace-cmd/plugins/.debug/plugin_function.so
/usr/share/trace-cmd/plugins/.debug/plugin_jbd2.so
/usr/share/trace-cmd/plugins/.debug/plugin_hrtimer.so
/usr/share/trace-cmd/plugins/.debug/plugin_mac80211.so
(From OE-Core rev: c3cff64708cb078405f5ecd9bca6801031786bc4)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When x32 is the tuning for a x86 MACHINE, the kernel should also have
CONFIG_X86_X32=y. This adds a x32 fragment that can be used to trigger
the right ABI.
The commit also contains a check for mx32 in TUNE_FEATURES, and if
present, the new fragment will be appended to KERNEL_FEATURES and
trigger the support in the kernel.
cc: Saul Wold <sgw@linux.intel.com>
(From OE-Core rev: bf689c60caa905eb8866101b9e99dd4ae246a2ca)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is sometimes useful for KERNEL_FEATURES to be set in a machine
or other configuration file. The linux-yocto recipes currently
initialize the variable, which clobbers any values set by .conf
files.
Appending to the variables allows these settings to propagate to
the kernel configuration, while maintaining the existing set of
added kernel features.
(From OE-Core rev: 7121fe8d836fc178e9ab8f0e6f8eb34a99325c81)
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>
Updating to 3.4.10 which has been soaking for a bit now, as well
as picking up the following meta commits from Tom Z:
a82db2f meta: have systemtap use kprobes and uprobes feature
d5d5b80 meta: add kprobes support to ktypes/standard
b32d373 meta: add kprobes feature
d40ed99 meta: have uprobe feature use uprobe.cfg
a69d1db meta: add uprobe.cfg
(From OE-Core rev: fb71d8c3ab735739baedcb5c8c44b028890d8a5e)
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>
The first import of 3.4.9-rt17 only picked up part of the import due
to a merge conflict with the modified files, and then SRCREVs being
generated from the pre-merge commit.
This SRCREV update picks up the rest of the modified files for full
-rt support.
(From OE-Core rev: d1ec0b64018dafaa6e47233b3465fbe4189e6280)
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>
Bumping the 3.4 kernel to -rt17.
As well as picking up the normal set of bug fixes, this update fixes
a boot issue that was introduced during merging of kernel.org -stable
updates into the -rt branches (in the timekeeping code).
(From OE-Core rev: 0c060a81ade685aee5492e0273f199850dffaf76)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.2/3.4 linux-yocto SRCREVs to pickup the following fix:
arm: Fix linking errors with binutils 2.23
We end up with linking errors on arm using latest binutils
because we are linking asm generated objects which use -march=all
generating different attributes into object and use some c objects
e.g. misc.o which use different march therefore generating a
different set of attributes into object. When linking is done
the ld complains since it finds incompatible attributes and ends
up with errors like
error: DIV usage mismatch between arch/arm/boot/compressed/head.o and
output
error: DIV usage mismatch between arch/arm/boot/compressed/misc.o and
output
error: DIV usage mismatch between arch/arm/boot/compressed/decompress.o
and output
error: DIV usage mismatch between arch/arm/boot/compressed/lib1funcs.o
and output
This patch fixes it by providing correct march to assembly routines
which than matches with output of ld.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(From OE-Core rev: e67ffb708522a622d149641ea09b249259ed3fb4)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Importing the following tools SRCREV:
kgit-meta: exclude explicit branches from name calculations
kernel branches are constructed during patching of the tree by
constructing a '/' based hierarchy of names as each branch
directive is encountered.
But if a "branch $name $branchpoint" is used, the entire branch
name is supplied so no additions to the hierarchy should
happen. As such, that type of branch command should not be part
of branch name calculation and preparation.
(From OE-Core rev: a3884938233c8a2d6861b1d4e6be5b9824d3b131)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When patches fail to apply, the status of all pending patches should
be exported to the logs and to the user. Currently, a missing export
of GUILT_BASE makes it look more like an internal error, than a 'normal'
patch failure:
| [ERROR] unable to complete push
| pending patches are:
| Patches directory doesn't exist, try guilt-init
With this variable exported, we have this:
| [INFO] validating against known patches (qemux86-standard-meta)
| error: patch failed: Makefile:2
| error: Makefile: patch does not apply
| To force apply this patch, use 'guilt push -f'
| [ERROR] unable to complete push
| pending patches are:
| links/files/0002-makefile-patch.patch
(From OE-Core rev: b2b2512cbc4196fa0f814be3677517dab30e5b52)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
commit 7a79f7412 [linux-yocto: make KBRANCH the exception and not the rule]
ensures that a request branch is always built. The implementation of this
guarantee is a branch switch before the build starts. But that switch may
be before all patches are applied. If the proper routines are not called,
no patches can be applied to the tree.
Updating the SRCREV to pickup this fix:
updateme: use branch command when forcing branch switches
When forcing a branch switch to the desired branch we should be
using the proper 'branch' command. Since without this call, the
proper variables will not be set, and patches can't be applied
to the tree.
(From OE-Core rev: bede3086cb9ab0f79fb7775528b646817b2b9af0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The qemu-config initscript was only starting oprofile-server, so move it
to the oprofileui-server recipe.
(From OE-Core rev: 3063126e2c8ec72e900a48f7048aaf9662606792)
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>
Increase SRCREV to include an upstream patch that fixes the configure
script so that the server can be built separately without gtk+ and
avahi-ui, and create a separate recipe for the server.
Also fix the RDEPENDS so that oprofile actually gets pulled in by the
client and the server.
Part of the fix for [YOCTO #1690].
(From OE-Core rev: 971fbbd50ae147805fc7498b72a046be5bffc3c7)
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>
Since kernelshark depends on trace-cmd, there is no reason to
install and package the plugins that are part of trace-cmd.
[YOCTO #238]
(From OE-Core rev: d6614b0ac7c83b2e17e68903a85fc8374e936c1a)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As discussed on the mailing lists, using a suffix to package names is
hard and has lead to many recipes having to do PKGSUFFIX games. Its
looking extremely hard to scale nativesdk much further without hacking
many recipes.
By comparison, using a prefix like multilib does works much better and
doesn't involve "hacking" as many recipes. This change converts nativesdk
to use a prefix using the existing multilib infrastructure.
(From OE-Core rev: 81813c0e322dc04ce4b069117188d8a54dfddb8c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
perf depends on bison and flex for event parsing - add them as
dependencies.
(From OE-Core rev: f04b0ddb7a392425ba5890026564bc3521a32c67)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To support custom repositories that set a SRCREV and that only have
a single master branch, do_validate_branches needs a special case
for 'master'. We can't delete and recreate the branch, since you
cannot delete the current branch, instead we must reset the branch
to the proper SRCREV.
(From OE-Core rev: de5bb5879fa3282c46dc1ede36af34eaab8f647f)
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>
In the kernel's tools/perf/Makefile CFLAGS was previously hard coded to
contain "-I/usr/include/slang" to work with hosts that have
"/usr/include/slang/slang.h" as well as hosts that have
"/usr/include/slang.h". This path can cause compile warnings like:
cc1: warning: '/usr/include/slang' doesn't exists.
or
cc1: warning: include location "/usr/include/slang" is unsafe for
cross-compilation [-Wpoison-system-directories]
Then in some cases warnings become errors if WERROR is enabled hence
build errors.
In coordination with a kernel fix, we can fix this error for all
kernels by modifying the perf Makefile within the staged kernel
source.
(From OE-Core rev: 4e0daf05ed04e9fb4343032c6290a379f53b89f3)
Signed-off-by: Liang Li <liang.li@windriver.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>
kmod will fail to build with the following error because O_CLOEXEC is
not defined:
| libkmod/libkmod-module.c: In function 'kmod_module_get_initstate':
| libkmod/libkmod-module.c:1640: error: 'O_CLOEXEC' undeclared (first use in this function)
| libkmod/libkmod-module.c:1640: error: (Each undeclared identifier is reported only once
| libkmod/libkmod-module.c:1640: error: for each function it appears in.)
| libkmod/libkmod-module.c: In function 'kmod_module_get_refcnt':
| libkmod/libkmod-module.c:1754: error: 'O_CLOEXEC' undeclared (first use in this function)
| libkmod/libkmod-module.c: In function 'kmod_module_get_sections':
| libkmod/libkmod-module.c:1913: error: 'O_CLOEXEC' undeclared (first use in this function)
| libkmod/libkmod-file.c: In function 'kmod_file_open':
| libkmod/libkmod-file.c:282: error: 'O_CLOEXEC' undeclared (first use in this function)
| libkmod/libkmod-file.c:282: error: (Each undeclared identifier is reported only once
| libkmod/libkmod-file.c:282: error: for each function it appears in.)
Since we are only using kmod-native for depmod, and it's a non-threaded
user of this libary being built this should be safe to override O_CLOEXEC.
Keep in mind this is ONLY effecting the native builds and not what is
being shipped in the root file system.
(From OE-Core rev: edcb57fe308979cc5b92359d064e32bb70d4ad76)
Signed-off-by: Matthew McClintock <msm@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This helps in appending to this regexp from bbappends
coming from other layers who want to leverage linux-yocto
with minimum tweaks by using a standard prefefined machine
from linux-yocto
(From OE-Core rev: 32ba716e71fb7a16f13c83ab6c8cc51de56b3be2)
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>
Bumping the meta SRCREV to pickup this fix:
meta: rename virto.scc to virtio.scc
The virtio configuration block is misnamed. BSPs that include it with
the proper name, now throw an error (as they should). So fixing the
name of the fragment fixes the build.
(From OE-Core rev: c6b335099224d590109a8bcda22bf54c597c7eee)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To streamline the creation of build time branches (branches that are
not always present in the upstream kernel repository), linux-yocto-tiny
should specify a default kernel branch. By setting the default branch
(KBRANCH_DEFAULT) and also setting the build branch (KBRANCH) to that
default, the tools will allow the board description to be processed
and no branching forced.
(From OE-Core rev: 07e422138b89e4f4a0cc911db70e2ce953b7623b)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removes a make install-python_ext when not present since
older versions of perf lack this install rule
This also fixes a library issue on older kernels building with
a newer toolchain where libaries that would previously be pulled
in are no longer. So we add them manually.
(From OE-Core rev: 70b17a893bd2e1bbba8ea16619b02a60e7c4b8d8)
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>
The kern-tools scripts can support a meta branch and directory of a name that
isn't "meta", but they need the name passed through the environment variable
KMETA. ensuring that KMETA is exported in the shell environment sets the stage
to support flexible meta branch name.
(From OE-Core rev: 9b90c8ace04c88ac6105f0bf686f9abc70fe8074)
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>
A BSP specific KBRANCH assignment is no longer a required
element to locate and build a yocto kernel. As such we can
set the default kbranch, and remove all other explicit
assignments.
KBRANCH is still used, and if it is changed from the
default, that branch will be built.
(From OE-Core rev: 7984a9f6ccd00bf282c9eedab7ab933add68448c)
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>
The kernel branch is no longer required by the yocto-kern-tools
to locate BSP feature descriptions (it is the MACHINE:KTYPE
descriptor), so we no longer require that the BSP branch be
explicitly set.
If a kernel branch is explicitly set, it is now used to trigger
a checks to ensure that the branch really is being built.
Otherwise the branch that the machine description creates will
be built (just as it always was).
This further simplies the use and configuration of a linux-yocto
based kernel recipe.
(From OE-Core rev: 3cac3ce65abae9dc253641a2004440a2b38fd44d)
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>
Updating the linux-yocto 3.4 recipe with consolidated fixes, BSPs
and cleanups.
From the kernel meta branch:
28bcd46 meta: move emgd features to staging
6c01949 meta: Crystal Forest Machine Created.
3c19c4d meta/qemuppc: remove redundant profiling options
a5da4d5 meta: kgdb: update configuration for out of box functionality
1d13e00 meta: update status/series and patches for v3.4
b96c408 fsl-mpc8315e-rdb: replace leading dot with hash in cfg file
7c9a3b0 usb: fix scc and cfg filename collision with ktypes/base/
aa0e1f6 kconfig: make CONFIG_BLOCK=y part of base config
3d1a2f2 kconfig: add tty/serial file to hardware listing
60b600f routerstationpro: specify chosen filesystems in audit input.
8b5c8c7 routerstationpro: add config data for audit purposes
d7ae8fa meta: add ath79 Kconfig to hardware listing.
And from the standard branch:
c77666c powerpc: uprobes: removed external declaration of uprobe_get_swbp_addr.
c262f3e powerpc: Uprobes port to powerpc
d40e73d powerpc: Add trap_nr to thread_struct
6a64190 Revert "This is the port of uprobes to powerpc. Usage is similar to x86."
e422119 Revert "powerpc: uprobes: removed external declaration of uprobe_get_swbp_addr."
d4ef82f keys: kill task_struct->replacement_session_keyring
1cc141e keys: kill the dummy key_replace_session_keyring()
090ca45 keys: change keyctl_session_to_parent() to use task_work_add()
61bc7a8 genirq: reimplement exit_irq_thread() hook via task_work_add()
5ee34dd task_work_add: generic process-context callbacks
70754de move key_repace_session_keyring() into tracehook_notify_resume()
6f70bc1 powerpc: uprobes: removed external declaration of uprobe_get_swbp_addr.
e5f6a4c This is the port of uprobes to powerpc. Usage is similar to x86.
2bc4597 On RISC architectures like powerpc, instructions are fixed size. Instruction analysis on such pl
8893371 perf probe: Detect probe target when m/x options are absent
544d531a perf probe: Provide perf interface for uprobes
103b503 tracing: Fix kconfig warning due to a typo
9bb012e tracing: Provide trace events interface for uprobes
b9b7281 tracing: Extract out common code for kprobes/uprobes trace events
91f0360 tracing: Modify is_delete, is_return from int to bool
a8600f2 uprobes/core: Decrement uprobe count before the pages are unmapped
a252056 uprobes/core: Make background page replacement logic account for rss_stat counters
3efc15b uprobes/core: Optimize probe hits with the help of a counter
20f3d76 uprobes/core: Allocate XOL slots for uprobes use
77bfad8 uprobes/core: Handle breakpoint and singlestep exceptions
7196d9a uprobes/core: Rename bkpt to swbp
c99bc18 uprobes/core: Make order of function parameters consistent across functions
7e9be99 uprobes/core: Make macro names consistent
c4247f2 uprobes: Update copyright notices
f066ff9 uprobes/core: Move insn to arch specific structure
e91cf65 uprobes/core: Remove uprobe_opcode_sz
942b91c uprobes/core: Make instruction tables volatile
56c1e99 uprobes: Move to kernel/events/
0a7ad1c uprobes/core: Clean up, refactor and improve the code
3760d62 uprobes, mm, x86: Add the ability to install and remove uprobes breakpoints
Two BSP updates:
- Crystal Forest Machine has been added
- routerstationpro configuration updates for 3.4
(From OE-Core rev: bd05dcb634cbb4022b4189985585f73c86f01fae)
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>
The v3.4.7 -stable update has been released, updating all in-tree
BSPs to this new baseline.
(From OE-Core rev: 89a0587d5affe8d8986efce7738b7b3774792154)
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>
Add in a workaround to avoid host infection detection build failures
from the slang include directory in perf. I'll defer to Bruce to
fix this properly but we need a workaround now as this is breaking
builds.
(From OE-Core rev: 4fd4b2eafb5f4ff2ef85d7f5ff3238a41c34313b)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This change breaks firmware loading on 64 bit platforms. This therefore
reverts commit ce2665b6ae77770d69ffbc4d45c96ce829d16738.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Latest version is 1.0.0 but in rc4 for now.
(From OE-Core rev: 6172f1fed9850180a3a84ca62cc0741d132031e4)
Signed-off-by: Radu Moisan <radu.moisan@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is considered good practice to use the build system provided
variables instead of directly specify hardcoded paths.
(From OE-Core rev: ce2665b6ae77770d69ffbc4d45c96ce829d16738)
Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is considered good practice to use the build system provided
variables instead of directly specify hardcoded paths.
(From OE-Core rev: 095f9c056373a252c0ba2679d8e6f4ad932a958d)
Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add pythonnative to the inherits list
(From OE-Core rev: b3ef5a986e3bc1a29ba2b4a25d063a0267e2f72f)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.4 kernel to the latest -stable release and updating preempt-rt
to 3.4.4-rt14.
Tested on qemu*
(From OE-Core rev: 955fd1408713634d9a96b00ef53ed0a6a188e9fe)
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>
Without this it can't reautoconf or run configure since it depends on pkg-config.
(From OE-Core rev: 7673cd498a50f59b0e2954341de0e8c6913d374f)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.4 meta SRCREV for the following fixes:
949fddd meta: crownbay.scc change emgd branch name
cd0721a yocto/emgd: emgd 1.14 driver
c2b5ee3 meta: disable CONFIG_MTD_NAND_VERIFY_WRITE
004cadb meta: kmemcheck: 'other' configs turning on CONFIG_FUNCTION_TRACER
(From OE-Core rev: c192b2da74b20f091b6191349ceb1cf195aae8c6)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add pythonnative to the inherits list
(From OE-Core rev: d27cd814162fde3362278435a6842928310c2704)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The bb and os modules are always imported so having these extra import calls
are a waste of space/execution time. They also set a bad example for people
copy and pasting code so clean them up.
(From OE-Core rev: 7d674820958be3a7051ea619effe1a6061d9cbe2)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.0 SRCREVs to pickup the recent perf scripting fixes.
cef17a1 perf: add sgidefs.h to for mips builds
3258da3 perf: change --root to --prefix for python install
1f9c25b perf: add 'libperl not found' warning
f2b1bf1 perf: use pkg-config instead of python-config
568e05f perf tools: Add support to install perf python extension
7e47f81 Revert "perf: hard-code NO_LIBPERL/NO_LIBPYTHON"
(From OE-Core rev: 20405bdab18b7a2b101f818e72863d289d5945e4)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
On 64bit systems dtc will still install libaries in /usr/lib
unless we havet this override
(From OE-Core rev: b60579e66601ba60669a9e1194409fcd8b80530e)
Signed-off-by: Matthew McClintock <msm@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a new feature named 'perf-tui'. Adding this into the
PERF_FEATURES variable in perf.inc will enable the perf TUI (Text-base
UI) user interface on a target, which adds libnewt and turns on the
perf text UI options in perf, if perf is included in an image.
If 'perf-tui' isn't named as a feature (the default), the perf TUI
will be disabled and unavailable.
(From OE-Core rev: 4fd8a550886f02189e4ed127d0a2f16e92f8474c)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a new feature named 'perf-scripting'. Adding this into the
PERF_FEATURES variable in perf.inc will enable perf scripting on a
target, which will turn on all the language bindings currently
available in perf (Perl and Python), if perf is included in an image.
If 'perf-scripting' isn't named as a feature (the default), all perf
language bindings will be disabled and unavailable.
(From OE-Core rev: fc0661041436013b9099dbd659994a2b8b292c19)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a perf.inc to contain utility functions and definitions and to
avoid cluttering up the main recipe.
(From OE-Core rev: 414d00be5b350ea84fc7e1ff690f78b3396cfcd0)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.4 SRCREVs to pickup the following changes:
6297e4c perf: add sgidefs.h to for mips builds
69b7817 yaffs: add leading underscore to mtd_info function names
160f1ac yaffs: change type for mode to umode_t
2d875e8 Unionfs: use mode_t
(From OE-Core rev: 9d75c34948f5d961cff9d72fbaa628ff58821cc7)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating SRCREVs for the following fix:
Author: Tom Zanussi <tom.zanussi@intel.com>
Date: Tue Jul 10 09:38:40 2012 -0500
perf: add sgidefs.h to for mips builds
Allow Python.h to find the definitions it needs on mips i.e. get rid
of the error: "_ABIN32" is not defined.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
(From OE-Core rev: 04396899dc7973261404d5fbec3f85aa03a32e03)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This shouldn't be unconditional - a later patch made it so, but that's
not yet pulled in. In the meantime, to fix build failures remove the
unconditional install.
(From OE-Core rev: dcc43c34bfa9304233ecfd3f518a84ddfdc2fd90)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libexec/perf-core contains all the pre-canned scripts and modules
needed by both the Perl and Python bindigs. Add libexec/perf-core
along with all the pre-defined perf scripts underneath it.
(From OE-Core rev: 00f9e8aed9f111d351c2dc71cd8605ccbd11f68f)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add support to enable the perf Perl binding.
The build depends on perl-native to retrieve the configuration
settings needed for the binding. cpan-base adds some useful functions
like is_target() and get_perl_version() that we need for
PERLCONFIGTARGET and related settings, which allow us to use the
target's Config_heavy.pl settings for ExtUtils:Embed when building for
the target.
Also adds the perl-modules dependency to give the target the perl
modules that scripts using the binding need.
(From OE-Core rev: 73a8eed010a821fc4f5c0e71ef749938ed780b44)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add support to enable the perf python bindings. The combination of
these changes and the changes in the python-config sections in the
kernel Makefile enable all the python bindings currently available in
perf.
(From OE-Core rev: 487c3a72f0ac7121b79d2f78b81f1d4732bc258a)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[YOCTO #1614]
Add the kernel headers to the kernel-dev package. This packages what was
already built and kept in sysroots for building modules with bitbake.
Making this available on the target requires removing some additional
host binaries.
Move the location to /usr/src/kernel
Before use on the target, the user will need to:
# cd /usr/src/kernel
# make scripts
This renders the kernel-misc recipe empty, so remove it.
As we use /usr/src/kernel in several places (and I missed one in the
previous version), add a KERNEL_SRC_DIR variable and use that throughout
the class to avoid update errors in the future.
Now that we package the kernel headers, drop the
kernel_package_preprocess function which removed them from PKGD.
All *-sdk image recipes include dev-pkgs, so the kernel-dev package will
be installed by default on all such images.
(From OE-Core rev: 6125ea40d4483965f793bd847b3ce14b668a5b1e)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
CC: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With recent kern tools changes, having a meta branch is opt-in. The
other linux-yocto recipes were updated, but linux-yocto-tiny was
missed.
Without specifying a meta branch, the kernel configuration audit
won't return any useful results, and throws a warning message.
WARNING: Can't find any BSP hardware or required configuration fragments.
WARNING: Looked at //cfg///hdw_frags.txt and //cfg///required_frags.txt in directory: //cfg//
NOTE: package linux-yocto-tiny-3.2.18+git1+ee78519365bdb25287703bbc31c06b193263c654_1+27b68a93eb791e830da8d3a2c0fc99780897ad89-r3.0: task do_kernel
(From OE-Core rev: 29dbe7d7ba66c66e9e5c8dc438f89d9b46c509a0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating preempt-rt in the 3.4 kernel to the latest upstream version
3.4.4-rt13.
(From OE-Core rev: f5ed8bc876fd24e4f08d29da06454037eec818e6)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the kernel version to v3.4.4 and importing the following
meta branch commits:
9b7c74b meta: bump kver to v3.4.4
8231dec ck: relocate config post patches
26b965e net_sched: remove dupicate configuration option
df8bf19 meta: remove non applying routerstationpro patch
292d8ea arm: import upstream versatile io.h fix
f4824b1 net_sched: select ACT as a dependency of INGRESS
30ae722 cgroups: delete obsolete namespace option
51f94f0 meta: add qemumipsel mapping
Built and boot tested on qemu*
(From OE-Core rev: 3d33b8c8b3be5dcdac30c115b9fec427269db2b4)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta branch with a board description and configuration
that can be found from the linux-yocto recipes without doing a
MACHINE -> KMACHINE mapping.
From the meta branch commit:
The mti malta board description for a little endian config can't
be found by default unless it has a matching KMACHINE, or the
KMACHINE is set in a kernel recipe. In this case, it is easier to
just add qemumipsel in the KMACHINE list, so the recipe doesn't
need to do the mapping.
The little endian mips support reuses everything but the endianess
settings from the big endian mti malta board emulation.
This change adds the required mappings and SRCREVs, but does not
update the machine compatibilty, since official support is still
pending. The compatibility can be set in addon layers until that
time.
(From OE-Core rev: de2535b2bb47b80bdaeb3053b0ac0d1bbb9c5d53)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When making changes to kernel.bbclass, it would be nice not to have to
manually change the PR of every linux-yocto*.bb file that requires it.
Move the "require kernel" line to linux-yocto.inc and update the
linux-yocto recipes to use INC_PR.
(From OE-Core rev: 7a41d96c946029aeec03cd26f326bc6ca26e74fd)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In tree linux-yocto 3.0 boards indicate that they are BSPs via
the older/obsolete syntax "scc_leaf". This line in their board
description is detected by the build process and is used to find
the BSP description and the kernel type they use as their base.
To work with the latest kern tools, the BSP descriptions should
be updated to "include <ktype> branch <machine>" to acheive the
same result.
All trees newer than 3.0 already have this change and do not need
to be updated.
(From OE-Core rev: e32c993859337964033a285922dac3971e5add2d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
including following enhancement:
* support multi-dtb build
* skip dtb build and install when KERNEL_DEVICETREE is empty
* print a warning message when specified dts file is not available
(From OE-Core rev: 66f7921f34dfa8b3c7f8f7184715214164f3f8b0)
Signed-off-by: Zhenhua Luo <b19537@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update the systemtap recipes to the recently released 1.8. Remove a
couple patches whose changes are already present in the new version.
(From OE-Core rev: 1c5a127d075ebf78b70d14e3ca1d0ff640a80cb8)
Signed-off-by: Wade Farnsworth <wade_farnsworth@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.4 SRCREVs to pickup build fixes for -rt, feature backports,
and a second set of 3.4 configuration audit results.
d65afd9 profiling: delete reference of obsolete CONFIG_X86_UP_APIC
9431490 meta: fix net_sched.cfg include
242149d meta: add CONFIG_VIRTIO_CONSOLE to virtio configuration
671a822 meta: resync series -> branches
e044ee1 rt: integrate patch to fix compile fail on certain configs
edac822 ktest: update with v3.5 content
182b8da net_sched: Add CODEL queue management algorithm.
c6adcd9 net_sched: move content out of cgroups dir
c8edb3e sys940x: branch before merge
6d06257 ext3: delete duplicate enablement settings.
6a5a2f8 ipv6: build in the core support vs. it being modular
e106230 ipv6: make standard and RT share a common config block
42996fb netfilter: coalesce bridge settings for standard and RT into a common file.
2b62fea netfilter: coalesce IPv6 settings for standard and RT into a common file.
d1c38c8 netfilter: coalesce IPv4 settings for standard and RT into a common file.
b5f9c7c preempt-rt: align with standard kernel type for basic cfg
ea33e01 cfg: move devtmpfs cfg/scc to cfg/fs dir
517eda4 preempt-rt: combine two config fragments into one
171a30a cgroups: re-enable net_traffic config fragment
86a599d cgroups: delete old blkio patches
8be6e5b netfilter: add comment documenting external bb use case
90e06bf x86[_64]: align with korg on HOTPLUG_PCI, HOTPLUG_PCI_PCIE and PCI_MSI
e103f7c seccomp: backport of BPF syscall filtering from v3.5
[YOCTO #1694]
(From OE-Core rev: 0c522dfabbf6b25488865a7653ea30f994d8177f)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The 3.4 kernel adopted the qemu machine name for the kernel branches, so
the 3.4-rt recipe needs to be updated to reflect that.
(From OE-Core rev: 9cec3f55cd2381c5d69c6f0911bd985311e2baf9)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the linux-yocto 3.4 SRCREV to import the -stable update
to v3.4.3.
(From OE-Core rev: 529d07cf663e671140ea99877e73db091d5a9734)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.4 kernel tree with some initial results of the 3.4
kernel configuration audit and refresh. This is the start of the
3.4 kernel configuration policy update and includes a refresh / update
with respect to kernel.org defaults and new categorization of
configuration fragments.
0f6975b Sched: Import base BFS-423 for v3.4
c517c5c cfg: strip off redundant path prefixes
689fd20 cfg: create timer subdir for HZ and HPET related settings
5367b46 cfg: add a fs dir for filesystem related configs
67a784b x86/x86_64: disable MTRR sanitizer
5da51ea x86/x86_64: consolidate ACPI and EFI settings
7627402 x86/x86_64: enable CONFIG_NO_HZ=y by default.
9ca6026 mips: select HZ=100 by default.
149efc6 arm: select HZ=100 by default.
29c9fc7 x86/x86_64: use HZ=1000
700b8b5 x86/x86_64: enable boot mem corruption checks; align with korg defaults
bbd054d x86: enable CONFIG_HIGHPTE=y by default.
2569871 x86: align to korg defconfig on IRQ fixups and microcode
ec5cdc2 x86/x86_64: enable SMP by default
b9932fa cfg: relocate/add a frag for HPET / RTC enablement
f9645f5 8250: separate out the 8250 configuration from feature dir
5e8fea0 bsp: tie cfg/x86.scc into all "KARCH i386" boards
4020ade cfg: make a common landing ground for ARCH=x86
e126316 cfg: add basic HZ fragments
4a8627b cfg: delete instances of any reference to dmesg buf size.
0794c16 routerstationpro: lib/kobject_uevent: switch to uevent_sock_mutex
[YOCTO #1694]
(From OE-Core rev: 92ff386b950879255802d3a74590fef36d160ba4)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the kern-tools SRCREV to pickup the following functionality:
- buildall: provides the ability to build all kernel branches
without a build system, only a cross compiler and configme
are required.
- robustness/cleanups: obselete/unused code removal and general robustness
fixes from Paul Gortmaker and Bruce Ashfield
The following kern-tools commits are part of this series:
b8dfd3d buildall: add whitelist/blacklist support
0ef039c configme: catch errors found during fragment sanitization
5b6498c buildall: remove all instances of it using/reading scc files
2e57550 buildall: support semi seamless restarts
4b5dd4d kconf_check: simplify cmdline args, dont store data per branch
58fbb6e configme: relieve it of all knowledge of scc files
a03e291 configme: strip out alternative meta series logic.
96d2bcf kgit-init: check for valid branchpoint
5598db6 buildall: allow a max cap on the number of builds done
b46abec buildall: add support for randomizing build order
68a04e9 buildall: dont copy failed build logs into main build dir
5575d85 buildall: script to independently build all board kernels
86d6200 configme: delete unused variable
8d4e29d configme: delete unused KPROFILE setting
7e15436 configme: ensure we have a valid machine type set
152b9cb scc: remove depreciated/unused commands
bb4e96a scc: allow includes within conditional statements
7da7951 configme: derive path to tools from $0
152dc45 configme: test for BUILD_DIR != ""
129f7b0 kgit-scc: add warnings about bad input args.
e977662 kgit-scc: add text for no arg and invalid arg case.
[YOCTO #843]
(From OE-Core rev: be3cff86d55db6255e036d68e943e527802b4f4c)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is now the authoratative repository, taking updates.
The latest has a couple updated license files, vs. the previous
srcrev that was used.
(From OE-Core rev: b9d42ec94dfcbe92ce2a857045a0e3678c05c26c)
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-libc-headers no longer needs its own ARCH mapping code,
since the mapping done in kernel-arch works and we can
consolidate all arch mapping code in a single place.
(From OE-Core rev: 7d73cfb2ae24ad2b694244c56dd4648ba7e2df11)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
perf has been moved to a standalone package, making linux-tools.inc
unecessary. It can now be removed and recipes that included it
updated.
(From OE-Core rev: b485f3e0e55ad62079ed0913970ff0620f4808ea)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
perf has been coupled to the kernel packages via kernel.bbclass.
While maintaining the build of perf out of the kernel source tree
is desired the package coupling has proved to be awkward in
several situations such as:
- when a kernel recipe doesn't want to build/provide perf
- when licensing of dependencies would prohibit perf and hence
the kernel from being built.
To solve some of these problems, this recipe is the extraction of
the linux-tools.inc provided perf compilation into a standalone
perf recipe that builds out of the kernel source, but is otherwise
independent.
No new functionality is provided above what the linux-tools.inc
variant provided, but the separate recipe provides baseline for
adding new functionality.
(From OE-Core rev: ab883d0c1a05bd99e97e5d71bc7bed05cb1ae8c8)
Signed-off-by: Liang Li <liang.li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Adding the 3.4 variant of the linux-yocto-rt recipe. This updates
to 3.4.1-rt9, and builds and boots on the supported targets.
(From OE-Core rev: 7f007994cbc5f188439ad2b26f60dbcc1c2763bd)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.4 SRCREVs to pickup a yaffs2 update and the removal
of a feature that was required in the 3.2 kernel tree.
1/2 [
meta: rc6: remove rc6 patches for snb
The sandybridge rc6 patches are part of the released v3.4 kernel.
Hence there is no need to keep these patches in the 3.4 linux
yocto kernel repository.
(From OE-Core rev: 7822565a3a3ae906112c88f7e59f396c7fdabd4c)
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
]
2/2 [
yaffs2: update core support
Uprev yaffs2 to latest version as of 2012-05-29
To include the following commits:
662466a yaffs2 checkpointing: Add further checkpoint data sanity checking
d9cae0a yaffs2: Make checkpoint block scanning skip bad blocks.
eb12d56 Remove trace that should not be in mounting.
9ee5d06 yaffs for u-boot: Cleanups to make patches acceptable for u-boot
83d9993 Merge remote branch 'origin/master'
07353dd Clean up checkin. Do not use
00ebf30 Update timothy test Makefile
1658295 yaffsfs: Allocate directory searches from a table rather than via malloc.
8dae7f1 Fix compilation of python tests.
14ff4e1 yaffs u-boot: Fix problem if an illegal nand chip number is entered.
8b34846 Set up u-boot glue code and patching scripts.
1a17e3a Add more descriptive comment for using the yaffs commands.
80f8530 Add files to hook up yaffs direct to u-boot
95ff7ef Merge branch 'master' of ssh://www.aleph1.co.uk/home/aleph1/git/yaffs2
e49491a Put both the summary and checkpoint version stamps together, update checkpoint version
468d72b Fix compilation of mkyaffsimage and mkyaffs2image
87166df Fix resizing of large files.
eeb0f17 Fix summary header validation
d308180 Add a summary header
7862c13 Remove extra line from banner.
d14c6a6 Add script to handle common Linux and direct files
6518138 Change Makefiles to support new way to structure yaffs_strxxx renaming for yaffs direct
8429784 Update README about linux patching
6ee2533 Update Makefiles for new sed-based way case-insensitive handling
2369fad Set up new version of case insensitive code using sed
4d8ae2f Add large file support changes to yaffs_vfs_single.c
ce0a5fb Merge branch 'big-files': Merge in large file support
80d031a Add Waldemar's patches for Linux 3.2
a7ae50c yaffs large file support: Fix max file size issue that prevented the scanning working.
a7cb3a3 WIP Changes to tests
2360446 yaffs large file support: Add more tests
0ed6086 yaffs large file support: Saves and restores large files fine under yaffs direct.
fc4028b large file storage WIP. Can save and verify a large file under yaffs direct.
20de150 WIP large file support
b4d93e2 First cut of changes to support large files.
Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The 3.4 kernel is released, and is the default for qemu* builds, so
we can safely update the default libc-headers version to 3.4.
Built and booted for qemu*
(From OE-Core rev: 3e57510bb11b350fbe15cae2fb5bf851956061ac)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove a stray character at the end of the meta SRCREV.
(From OE-Core rev: 009f7734e880084a5b01d8377cb006dc82f1d278)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the kern-tools SRCREV to pick up the following fix:
Out of tree feature descriptions (.scc files) take two forms: normal
features and BSP descriptions.
A normal feature is detected and added to the end of the current machine
being processed. During tree processing, it's configuration and patches
will be applied.
A BSP description on the other hand must be matched based on three
critera (which are in the .scc file via "define <foo>"):
- machine
- kernel type
- architecture
Since features that define machines are only explicitly added, they
are removed from the list of features that should be automatically
added.
The criteria for removing them from the auto-add list is the
definitions found in the .scc file. The existing check was simply
for KMACHINE anywhere in the file. This meant that a conditional
or even a comment containing that phrase would exclude a file.
Properly anchoring the KMACHINE test to "^define.*KMACHINE" fixes the
problem of overly agreesive exclusions.
(From OE-Core rev: 75a973328d50ef3c007edb7a471ea77fb97911ea)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating meta to move Kernel Features out of the BSP and add to
the Cedartrail Machine branch.
(From OE-Core rev: e44b616309dd8e442c7cd13c4c0b1a4ee41ac40f)
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>
Bumping the 3.2 SRCREVs to pickup the following configuration changes for
the new chiefriver BSP and the existing fri2 machines:
5b4c9dc fri2: update base config
cdfbb50 fri2: add usb-mass-storage to standard and preempt-rt
3c1af06 fri2 update: drop NETDEVICE, e1xxx, usb-mass-storage, add iwlwifi feature
26a4d79 iwlagn: Correct a comment typo
ade9c57 iwlwifi: Add a feature for iwlwifi
571b6cb fri2: Configuration update (usb, wifi, i2c)
b257485 meta: add tmp/rc6 feature
24c6494 chiefriver: create initial BSP infrastructure
All branches are also updated with the following fix:
1ce6700 efi: Add patch to fix 32bit EFI service mapping (rhbz 726701)
(From OE-Core rev: 0bef6360305c7d8cfa48e8132b3eeb2ac1b4236e)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
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>
Introducing the 3.4 kernel recipe. At this point there are three
supported kernel 3.4, 3.2 and 3.0.
Build and boot tested on qemux86, qemux86-64, qemuarm, qemumips and
qemuppc
(From OE-Core rev: f85c3f727fd326fe6dd2f2c2b68c692515867737)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To avoid mapping machine names to kernel machine names in recipes,
we can define multiple KMACHINE names for a single in tree board.
This allows the tools to match a board description to multiple
different MACHINEs.
As a result, we can remove the explicit KMACHINE mappings from
the linux-yocto recipes and allow the KMACHINE=${MACHINE} default
to handle mappings. Individual recipes an bbappends can override
this as required.
(From OE-Core rev: d3dc05a4b808136876cb257a568737abfaceeadd)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With the introduction of the 3.4 kernel recipe, the 2.6.37 kernel
recipe is removed, keeping the supported list at three kernels.
(From OE-Core rev: 96ae45be42dcab338e9f8e3aebd2217146a79f87)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.0 kernel SRCREVs to integrate the v3.0.32 -stable
release.
(From OE-Core rev: be8b5332ddc8e3e1a1fb8fb119c5ab5c7c290c99)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.2 kernel SRCREVs to pickup the -stable update
to v3.2.18.
(From OE-Core rev: 11f2e4b0dcfc66cd9982471173ba42c6e31b470a)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the kern-tools SRCREV to pick up fixes that remove unused
code, transition code (tree format changes) and to remove assumptions
about branch and directory naming.
There are no user visible changes with this update, but the plumbing
changes will be used in future updates for more generalized support.
The commit details are below:
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Fri May 11 12:13:12 2012 -0400
kgit-publish: remove --remote option
The ability to publish and automatically push a repository was
never used, and is error prone. The complexit isn't needed in
the script, so removing it is the best option.
An explicit push after tree publication is suggested, or a
wrapper script (specific to a particular infrastructure) around
this script.
(From OE-Core rev: 5b1a096211ebeb8dac4f1a39d96ae2f9a3d00634)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Fri May 11 12:04:09 2012 -0400
kern-tools: remove unused code, scripts and transition code
The period of supporting old trees with a different meta
branch name and directory structure are gone. So the cleanup
and removal of the old structure can be completed.
The meta branch and directory are now controlled via command line,
or via the KMETA environment variable. No testing and conditional
processing of the tree are required.
Additionally, the generate_cfg script is no longer used, or is the
branch conditing code in createme. So they can be safely removed
from the tools and repository.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Thu May 10 12:18:19 2012 -0400
kern-tools: remove meta tag and directory assumptions
During repository sanity checks (createme) and during the
checkpoint process, there were several assumptions about the tree
that either relied on a tag, or a particular directory name.
With this set of changes, simply passing the meta branch name is
enough to sanitize and restore the checkpoint. If no meta branch
name is passed, the default of 'meta' is used for both the branch
and meta data directory name.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Without this, the installed files get mangled when a dash shell is used.
(From OE-Core rev: 59db7976fa870084af19d880e594b0e94678cf19)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed patch for ARM compilation, as it seems that the upstream fixed
the ARM compilation problem in a slightly different way (tested by compiling
lttng-tools for MACHINE=qemuarm)
(From OE-Core rev: aa43a37da4f14b5a184f79b2ff43b0cd491e49af)
Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta SRCREVs to pickup configuration policy cleanups:
49f931b meta/fishriver: remove redundant features and options
51a6d3f meta/emenlow: remove redundant features and options
101dd7f meta/crownbay: remove redundant features and options
4110ecd meta/sugarbay: remove redundant features and options
0f1304a meta/jasperforest: remove redundant features and options
0a56a3b meta/common-pc-64: factor out SCSI CDROM option
b71938a meta/common-pc-64: use usb-mass-storage feature
0724f40 meta: add scsi cdrom feature
438bca8 meta/common-pc: use usb-mass-storage feature
c970881 meta: factor out SCSI options from the usb-mass-storage feature
4c8135e meta: add scsi disk feature
6872a81 meta: add scsi feature
e706ec5 meta/sugarbay: factor out policy-related options
8b7fbc2 meta/jasperforest: factor out policy-related options
fea1b0e meta/fishriver: factor out policy-related options
13bf9ab meta/emenlow: factor out policy-related options
4748d50 meta/crownbay: factor out policy-related options
44f592f meta/common-pc-64: factor out policy-related options
5a3f5c7 meta/common-pc: factor out policy-related options
1f5a10b meta/common-pc-64: use usb features
4b87723 meta/common-pc: use usb features
594ba05 meta: add ROOT_HUB_TT config option to the usb/ehci-hcd feature
(From OE-Core rev: b8ce5b4a8f6ea5021e284dfd486593dbcfbe0502)
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>
The LICENSE field for kern-tools was generic and leads to QA warnings
from the license classs:
"No generic license file exists for: GPL in any provider"
Updating to a specific GPL version that matches the source fixes the
warning.
(From OE-Core rev: 72101b324062642474d67ee90356489993a973d0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta SRCREV for the following fixes:
1dfd60f meta/fishriver: move smp options from recipe-space
012780a meta/emenlow: move smp options from recipe-space
b59b1a5 meta/crownbay: move smp options from recipe-space
74dc6ac meta/sugarbay: remove boot-live options
a4bedcb meta/jasperforest: remove boot-live options
4ae7b81 meta/sugarbay: use usb features
30e7e8c meta/jasperforest: use usb features
22d0c5d meta/fishriver: use usb features
e262965 meta/emenlow: use usb features
(From OE-Core rev: 5bf86f42e25489ebe92d2c891ee7ee340d668e29)
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>
The commit breaks pkgconfig and after discussing it with the kmod and udev maintainers the conclusion was reached that putting the libraries in /lib instead of /usr/lib is not supported.
This reverts commit 6b74f2461735272bd950a4f060dab6e778a36f92.
(From OE-Core rev: 7163ebd92a799b8f000b2b6f303b20de468b5f90)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* PROVIDES does not need _${PN}
* CONFLICTS should be RCONFLICTS
* opkg needs RREPLACES to automatically remove older module-init-tools
instead of just reporting it conflicts with kmod
SHR root@gjama ~ $ opkg install kmod
Installing kmod (7+git02629fa02e96763db7460a930239cc93649a52f8-r0.0) to root...
Downloading http://jama.dyndns-home.com/org.openembedded.shr-core//armv4t/kmod_7+git02629fa02e96763db7460a930239cc93649a52f8-r0.0_armv4t.ipk.
Removing package module-init-tools-depmod from root...
update-alternatives: removing //sbin/depmod as no more alternatives exist for it
Removing package module-init-tools from root...
update-alternatives: Linking //sbin/insmod to ../bin/busybox
update-alternatives: Linking //sbin/modprobe to ../bin/busybox
update-alternatives: Linking //sbin/rmmod to ../bin/busybox
update-alternatives: removing //sbin/modinfo as no more alternatives exist for it
update-alternatives: removing //bin/lsmod as no more alternatives exist for it
update-alternatives: Linking //sbin/lsmod to ../bin/busybox
Configuring kmod.
update-alternatives: Linking //sbin/insmod to /sbin/insmod.kmod
update-alternatives: Linking //sbin/modprobe to /sbin/modprobe.kmod
update-alternatives: Linking //sbin/rmmod to /sbin/rmmod.kmod
update-alternatives: Linking //sbin/modinfo to /sbin/modinfo.kmod
update-alternatives: Linking //bin/lsmod to /bin/lsmod.kmod
update-alternatives: Linking //sbin/lsmod to /bin/lsmod.kmod
update-alternatives: Linking //sbin/depmod to /sbin/depmod.kmod
(From OE-Core rev: 8de7f8045f28aecfe796afcdb013c557ce9d1372)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This also helps avoid QA errors about binaries
accessing contents from /usr/lib
Also fixes emptry libkmod problem since now
the files are installed in expected place
(From OE-Core rev: 6b74f2461735272bd950a4f060dab6e778a36f92)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The linux-yocto repository and scripts can support a mode of
meta data management that merges a base meta branch to every
BSP branch. In this case, the scripts don't have to restore
a checkpoint for the meta data to be globally accessible.
The decision to restore or not is made based on whether or
not the meta branch is part of all branches or not.
The linux-yocto recipes have a sanity check to determine if
the requested SRCREV for meta data matches the head of the
meta branch (via do_validate_branches). If the wrong commit
is at the head, the meta branch is moved aside and the branch
reset to the right commit. This creates two meta branches that
contain the base meta data.
The test for integrated meta data mistakes this for a globally
merged set of meta data and doesn't restore the checkpoint, which
leads to build failures.
The immediate fix is to allow two branches to have the meta
data. The long term fix is to make the detection only consider
if the build branch contains the meta data.
(From OE-Core rev: bd794b92d12ceda2728520701e980b7a3cabd23d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* until it's decided it should be installed in base_libdir or libdir
* fixes libkmod packaging
(From OE-Core rev: 87249372b4a9951f9e4dc6acece950718382a164)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the SRCREV to pick up two minor fixes:
1/2:
kgit-init: correct spelling of createme
kgit-init copies the kern-tools scripts and intends to copy createme.
The typo is in the usage() of updateme as well.
(From OE-Core rev: 043871d7e5d2d19c2ff43e54d2ff180c09e8903e)
Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com>
2/2:
kconf_check: fix bad quoting around missing_required.cfg
missing_required.cfg won't have it's path truncated (if applicable), since
the quoting it wrong.
Signed-off-by: Andrea Adami <andrea.adami@gmail.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In order to support repositories of various types (with or without
meta data, branched, pristine, custom, etc) information about the
type of processing that is required was passed to the processing
phases via variables.
The combination of variables involved in coordinating the processing
creates a learning curve and overly complicates recipe extensions.
With minor tweaks to the kern-tools, adding flexibility and keying
off the existence of the meta branch it is possible to remove all
of the variables that were added to support different repository
types.
(From OE-Core rev: 06e5f45c8f38925cd5902a3a3f436f5e9451dd16)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.2 SRCREVs to import the following meta/config
changes:
6b3d4e0 meta: add mei feature
519abac meta: add usb/uhci-hcd feature
a67c5a3 meta/crownbay: use usb features
0855066 meta: add usb/ohci-hcd feature
15f1a99 meta: add usb/ehci-hcd feature
8fa6408 meta: add usb/xhci-hcd feature
c724a55 meta: add usb/base feature
b55b3a1 sys940x: Cleanup sys940x.scc
93f2e97 sys940x: Use PHYSICAL_START of 0x200000 to boot
aaa034b sys940x: Add common standard and preempt-rt features
e2b1286 sys940x: Add efi-ext to standard and preempt-rt configs
d188c21 sys940x: Move emgd-1.10 data to the standard scc file
72d9369 fri2: Cleanup fri2-$KTYPE.scc files re efi-ext.scc
dbcb120 fri2: Use emgd-1.10 feature and branch
And the following driver fix:
f39a0a9 pch_gbe: Do not abort probe on bad MAC
(From OE-Core rev: 612047a20ca400b932ccc634ddb759460d69fdce)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
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>
Since its provided by kmod
(From OE-Core rev: 27bc204010b9dccb30847d7b3216f8b1e106f64e)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta SRCREVs to pickup the following meta change for the
3.0 and 3.2 kernels:
[
meta: Clean up BSPs kernel config
Clean up some QEMU and non-x86 BSPs kernel config, including
qemuarm
qemuppc
qemux86
beagleboard
mpc8315e_rdb
Only obsolete/invalid kernel configs are removed.
(From OE-Core rev: 1f68d624c109c3f31a6f2f6106b5ef56e3d9a166)
Signed-off-by: Yang Shi <yang.shi@windriver.com>
]
With this commit, the configuration audit for the qemu and hardware
reference boards is (largely) warning free.
Signed-off-by: Yang Shi <yang.shi@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta SRCREV for both the 3.0 and 3.2 kernel trees to
pickup the beagleboard xM boot fix:
[
meta/beagleboard: disable CONFIG_PREEMPT
The boot hangs with the message:
mmc0: error -110 whilst initialising SD card
The MMC driver has issues initializing when PREEMPT is enabled (either forced
or voluntary). Unplugging and then plugging the card back will reset the
driver and continue booting. Alternatively, disable preemption.
]
[YOCTO: #1892]
(From OE-Core rev: 36e9e6a88bc4436efefd4a25c0a58be75f887142)
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In fixing an existing patch migration bug, the list of valid extensions
got out of sync from the core patch class. As a result, valid patches
were not being applied to the tree.
Updating the tools to migrate .diff files fixes the issue.
Also in this fix is the removal of .patch in the find_sccs() routine, since
it will never be returned by patch.bbclass when all non-patches are
requested, it is simply confusing.
(From OE-Core rev: 0ade3f26f40b67d7296725b1e956c46be9a86089)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This allows systemtap-uprobes to build again after the recently
added patch broke the builds.
(From OE-Core rev: 4bbe926f3ca68297d70849bab67177da624316d1)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Building the systemtap documentation adds significantly to the build
time, so disable it by default.
(From OE-Core rev: e37391a949fb0a6edf87eb910e93a17caf309119)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When building docs in systemtap, docproc is used to generate the
tapset documentation, but it gets built for the target, while it needs
to be build for the host instead. This change causes that to happen.
Fixes [YOCTO #2193].
(From OE-Core rev: 6ef7112e339bb5c03dee862bc56c10fdf677be78)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
During testing/extension of the linux-yocto-tiny kernel it was found that
defconfigs were not always properly applied. This was due to two issues:
- not being able to fully control the order of objects applied to the
git tree on the SRC_URI
- defconfigs triggering --allnoconfig before being applied
To fix this, the recipe space code that previously detected and generated
automatic features moves back to the kernel tools (where it was before) and
is updated to also process .cfg and defconfigs. Moving this back to the
tools allow other recipes to automatically benefit from the additional
support.
The second issue is addressed by allowing configme to take --alldefconfig
when a recipe wishes to pass a defconfig and override the default
behaviour.
Fixes [YOCTO: 2250]
(From OE-Core rev: 08c368b9980716e459d846dd7183940a5bf8bea4)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.2 recipe SRCREVs to pickup the following meta change:
[
meta: Add igb.scc to Romley
Romley machine has 82580 Giga bit Ethernet Controller.
Add the relavent Nic driver to it.
(From OE-Core rev: d7c567816bf828da34fb9e315d4d76c4181337e9)
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>
The dtb files were not being installed into a location compatible with sstate and
the do_deploy task. This means in builds just using sstate, the dtb files disappeared.
This patch fixes the code to use the correct location for deploy files.
[YOCTO #2190]
(From OE-Core rev: 9815b7a95ac33d3234073cdd204d9389b4241189)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes [YOCTO #1501]
hello-mod is an example kernel module, and does not provide any real
functionality. As such, it would be better placed under meta-skeleton than
meta.
(From OE-Core rev: bde1744018afd4616e114b20ffdc21b9abddcedc)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Recent Linux kernel tries to load the libertas firmware with the version
string in its name first. This results in a delayed firmware load on
system boot. Keep the default libertas firmware name and add a link for
older driver versions.
(From OE-Core rev: baa1323dfff35ccd5aebc036ca97925a1f1a604e)
Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Migrate linux-yocto-tiny from 3.0 to 3.2. The 3.0 recipe was
based entirely on recipe-space fragments and was only a proof of concept.
The 3.2 linux-yocto meta-data now has a proper tiny KTYPE defined.
By default this recipe supports only the qemux86 machine, which builds the
common-pc support (including networking, sound, USB, VGA and serial consoles,
etc.). New machines can be added and will use the tiny KTYPE, but will need to
add any desired hardware support as the base config is very minimal.
No filesystems are supported by default, only the initramfs.
(From OE-Core rev: 44c556f5300b1d811a1ae71f501320d1a6b0fb2e)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the META SRCREV to pickup these commits:
59f350e meta: Add common-pc-tiny.scc
0996ca9 tiny: Minimize the tiny config
d6b57bb meta: common-pc add dependencies to cfg
Which update the configuration for the tiny profile of the kernel
for the 3.2 release.
cc: Darren Hart <dvhart@linux.intel.com>
(From OE-Core rev: df3b8f716cc9203251cd4d4b5e673d7ecab5111b)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta SRCREV to pick up this commit:
[
common-pc: Add PCNET32 to the config
Qemu and VM Ware both support PCNET32 and the latter requires it for
32 bit images.
(From OE-Core rev: 6b431f1a09abde57d03b799e57186afb9a572387)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
]
Signed-off-by: Darren Hart <dvhart@linux.intel.com>5A
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* show warning for old /etc/modutils/* files without .conf extension
* v2: keep adding modules also from old /etc/modutils/* after showing
warning, this way update-modules will be backward compatible also on
images without kernel upgrade
(From OE-Core rev: 38302a1353cf072b7c6c54f7f90936e4c2180102)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The linux-libc-headers-yocto is not required in oe-core, it can be
moved to yocto specific layers. The linux-libc-headers_* recipes
provide sufficient headers fore core users.
(From OE-Core rev: 6320041fa77514e2d2bf54f0ea6c7052d2a4a89a)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The 3.1 kernel was never released or directly supported via
oe-core. So as part of update the libc-headers to 3.2 we can
take the opportunity to remove it.
Built and booted on the qemu* targets.
(From OE-Core rev: ce7469ab3b49f8a326ba4c3486a4e63b7cd48799)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Change the recipe name lttng-ust from lttng-2.0 to lttng2-ust so that
that both the lttng-ust of the old framework and of the new framework
lttng-2.0 can coexist.
Fixed bug [YOCTO #2062].
(From OE-Core rev: 0d9fc8185945328837aa1a3d9d705afa56856853)
Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update blktrace to reflect the newer 1.0.5 tag.
(From OE-Core rev: c981fa4fad8a457882293157b7bdca05aad5a778)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
recent -stable kernels have their own fallback definition of is_compat_task
#define is_compat_task() (0)
To protect against this double definition of is_compat_task we can check
to see if it is already defined, and skip the lttng variant.
(From OE-Core rev: 53db58982b7af59d75fc11b73475e9d71e6927ac)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta and machine branches to the latest 3.0 -stable
release.
To see the full changelog: git log v3.0.23..v3.0.24
(From OE-Core rev: 7ed5780cbae6b60adeb56d4d3deb0b82c2dfec70)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.2 meta and board branches to the latest 3.2-stable
update.
(From OE-Core rev: 5de1757cc139565b02c6c56b4aa78a2401b42aa9)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the meta SRCREV to pickup the following change
fri2: Update fri2.cfg for hardware specific support
The FRI2 does not require R8169 or PATA support. It does not need SFF
or GENERIC ATA options either.
The FRI2 does require IEEE802154 (Zigbee), BT (Bluetooth), and IWLWIFI.
The latter is compiled as a module to avoid the need for an initrd
containing the firmware blobs.
(From OE-Core rev: 97c21129819ee7a3091757879cd2f0b8133f12e7)
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>
Bumping the meta branch for two changes:
cac43c1 fri2: Update fri2.cfg for hardware specific support
892bd13 meta: Create scc file for pvr merge
(From OE-Core rev: 8d1ed5e42358bd33442a6038a9f3931c827bdf94)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The packaging changes to ncurses could break package feeds,
so bump the PR on everythong that DEPENDS on ncurses.
(From OE-Core rev: be92256917c157284ef8370bb93bbf443849b2e1)
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The kernel configuration requires lzma to compress the kernel image
(CONFIG_KERNEL_LZMA=y), so add a dependency on xz-native which provides
it.
Fixes [YOCTO #1728].
(From OE-Core rev: e1f656492475fb65d1203afe0afeeec7e279a317)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* The previous copy command preserved the original
owner and permission bits.
* The new command uses root:root and applies OE's
umask.
(From OE-Core rev: 710e565beadcf4ea965af688fd08b9b1f274ad57)
Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Adding "GPLv2 & LGPLv2.1" to create a dual license to cover the libraries.
* Bump up PR
(From OE-Core rev: 468aab48b07d345aadb6f449421824b0447d29c2)
Signed-off-by: Jeff Lance <j-lance1@ti.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the -rt kernel to pickup the incremental update to -rt16.
No major changes from -rt15, except for a bug fix that we want
to pick up.
(From OE-Core rev: 0b03c2382ad6b2d472555f5054a1ce82eb4e3de9)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta SRCREV to pickup the following fixes:
a9ffedb meta/fri2/sys940x: fix incorrect cfg includes
3d1a678 meta/sys940x: fix incorrect emgd branch merge
During the merge of the 3.0 BSPs forward to 3.2, a few moved config
fragments were missed.
(From OE-Core rev: 51c0c1d07d44b3bffb63d15b6befff6e7ba2549f)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is an update of the linux-yocto 3.0 and 3.2 SRCREVs to bring
in the following updates:
- v3.0.23 stable update
- v3.2.9 stable update
- 3.0/3.2: fri2 updates (pch + configuration changes) from Darren Hart
- 3.0: pvr merge from Kishore Bodke
- linux-yocto/rt: update to 3.0.23-rt38
- linux-yocto/rt: update to 3.2.9-rt15
These have been built for all qemu targets, and built for the appropriate
hardware platforms.
(From OE-Core rev: a9e7131b85e1787e6f76c64d77b2ac6684c8a9c9)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Instead of specifying nocheckout=1, it provides a better workflow if
the linux-yocto recipes use the new bareclone=1 option to get a mirrored
copy of the source repository. This allows all local and remote branches
to be available during the kernel build and development cycle.
(From OE-Core rev: 2281e14a342639bfd2656ffa220dc023168cb35e)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Using "1" with getVar is bad coding style and "True" is preferred.
This patch is a sed over the meta directory of the form:
sed \
-e 's:\(\.getVar([^,()]*, \)1 *):\1True):g' \
-e 's:\(\.getVarFlag([^,()]*, [^,()]*, \)1 *):\1True):g' \
-i `grep -ril getVar *`
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
3.2.8 was released and contains a floating point fix for x86 32
bit and some x86-64 fixes. So it's worth picking up right away.
(From OE-Core rev: 8bd3038b62eaf46f9ac09fcdc1ca5e6f6e53a126)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.0 and 3.2 kernel SRCREVS to make the PVR feature
description available to machines with the appropriate hardware.
(From OE-Core rev: 0027bb45a40d209f43088e2c2b38191446ea1190)
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>
Making two changes for BSPs that prefer linux-libc-headers-yocto:
- bumping to v3.2.8 headers
- stubbing out unecessary linux-yocto functions when headers
are being built
[YOCTO #2032]
Acked-by: Darren Hart <dvhart@linux.intel.com>
(From OE-Core rev: 0889f693916bb8f77003af419f71212201b4d9c9)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.2 kernel recipe to the latest -stable release.
(From OE-Core rev: 97d55a32c7bb7650af59a5bce49cf8409a875f98)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bumping the revision of the 3.0 kernel to the latest -stable release.
(From OE-Core rev: b91c32360469ce97fc00e807e7c3415fed1848a5)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* We have various variables which are either not quoted at all or are half
quoted. This patch fixes the bad exmaples so everything is consistent.
(From OE-Core rev: 960ee8076e860353a05eb2eb7f825a455c54698d)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating meta for the following change:
[
fri2: use emgd-1.10
Use the yocto/emgd-1.10 branch in place of yocto/emgd.
]
(From OE-Core rev: aa6293ffbc7f8f17e55f2105de56384e14591b44)
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>
To adapt to different branch names in a repository, removing explicit
references to 'yocto' in automatically created BSPs ensures that they
are consistent with the merged variants. Existing BSPs and auto BSPs
are not impacted by this change.
(From OE-Core rev: 74613d02aa844cac3be0626cc64139643fe17a4f)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta SRCREC to pickup the following changes:
70e86dc meta/rt: update rt patch cache
Without this change a 3.0 based -rt build will fail to patch.
(From OE-Core rev: e5da5e84e64362f59a62f65b9f260f96af96bc11)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta SRCREV to pickup the following changes:
[
Author: Darren Hart <dvhart@linux.intel.com>
Date: Wed Feb 1 09:37:48 2012 -0800
Remove boot-live cfg duplication from BSPs
Several BSPs duplicated the boot-live fragment in their BSP
specific config. Remove the duplication and add CONFIG_RD_GZIP
and CONFIG_BLK_DEV_SR to the boot-live fragment.
(From OE-Core rev: a243dded5c84d48728308a769e527302b7539939)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Acked-by: Tom Zanussi <tzanussi@intel.com>
Author: Darren Hart <dvhart@linux.intel.com>
Date: Tue Jan 31 13:18:17 2012 -0800
meta: sys940x BSP meta data
The Inforce SYS940x-ECX Developer-Ready Reference Platform features:
o Intel Atom E6xx (0.6-1.6 GHz)
o Up to 1GB on-board DDR2
o Intel Platform Controller Hub EG20T
o VGA,LVDS
o HD Audio
o SD Card
o Dual SATA
o Mini-PCIe
http://www.inforcecomputing.com/SYS940X_ECX.html
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Acked-by: Tom Zanussi <tzanussi@intel.com>
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
]
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>
SystemTap needs to provide uprobes.ko in order to support user space
probing. Build and install the module on systems that support it.
Additionally, split off common bits into systemtap_git.inc.
(From OE-Core rev: 3cc4ba935444240b93abdc726342658ada803118)
Signed-off-by: Wade Farnsworth <wade_farnsworth@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since the target image may not contain dev tools, it is useful to
provide native systemtap in order to be able to compile systemtap
scripts for the target.
(From OE-Core rev: 507bd29c5d1a3459e376e2d2c338b7e2a0afabaa)
Signed-off-by: Wade Farnsworth <wade_farnsworth@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bump SRCREV to the latest stable version of systemtap.
(From OE-Core rev: ea57a29c75aa8265aecb8b0acd9c29340e98092c)
Signed-off-by: Wade Farnsworth <wade_farnsworth@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The -stable team released v3.0.18, so it becomes the new base for the
linux-yocto_3.0 recipe.
Along with the 3.0.18 update this kernel refresh brings in the following
changes:
59314a3 meta/beagleboard: Using CONFIG_PANEL_GENERIC_DPI=y
b168325 crownbay: use emgd-1.10
281b80f kver: bumping to v3.0.18
0d5d0dd common-pc*: add SMP and virtio
(From OE-Core rev: b58d330a88a64ac8ff82362cc90cc817f38b82cd)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Adding initial support for the linux 3.2 kernel.
Although the branching and naming has changed slightly, the same BSPs and
features exist in this tree as have existed in previous linux-yocto versions.
Notable features of this update are:
- streamlined branch naming
- configuration and functionality split in the standard kernel
- creation of the 'tiny' kernel type branch
- audited kernel configurations with optional features documented
in the meta branch
- feature and BSP refreshes
- 3.2-rt support refresh
- qemu ppc graphics support
Build and boot testing has been performed on all emulated targets
(sato and core).
(From OE-Core rev: 72264df07d7e57ba8232aae90b76ab220fdb2d22)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the kern-tools SRCREV to import the following changes:
a7a9930 kgit-meta/scc: allow multi-line defines
e3442c6 kern-tools: add required and optional kernel configuration processing
b56b67b configme: extract redefinition and mismatch information
6118eaf kern-tools: remove branchname assumptions
These are required to support the kernel configuration policy changes
implemented in the yocto 3.2 kernel repository.
(From OE-Core rev: 5a3759f4b23361dd2c1968ce51e5c3695a661972)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As binutils is required by perf to build and is GPLv3 licensed adding
GPLv3 to INCOMPATIBLE_LICENSE will cause linux-yocto to be skipped.
Long term we should look at moving perf to a separate recipe but as a
short term solution this patch will ensure that when GPLv3 is in
INCOMPATIBLE_LICENSE perf is not built and it's dependencies are not
added to build.
Fixes [YOCTO #1879]
(From OE-Core rev: ce61f9031b54067bffa304dab90c31278631dcdf)
Signed-off-by: Joshua Lock <josh@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch is to upgrade kexec-tools to 2.0.3.
And since fix_for_compiling_with_gcc-4.6.0.patch is there in 2.0.3, it is removed.
(From OE-Core rev: aea75907ff0ad11b7a17910f74491278e55bbc10)
Signed-off-by: Shane Wang <shane.wang@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Two issues are fixed with this commit, the ability to use the keyboard
on a graphical qemu boot and enabling ethernet by default on a 3.0
kernel.
The keyboard is fixed via the same method as the other simulations with
the addition of console=tty on the qemu command line.
Ethernet is fixed by adding a dependency of PCNET32 to the qemuppc
configuration, which allows us to build ethernet directly into the image.
(From OE-Core rev: 29c71eeb98aa8ce0fb0e0a30483499525bf6305d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It provides trace read and write libraries, as well as a trace converter.
(From OE-Core rev: d14441874163bd579d9901f9bc07852882502100)
Signed-off-by: Zumeng Chen <zumeng.chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch intended to integrate the lttng-modules 2.0 package
containing the kernel tracer modules.
LTTng-modules 2.0 is currently in pre-release (-pre11), so we
have to update it when official released.
lttng-2.0 supports lttng-modules extra builds, which don't need
any patches on Linux kernel vs the previous version of lttng.
As described in README of lttng-modules-2.0, so far, it has been
tested in the latest kernel on x86 32/64-bit, and powerpc 32-bit,
, build tested on ARM. So does yocto kernel, the related tests
on qemux86 and qemuppc has been validated and a build test on
qemuarm passed too with this patcheset.
(From OE-Core rev: b054921f7dd59519a896a4e1a5f40965d4abd87e)
Signed-off-by: Zumeng Chen <zumeng.chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch intended to integrate the Linux trace toolkit, which
is a suite of tools designed to extract program execution details
from the Linux operating system and interpret them.
lttng-tools 2.0 is currently in pre-release(-pre16), so we have to
update it when official released.
(From OE-Core rev: 4733cd6501e5d39b4229c3da79529d6a3ae844f6)
Signed-off-by: Zumeng Chen <zumeng.chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch intended to integrate the LTTng UST 2.0 package, which
contains the userspace tracer library to trace userspace codes.
(From OE-Core rev: 4ed09cb80196c7a3f691c8b9304df7c1fe4a8be5)
Signed-off-by: Zumeng Chen <zumeng.chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the SRCREVs to include the following fixes from Khem Raj and
Zumeng Chen.
6f5b118 compiler.h: Undef before redefining __attribute_const__
fe80c1e oprofile, arm/sh: Fix oprofile_arch_exit() linkage issue
(From OE-Core rev: 02e22816d68dc2bac7fed6952e52ea8a3d9532d2)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With this new emulation, existing qemuppc functionality is maintained
and other functionality such as framebuffer + sato and NFS boot are
added.
(From OE-Core rev: 52ea026df141ea23bbab38ad3a9733c15097eaa4)
Signed-off-by: Liming Wang <liming.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* from meta-oe (originally from org.openembedded.dev)
* There are no reasons to install kdump when only kexec is needed.
*
* In oe-core/meta there are no references to kexec-tools so
* the recipes inn external layers rdepending on kexec-tools should be
* fixed and rdepend on kexec and/or kdump.
*
* Bump PR.
(From OE-Core rev: 1f40a5486f703684c5d1d7360ef3cbdf75577495)
Signed-off-by: Andrea Adami <andrea.adami@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
systemd has its own mechanism for loading kernel modules at startup
(From OE-Core rev: 553deffc8040afabd56b1c1d87a8a8d24bbae5d0)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is no reason to continue to carry this feature
(From OE-Core rev: f1193e077d187b9ce18ae0686b1a1f0f9832036d)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The pkglibexec_SCRIPTS pair is valid. the 1.11.2 introduced an bug
to make it invalid. Now the automake 1.11.2 recipe is fixed, so
no need for this fix for systemtap recipe.
(From OE-Core rev: 0d0a9c71499c6b973fe08b02838b99e47785a07e)
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield
Bogdan Marinescu
Marcin Juszkiewicz
Kang Kai
Fahad Usman
Anders Darander
Maxin B. John
Constantin Musca
Khem Raj
Jack Mitchell
Noor Ahsan
Richard Purdie
Eric Bénard
Ross Burton
Robert Yang
Tom Zanussi
Christopher Larson
Martin Jansa
Saul Wold
Vladimir Zapolskiy
Darren Hart
Phil Blundell
Cristian Iorga
Paul Eggleton
Liang Li
Matthew McClintock
Radu Moisan
Javier Martinez Canillas
Morgan Little
Mark Hatle
Zhenhua Luo
Wade Farnsworth
Paul Gortmaker
Andreas Müller
Nitin A Kamble
Koen Kooi
Stefan Herbrechtsmeier
Lianhao Lu
Scott Garman
Andreas Oberritter
Jeff Lance
Joshua Lock
Shane Wang
Zumeng Chen
Liming Wang
Andrea Adami
Steve Sakoman