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>
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>
