The runtest.patch is unused, so there is no reason to keep it on the
tree.
(From OE-Core rev: c1fb471dc83206f3940108319fca760b39cbbac7)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This quiets a GNU_HASH warning.
(From OE-Core rev: ad8a2ca46075a7ea236d6db9da963dc0040d2206)
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This makes the gtk dependencies optional.
(From OE-Core rev: 191a1817c9dce90f3094bc98d6e0f5ab02f8a5c7)
Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We only have a short description, so set SUMMARY and DESCRIPTION
will be defaulted from it.
(From OE-Core rev: 1d655e2407267ed91e371e078e9a9a10183e3d62)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The for loop already handles the case when KERNEL_DEVICETREE is empty.
(From OE-Core rev: 49010f4a1ae9570e96691c9faeb17808174488fe)
Signed-off-by: Stefan Christ <s.christ@phytec.de>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In order to use virtio devices as default in runqemu script
because these drivers are designed to use in vrit providing
better performance.
[YOCTO #8427]
(From OE-Core rev: 16dad3a6ccba01639b3a711426599af49c30a088)
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the META SRCREVs to make the nf_tables feature available.
(From OE-Core rev: 43ed2494ae4f89cab6e018f289bb048289d478f5)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the SRCREVs to apply the same fix as 3.14 and 4.1 already
have to fix qemuarm boots with gcc5.x
[YOCTO: #8415]
(From OE-Core rev: fa9852d5d7383e6d03c756b8ad615668857b0b86)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With the recent changes to improve patch processing times, the ability
to skip already applied patches is not active by default.
The automatic detection and resume was hiding issues with the include
files generated by scripts like yocto-bsp.
If a .scc file that contains a patch is included twice, the patch is
applied twice, and the second appliation fails for obvious reasons.
We can partially fix this by ensuring that already included
configuration fragments are not forced into the meta-series.
.scc files that are explicitly listed twice will continue to fail, and
recipes must be modified to avoid this.
[YOCTO: #8486]
(From OE-Core rev: ed2da98bf3ac798009f58a53b91285b4dac69d5a)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 4.1 SRCREVs to integrate the following fix:
[
drm/i915: Fix the VBT child device parsing for BSW
Recent BSW VBT has a VBT child device size 37 bytes instead of the 33
bytes our code assumes. This means we fail to parse the VBT and thus
fail to detect eDP ports properly and just register them as DP ports
instead.
Fix it up by using the reported child device size from the VBT instead
of assuming it matches out struct defintions.
The latest spec I have shows that the child device size should be 36
bytes for rev >= 195, however on my BSW the size is actually 37 bytes.
And our current struct definition is 33 bytes.
Feels like the entire VBT parses would need to be rewritten to handle
changes in the layout better, but for now I've decided to do just the
bare minimum to get my eDP port back.
Cc: Vijay Purushothaman <vijay.a.purushothaman@linux.intel.com>
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
(cherry picked from commit 90e4f1592bb6e82f6690f0e05a8aadcf04d7bce7)
Signed-off-by: abdul arif abdul muttalib
<abdul.arif.b.abdul.muttalib@intel.com>
Signed-off-by: Tan Jui Nee <jui.nee.tan@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
(From OE-Core rev: 1f575df04f003c1e1fe9413f95023c20a2f30e19)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the configuration fragments for the Intel Axxia on the 3.14
and 4.1 kernels.
(From OE-Core rev: a4964955257a1ab2586fd5efeedc2e32b725895d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The source makes no reference to KERNELDIR any more and this make the recipe
machine specific. Simply drop the unused reference.
(From OE-Core rev: 21bad4c807acd4c596fcca8afeab737161fbbb39)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the kern-tools SRCREV to import the following fix:
kgit-meta: resume after last applied patch
When the auto-resume (resume point detection) was removed from the
processing of a meta-series, it ignored the fact that a single patch
series may in fact be processed a number of times.
Two layers patching a kernel will generate two different runs on the
same branch, which always start at patch one. This will obviously
break with duplicate patches.
To avoid this, we simply track the last patch applied, and
explicitly
tell the patch scripts where to start. This gets us resume
functionality, without the overhead of resume point detection.
(From OE-Core rev: 692f1333e257556e7462b2436dd60e865869349c)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 4.1 SRCREVs to integrate the following DRM backports:
a8abc111a96d drm/i915: Only wait for required lanes in vlv_wait_port_ready()
81354180432b Revert "drm/i915: Hack to tie both common lanes together on chv"
d660fc117731 drm/i915: Work around DISPLAY_PHY_CONTROL register corruption on CHV
0e797e9cb717 drm/i915: Implement chv display PHY lane stagger setup
(From OE-Core rev: 2ea7533b5d45bb459284dd1c3f81d4bcac88f882)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are some important fixes and CVEs in 4.1.8, so we update the
SRCREVs to integrate the -stable changes.
(From OE-Core rev: 0cd10fc32fd6a3faced69ef206271c8afde17533)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As part of the axxia preempt-rt integration, the preempt-rt
branch now becomes standard/preempt-rt/base, to allow proper
branch inheritance as: standard/preempt-rt/axxia/base.
No functional changes happen to the base -rt, just the default
KBRANCH changes.
(From OE-Core rev: 5c91535baf876a3e2c4fd91be046dc3a92dc0ad2)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The gettext 0.16.1 doesn't install any m4 files to sysroot, please see
the following commit:
commit 9e10db5bdf
Author: Christopher Larson <kergoth@gmail.com>
Date: Mon Mar 17 18:10:54 2014 +0000
gettext-0.16.1: kill target m4 macros from sysroot
This is aim for using gettext-native's macros(gettext-native-0.19.4),
but when we set:
PREFERRED_VERSION_gettext = "0.16.1"
And build the recipes like pcmanfm, we would get errors when
do_configure:
configure:5164: error: possibly undefined macro: AM_NLS
This is because autotools_copy_aclocals doesn't copy the native macros
for target unless they're direct dependencies.
Add gettext-native to DEPENDS will fix the problem.
(From OE-Core rev: 48c168334bb60937653ab782026948d139603f8e)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If you currently do a DISTRO_FEATURES_remove = "x11" with OE-Core, you
see failures due to dependency problems. The work in resolving this was
partially completed a while back. This adds in the markup mainly for
gtk/gtk3+ recipes and means "bitbake world" will work successfully.
Rather than code the gtk/gtk+ specific distro features into each recipe,
a shared variable is used.
(From OE-Core rev: ef967c70182eeccb59c7511d838a7ecb0b2315c1)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The -rt build suffered the same breakage in master as the standard
kernel builds: due to a bad git history merge, existing patches were
dropped from branches.
This meant that we were missing the -rt changes, which re-introduced
some failures with linux-yocto-rt.
With these SRCREV updates, we have the latest 4.1.x-rt and all
architectures build.
(From OE-Core rev: 96db930d8add6623168ec5e638769d5c0f348265)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta SRCREVs to integrate the following config change:
Author: Saul Wold <sgw@linux.intel.com>
Date: Tue Sep 22 07:23:06 2015 -0700
common-pc-drivers: add CONFIG_PATA_SCH
The NUC uses this hardware and should still operate correctly with a
genericx86
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
(From OE-Core rev: c597c230b4f66bd04d47a448a00cf54fca71c0f2)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Setting the SRCREVs to import the following changes in the
4.1 kernel tree:
79a31b9d23db hid-core: Avoid uninitialized buffer access
121593d3a0a4 aufs: call mutex.owner only when DEBUG_MUTEXES or MUTEX_SPIN_ON_OWNER is defined
efa7952a190f Bluetooth: Delay check for conn->smp in smp_conn_security()
69428ec43bd9 cc2520: set the default fifo pin value from platform data
ee0ddf37f3d6 fs/yaffs2: Fix a judgement logic for ACL operations
fff29e47f5c4 yaffs2: remove read and write methods
b3b9d030ad84 yaffs2: replace f_dentry to f_path.dentry
(From OE-Core rev: 6398e9be3c3a2af5e650a4e7ee7f8f61c7b520fd)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Make nios2 kernel depend on libgcc.
In arch/nios2/Makefile, it adds LIBGCC to libs-y:
LIBGCC := $(shell $(CC) $(KBUILD_CFLAGS) -print-libgcc-file-name)
libs-y += $(LIBGCC)
In file Makefile in top directory, libs-y is assigned to to var
KBUILD_VMLINUX_MAIN. It uses script link-vmlinux.sh to link vmlinux.o,
and when execute function vmlinux_link() in link-vmlinux.sh,
KBUILD_VMLINUX_MAIN is passed to ${LD}.
If build without libgcc, the value of LIBGCC is just libgcc.a without
parent directory. linux-yocto fails to build:
| LD vmlinux.o
| nios2-poky-linux-ld.bfd: cannot find libgcc.a: No such file or directory
Add libgcc to nios2 kernel dependency.
(From OE-Core rev: d3ccab5bb717da57dcaaeb1993ae0f790ce45dcb)
Signed-off-by: Marek Vasut <marex@denx.de>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Get upstream patch from lttng-tools github:
<https://github.com/lttng/lttng-tools>
<commit:700c5a9d4dc7b552926b8ddcbba91cc13312aba0>,
for solving the filtered tracepoint disabling error.
The use of a simple lookup and match on event name is insufficient
to identify the corresponding ust app event.
(From OE-Core rev: 60f8c0e679f70f4477472d7895fddff12530a929)
Signed-off-by: Li Zhou <li.zhou@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 4.1 SRCREVs to integrate the following commit:
hid-core: Avoid uninitialized buffer access
hid_connect adds various strings to the buffer but they're all
conditional. You can find circumstances where nothing would be
written
to it but the kernel will still print the supposedly empty buffer
with
printk. This leads to corruption on the console/in the logs.
Ensure buf is initialized to an empty string.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[dvhart: Initialize string to "" rather than assign buf[0] = NULL;]
Cc: Jiri Kosina <jikos@kernel.org>
Cc: linux-input@vger.kernel.org
Cc: stable@vger.kernel.org
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
(From OE-Core rev: 1c6c1af385a481b0a57ab06cd40af56be3425cc8)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the kern-tools SRCREV to integrat the following commit:
patching: only validate user supplied patches by default
Previously the patching tools would consider both system and user
supplied patches in the same manner .. they are simply a series of
patches to be applied to a branch, and that the scripts should determine
where in the series to start (based on what is already on the
branch).
This detection was causing a few problems:
- time consuming
- starting in the middle of a series when intermediate patches
were merged to a branch.
To solve both the performance and start detection, we instead simply
note the transition from system (i.e. already defined features and
series) and user/recipe supplied patches. When the transition is noted,
the system will start pushing ALL patches without doing autoresume
detection.
Control in keeping the series up to date is passed to the user, and
consistent behaviour/performance is achieved.
(From OE-Core rev: 440ad49e53359ea800c179df105ab885873d7691)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 4.1 SRCREVs to integrate the following changes:
f830ab33799d aufs: call mutex.owner only when DEBUG_MUTEXES or MUTEX_SPIN_ON_OWNER is defined
87df2e93ed65 Bluetooth: Delay check for conn->smp in smp_conn_security()
b09c3eab3e50 cc2520: set the default fifo pin value from platform data
62b01c325d42 fs/yaffs2: Fix a judgement logic for ACL operations
1d19c4e95cfc yaffs2: remove read and write methods
2c822dbc43b9 yaffs2: replace f_dentry to f_path.dentry
(From OE-Core rev: c49ddbf254c2d170d0aeced78ef6c87e60736a26)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
${B} is the default cwd of tasks, so there might be race issues such as:
| mkdir: cannot create directory `/path/to/work/qemux86-poky-linux/perf/1.0-r9/perf-1.0/': File exists
[snip]
NOTE: recipe perf-1.0-r9: task do_configure: Failed
(From OE-Core rev: d41e9fc53230a8fd911c61e018ea901caee4cafc)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The Perf source code between Yocto and upstream are different, like below
commit is not in upstream, so broaden the "--root" replacement to Makefile*
commit 33e96fb1e2d77541e81eb341ccd3fbe9419e4c9a
Author: Tom Zanussi <tom.zanussi@intel.com>
Date: Tue Jul 3 13:07:23 2012 -0500
perf: change --root to --prefix for python install
Otherwise we get the sysroot path appended to the build path, not what
we want.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
(From OE-Core rev: c849ed0c66a2fb7d91795c421eb4c87b47d03c0d)
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If base_bindir is not a direct child of / the link creation in
do_install_append creates incorrect relative links.
Instead pass a full path to the link source too the lnr script
to create a relative link.
(From OE-Core rev: dc184ace9d72a2d4f8eeec831942663cd3b1fd47)
Signed-off-by: Joshua Lock <joshua.lock@collabora.co.uk>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fix a variety of problems such as typos, bad punctuations, or incorrect
Upstream-Status values.
(From OE-Core rev: bd220fe6ce8c3a0805f13a14706d3130ea872604)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-r is understood by gcc but not by clang, anyway its a linker option so
pass it straight to linker by using -Wl explicitly
(From OE-Core rev: 3f4ab836d7d9b7a994b65ab8c7ebf6ff65e6277b)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Clang is stricter with syntax checking and flags the functions return
values if they dont match with function signatures, Fixed thusly
(From OE-Core rev: 91b8c2900570720d56a123a90e927f49a6a6095f)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
1. $(grep xxx xxx) never returns 0, it maybe return empty or string, and
can not compare with 0, this fixes that python module never are installed.
2. python library is installed into /usr/lib/ by default, but we expect
it is installed into ${libdir}, so add --install-lib parameter for python
setup.py to set the library dir;
this fixes not shipped warning, since python modules are installed into
/usr/lib/, but FILE_${PN}-python expects it is under ${libdir}, which is
/usr/lib64/ for 64bit machine
3. the makefile target install-python_ext is moved from Makefile to
Makefile.perf from linux v3.13, so match install-python_ext in Makefile.*
and --root='/\$(DESTDIR_SQ)' before linux v3.13 will install the target
python library to native sysroot, so replace it with --prefix as after linux
3.13;
this fixes not shipped warning, and install target files to native dir, like
below:
ERROR: QA Issue: perf: Files/directories were installed but not shipped in any package:
/home
/home/pokybuild
/home/pokybuild/yocto-autobuilder
/home/pokybuild/yocto-autobuilder/yocto-worker
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr/lib
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages/perf.so
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages/perf-0.1-py2.7.egg-info
(From OE-Core rev: 43f965061f8af4c4537e9d9c0257253e613a616d)
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upating the SRCREVs to import the following commit:
Author: Kevin Hao <kexin.hao@windriver.com>
Date: Mon Aug 31 19:34:48 2015 +0800
mips: octeon: use ll/sc for the atomic ops for all the predecessor
of octeon2
Even the octeon plus has the support of the 'saa' instruction, but
we
don't have a way to distinguish between octeon and octeon plus at
compile time and pass "-march=octeon" to all the predecessor of
octeon2. So it will cause the following error when trying to
assemble
the "saa" instruction with option "-march=octeon":
{standard input}: Assembler messages:
{standard input}:360: Error: Unrecognized opcode `saa $2,($4)'
scripts/Makefile.build:308: recipe for target
'arch/mips/cavium-octeon/executive/cvmx-lap.o' failed
Forcing to use the "ll/sc" for the atomic ops for all the
predecessor
of octeon2 to fix this issue.
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
(From OE-Core rev: a31c715fe484af7fe582d8becac0f20a33acac42)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
oprofileui uses gettext during the configuration task so should be inherit
gettext. This issue appears when an older version of gettext is used do to
pinning to the older non-gplv3 version.
[YOCTO #7795]
(From OE-Core rev: 4734ebef1c5259791daba8ce2ce6dd4ddd5d087b)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
At a guess, Bruce's scripts have mixed up the -rt and on -rt versions
of the qemuppc branches. Set this to a revision on the
standard/qemuppc branch.
(From OE-Core rev: d19f6900a07a718660fcd75d36a3facf048ce157)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Booting qemuarm when the kernel was built with gcc 5.x would result in
a boot hang (or at least no visible output).
Updating the SRCREVs for the following change:
Author: Jianchuan Wang
Email: jianchuan.wang@windriver.com
Subject: Omit to optimize vsprintf.c/kasprintf.c
Date: Wed, 26 Aug 2015 13:54:57 +0800
Add "-O0" for vsprintf.c/kasprintf.c
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
While this may not be the final fix (it still has to go usptream and
be better explained), it gets us booting, so is good enough for the
time being.
(From OE-Core rev: 8610017e4e017ddc59d76e64c4d4557fcffc363e)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The -dev kernel is now tracking 4.2 content, so we update the
linux-yocto-dev recipes PV to match.
(From OE-Core rev: fc22f6ee38731e60b2bc15640fa697e5af663422)
(From OE-Core rev: 468fef1ccfcc5495b6d20576864269da0cdba948)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta SRCREVs for the following changes:
92977854ff52 graphics: disable CIRRUS DRM for qemumips and qemuppc
57f4dc4dfe16 intel-quark: Enable thermal support
(From OE-Core rev: 5c9d414fc8e88cd5ef8e7e530ba4c5e788e03bb7)
(From OE-Core rev: d0cc398d3cd47963fbe3fa22db0a1e73c162e67f)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta SRCREV to enable cirrus graphics emulation and wider
compatibility for the ext4 driver.
[YOCTO: #7348]
[YOCTO: #6667]
(From OE-Core rev: 530c51e5354d5cd233b7015a3d0dfe94cb9cbaa1)
(From OE-Core rev: db02cf0734ce059b7bf47edeb1107e23e20e7160)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the SRCREVs to import the latest 4.1-stable and 4.1-rt changes.
(From OE-Core rev: 21fd4093bbd0177453a1e749d825cf510746f201)
(From OE-Core rev: 576fb9f267f7dbca2b76a68903f335be108160e7)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.14 SRCREVs to match the latest kernel meta data updates
and also to merge four patches Richard Purdie located that fix the
gcc 5.x ARM build (we still have boot issues, but building is the
first step).
(From OE-Core rev: 24a888ddd04e44f8a069364bfbde06871ad33ae8)
(From OE-Core rev: b9509a02c4dae0fabbba730d3311bca29e353e4f)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.19 and 4.1 meta SRCREVs to pull in the coretemp
configuration values.
Partial fix for [YOCTO #8107].
(From OE-Core rev: 4511961afca854d8006c0d058f46f8ba46f277c4)
(From OE-Core rev: 39eff54fec9a90c9a5f49d8beb643ec9152add2e)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With the recent changes to the kernel meta data handling and the
removal of BSP branches, we need to shuffle some patches around to
match.
This prevents patches from being applied twice, and the qemuarm BSP
can be configured for preempt-rt.
[YOCTO: #8122]
(From OE-Core rev: b6b7a80440521a8e82cfe6c56dddedf061de6208)
(From OE-Core rev: f18b19e1be0b84d431328f87ec4a694ac1415469)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Remove backport patch filemode-fix.patch.
* Update --with-kernel=${STAGING_DIR_HOST}/${prefix} to find kernel
headers (linux/*.h) to fix the error:
| checking kernel supports perf_events... unknown -- perf_event.h not found
| ERROR: You requested to build oprofile with '--with-kernel=/buildarea/lyang1/test_f2/tmp/work-shared/qemux86/kernel-source',
| but headers were not accessible at the given location.
| Be sure you have run the following command from within your kernel source tree:
| make headers_install INSTALL_HDR_PATH=<kernel-hdrs-install-dir>
| Then pass <kernel-hdrs-install-dir> to oprofile's '--with-kernel' configure option.
| configure: error: Unable to build oprofile. Exiting.
(From OE-Core rev: b2200152deef0aec3cd8fe55bb73d6e8fccfe159)
(From OE-Core rev: 2dff13e834dc7b67e16ee597d7f9a3efdc72d10f)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add a patch which updated add LDFLAGS variable to SLDFLAGS
in Makefile.
(From OE-Core rev: 6bf2743a967ede08d19f9ca1f72e36e806e92fb0)
Signed-off-by: Noor Ahsan <noor_ahsan@mentor.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A recent commit fixed perf build failures with a change that duplicates
a fix that can be found in kernels after 4.1. Unfortunately there is a
conflict between these two fixes and we see perf build failures when
building perf in kernels that contain the fix already. The problem is
that the fix from the recipe modifies the location of .config-detected
to $(OUTPUT).config-detected. In a 4.2 kernel the location will be
changed to $(OUTPUT)$(OUTPUT).config-detected.
We change the recipe to require a space in the pattern to only change
kernel sources that do not already place file in $(OUTPUT).
The recent commit that introduced the build failure is:
commit ea9016b60b47138bc58d84a06954b44527b20a19
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Sat Jul 25 14:37:58 2015 +0100
perf: Fix config file conflict with 4.1 kernels
If you setup mutlitlibs and then:
bitbake perf libb32-perf
bitbake perf libb32-perf -c cleansstate
bitbake perf libb32-perf
you will see races where the two builds get confused about which directory
they should be using and they corrupt each other.
The issue is that .config-detected is created in ${S}, not $(OUTPUT).
We can fix this by moving the file to $(OUTPUT).
[YCOTO #8043]
(From OE-Core rev: 00608cffffb586e8d2a2075117e710113c471448)
(From OE-Core rev: 57df1ebd910e42af47a0039830a60f41a3bd29b6)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The commit in the kernel source that fixes the problem from kernel side is:
commit 642273795fa81da11290ffa90bce6ff242f2a7bb
Author: Aaro Koskinen <aaro.koskinen@nokia.com>
Date: Wed Jul 1 14:54:42 2015 +0300
perf tools: Create config.detected into OUTPUT directory
Create config.detected into OUTPUT directory instead of source
directory.
This fixes parallel builds that share the same source directory.
Signed-off-by: Aaro Koskinen <aaro.koskinen@nokia.com>
Acked-by: Jiri Olsa <jolsa@kernel.org>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: http://lkml.kernel.org/r/1435751683-18500-1-git-send-email-aaro.koskinen@nokia.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
(From OE-Core rev: cb8d309ff0ea0ca11edc2aae75ddd869491cb330)
Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The source tarball should be listed first.
(From OE-Core rev: 3f5d6405a0f4a5de14f7aebe430160c2256bf218)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop patch merged upstream and part of x32 patch merged upstream.
Refresh patches.
(From OE-Core rev: ae831faa25fa7bbe8ebff313f1ae6e862bcbe602)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With kernel commit 6c6f0f6164f [tools build: Add feature check for lzma
library], perf now performs a test for lzma and adds functionality
appropriately.
This currently is a floating dependency that will sometimes be present,
and sometimes not. The result is the following QA warning:
WARNING: QA Issue: perf rdepends on liblzma, but it isn't a build dependency? [build-deps]
By adding xz to the DEPENDS, we'll ensure that it is consistently in
place.
[YOCTO: #8045]
(From OE-Core rev: 2b7bf357e126bf272504548a4692cf764fd7f8ea)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the linux-yocto kernel recipes to include a named/versioned 4.1
recipe. This will be the LTSI kernel, and the 3.14 and 3.19 kernels will
be removed in subsequent commites (once reference boards have transitioned).
(From OE-Core rev: c027c1283e6444ab05f444eb5d292ec1a36b5821)
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:
cbd4b7102668 patchme/updateme: unify meta directory handling
b65075997152 configme: standalone operation
The change of note is [configme: standalone operation], which makes the
kernel configuration script free from dependencies on other parts of the
kern-tools.
With this change, we set the stage to extend kernel configuration
fragments and auditing to arbitrary trees.
(From OE-Core rev: 17f071dea78a08648eda71829c845104338510b9)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The linux-yocto tree has always been a combined set of kernel changes
and configuration (meta) data carried in a single tree. While this
format is effective at keeping kernel configuration and source
modifications synchronized, it isn't always obvious to developers on
how to manipulate the meta data versus the source.
With this change, we remove the meta data processing from the
kernel-yocto class and use the external meta-data repository that
has always been used to seed the linux-yocto meta branch.
After this change, linux-yocto can no longer process combined trees,
and is simplified as a result.
(From OE-Core rev: 523e4f6a6913b64453579d27a02467e14f7df42e)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If you setup mutlitlibs and then:
bitbake perf libb32-perf
bitbake perf libb32-perf -c cleansstate
bitbake perf libb32-perf
you will see races where the two builds get confused about which directory
they should be using and they corrupt each other.
The issue is that .config-detected is created in ${S}, not $(OUTPUT).
We can fix this by moving the file to $(OUTPUT).
[YCOTO #8043]
(From OE-Core rev: 00608cffffb586e8d2a2075117e710113c471448)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the libc-headers to match the 4.1 LTSI kernel version.
We also tweak the logic in linux-libc-headers.inc to look in the
4.x subdirectory if a 4.x kernel is specified as the header source.
(From OE-Core rev: 3143920c541b55b543b9dcc12b18af4e0e4b7ae1)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Remove add-aarch64.patch since it is already in the source.
* Rename lttng-ust_2.6.1.bb -> lttng-ust_git.bb
(From OE-Core rev: f5b03208c0ae0f47dddec6e39712fb0f1d041ebc)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When run "kexec" in powerpc board, the kexec has a limit that
the kernel text and bss size must be less than 24M. But now
some kernel size exceed the limit. So we need to change the limit,
else will get the error log as below:
my_load:669: do
Could not find a free area of memory of 0x12400 bytes...
Could not find a free area of memory of 0x13000 bytes...
locate_hole failed
(From OE-Core rev: 8458910b3524eeb5164137332f60ba40247c33fa)
Signed-off-by: Quanyang Wang <quanyang.wang@windriver.com>
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If the GCC's stack protection is enabled by default, the purgatory will
also be built with this option. But it makes no sense to enable this
for the purgatory code, and would cause error when we are trying to
relocate the purgatory codes because symbol like __stack_chk_fail is
unresolved. Instead of disabling this for some archs specifically,
disable it for all the archs.
(From OE-Core rev: 466b0b2c572fb3201ca415b689ce7a950b8625a7)
Signed-off-by: Kevin Hao <kexin.hao@windriver.com>
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Rename recipe name from lttng-modules_2.6.1.bb to lttng-modules_git.bb
(From OE-Core rev: 180ce6570ba133ec5f36de3288d6ec163b54eefe)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the 3.19 SRCREVs for the following fixes:
e152349de59b drm/i915: Reset CSB read pointer in ring init
a87a6ffb3459 drm/i915/bdw: Enable execlists by default where supported
a70b2eb273ef meta: axxiaarm: add configuration fragments
(From OE-Core rev: 1b3d77195210d7d2b17c1bb8ab756053d72c7d4c)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.14 SRCREVs for the following commits:
7534aeb01883 yaffs2: fix memory leak in mount/umount
4287412436cb MIPS: Fix build with binutils 2.24.51+
(From OE-Core rev: 370cd615ea3aa11d39e4c7303e8bca79e3ec6621)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This recipe doesn't unpack any source, so set S to ${WORKDIR}.
(From OE-Core rev: b82d60aa19ecbe1e4fed6a1ce7077b3d6c620ef4)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is because S = "${STAGING_KERNEL_DIR}".
(From OE-Core rev: 7c92e64834af8f578b5cfc3cfe33c13bb8a89754)
Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fix timer calculation error in the lttng-tools/lttng-ust
(From OE-Core rev: 780a590cf2f0604435c05445d02c342e3387497f)
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The current kernel supports WERROR now, and there is no Werror in
tools/perf/Makefile, remove both sed commands.
(From OE-Core rev: 664508e6307903fdc3054ca84d37f16718c41ede)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This fixed the bug https://bugs.lttng.org/issues/790
(From OE-Core rev: 8152bcadba8581f75822b75e13c2a43dd6464cd3)
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The lttng-modules Makefile allows us to specify the kernel we're
building against via the KERNELDIR variable on the build command line.
Use that and drop the patch (which tends to need updating whenever the
upstream Makefile changes).
(From OE-Core rev: cc6f6f96b668f7ef3db0f83c7d3585d81c569d31)
Signed-off-by: Nathan Lynch <nathan_lynch@mentor.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(From OE-Core rev: 032402438befd5906d05fed843bab9520bf7fc3e)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(From OE-Core rev: a798e98a3e95f896f5cf30a547c56aaf5526bf33)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the linux-yocto SRCREVs to integrate fixes for the h/w reference
BSPs to the 3.19 kernel.
(From OE-Core rev: 4c992854414360a10e1b452c9a776cbd993dee1f)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(From OE-Core rev: 01c7a7c013c4ee56f06fb7b5ab683066d8cb62f8)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Pull out the compilation of the DTB blobs right after the kernel's
own do_compile function finishes. This makes them available just in
time for the kernel image construction functions.
(From OE-Core rev: 86b3f29f93e3f87903668ea317c6bd97be4cdf62)
Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Ross Burton <ross.burton@intel.com>
Cc: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.19 kernel SRCREVs for the following commits:
NFC:
727cfce45077 meta: intel-common: enable generic NFC support
f3e890065903 meta: features/nfc: add generic configuration for NFC support
Braswell:
d3c0b958e688 drm/i915: New offset for reading frequencies on CHV.
dac6babbba62 drm/i915/chv: Populate total EU count on Cherryview
Axxia:
c706cb356dea arch/arm/axxia: Remove the axxia zImage.fm build
45a1aaacf6cb drivers/hwmon: Remove adt75 redundant driver
7203ee166c01 arch/arm/mach-axxia: Fixed L2 power up failure
a1541e9f0a4c kernel/irq/manage.c: Fix irq_set_affinity to allow use with buslocks
d42c0bd1c8be arch/arm/mach-axxia: Reverse checkpatch compatibility
5dbd07431a7a arch/arm/mach-axxia: changed affinity parameter to cpu
23e4ebc66acb char: hwrng: AXXIA TRNG driver added for AXM55xx
61eb3c8ee1d7 arch/arm/mach-axxia: Updated Axxia 55xx PCIe driver to use correct Doorbell interrupt IRQs
b03e0655094a AXM55xx RapidIO : Added support for Device revision and link down Monitor.
7577ad26cf73 rionet: Fix the corruption of tx_cnt during Transmit.
07fd2163ae56 arch/arm/mach-axxia: fixed NO SMP
c9371e98cc80 arch/arm/mach-axxia: fixed compiler warning
0a814fe7e747 arch/arm/mach-axxia: Updated PCIe driver doorbell support
cd3d9b46bea4 misc: lsi-ncr: Only use AMP lock on PPC platforms.
826c600c6ad6 fs: vmfs: Use generic mmap function
e2d0047cb106 arch/arm/mach-axxia: Removed axxia_circular_queue
f1ff06eaabed ARM: axxia: Add cluster and L2 power off in hotplug
b98711344263 ARM: irq: Return error when set_affinity is called from hotplug
9fd9306a30ae arch/arm/mach-axxia: Enable L3
68989d446582 Revert "arch/arm/mach-axxia: Fixed affinity error on IRQ migration"
0be0ef90a887 Revert "arch/arm/mach-axxia: fixed failure to power up cluster"
1c6522a03e81 Revert "arch/arm/mach-axxia: fixed hang in preempt kernel"
ef06a68393a3 fs/vmfs: Changes to add VMFS support for axxia.
3025e9deede6 drivers/usb/host: Changes to support the axxia BSP
b128b4f0d4e8 drivers/tty: Changes to support the axxia BSP
d1b60a7e62ef drivers/hwmon: Changes made to support the axxia BSP
2899ccbf1438 drivers/spi: Changes to support the axxia BSP
8e9cff566254 drivers/rapidio/devices: Changes to support axxia BSP
3424d2ca2653 drivers/net/ethernet: Changes to support the axxia BSP
2353dc816d6b drivers/mtd: Changes to support the axxia BSP
4b5fa2bf86cf drivers/misc: Changes made to support axxia BSP
8a5bd53ec241 drivers/i2c: Changes to support axxia BSP
02bfe1548d1a arch/arm/drivers/edac: Changes to support axxia BSP
2431db7c0c90 arch/arm/drivers/dma: Changes to support the axxia BSP
61fa3f268d5c arch/arm: arm changes to support the axxia BSP
22e0fb7be665 arch/arm/mach-axxia: add power management support
5cab63c5a1f2 arch/arm/mach-axxia: kernel files to support the mach-axxia
1336aba51616 arch/arm/boot: Changes to support the axxia BSP
97324fa920cb arch/arm/boot/dts: Files added to support axxia 5500 board
(From OE-Core rev: b74dafa8a3aad069140978420c535c18e89a964b)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Integrating the following commit to remove a ATA configuration warning:
common-pc-drivers: Enable CONFIG_ATA_BMDMA
Enabling the ATA_BMDMA re-enables ATA_PIIX which was getting
disabled
Signed-off-by: Saul Wold <sgw@linux.intel.com>
And the following to fix the ARM64 gcc5 boot:
arm64: psci: move psci firmware calls out of line
An arm64 allmodconfig fails to build with GCC 5 due to __asmeq
assertions in the PSCI firmware calling code firing due to mcount
preambles breaking our assumptions about register allocation of
function
arguments:
/tmp/ccDqJsJ6.s: Assembler messages:
/tmp/ccDqJsJ6.s:60: Error: .err encountered
/tmp/ccDqJsJ6.s:61: Error: .err encountered
/tmp/ccDqJsJ6.s:62: Error: .err encountered
/tmp/ccDqJsJ6.s:99: Error: .err encountered
/tmp/ccDqJsJ6.s💯 Error: .err encountered
/tmp/ccDqJsJ6.s:101: Error: .err encountered
This patch fixes the issue by moving the PSCI calls out-of-line into
their own assembly files, which are safe from the compiler's
meddling
fingers.
Reported-by: Andy Whitcroft <apw@canonical.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Armin Kuter <akuster@mvista.com>
(From OE-Core rev: 3977a70c197bf0d853ea9eb01f2185ae2c75ca4f)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.19 kernel SRCREVs to integrate the following Braswell
changes:
374b5d0e09ea drm/i915: Only wait for required lanes in vlv_wait_port_ready()
fca99e8ee111 Revert "drm/i915: Hack to tie both common lanes together on chv"
00682f31b612 drm/i915: Work around DISPLAY_PHY_CONTROL register corruption on CHV
654b1a4497c5 drm/i915: Implement chv display PHY lane stagger setup
(From OE-Core rev: 211b631b0d7bf4df3152f4d8d626d798d023d512)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.14 SRCREVs to integrate the latest round of cavium
support patches, as well as configuration backports from 3.19.
(From OE-Core rev: df552f18cf9852e0f04780399b78605c8085d935)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This fixes a build issue with the 3.19.5 kernel where the regmap prototypes
have changed. The patch is rebased do to changes in the new version of the
Makefile.
[YOCTO #7737]
(From OE-Core rev: 787fde133c6b50c5df6ce8f90b2906b7955b41e4)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed when rebuild:
| NOTE: make prefix=/usr bindir_relative=bin libdir=lib NO_PYTHON=1 gui clean
| make: *** No rule to make target `sysroots/x86_64-linux/usr/lib/i586-poky-linux/gcc/i586-poky-linux/4.9.2/include/stddef.h', needed by `event-parse.o'. Stop.
| ERROR: oe_runmake failed
(From OE-Core rev: 6cb0e401f0bfc962eb9f57988fd93f0b0d43c79b)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If we have DEPENDS = "virtual/kernel" is means that the kernel module
depends on the kernel's do_populate_sysroot task. This is not entirely
desireable since that depends on do_install which depends on
do_compile_kernelmodules and so on. In a situation where rm_work in involved
this can cause some pretty length build cycles after the kernel workdir
has been cleaned up by rm_work.
As well as removing this, take the opportunity to clean up duplicated
dependency lines, tweak the dependency of make_scripts for the same
reason and generally try and make things more readable.
(From OE-Core rev: a641247d262971db2d44815c5a668e7e50bdaf4f)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the SRCREVs to import the following fix:
mips: define cpu_has_saa in common features include
To avoid build failures such as the following on non-cavium
platforms:
| arch/mips/include/asm/atomic.h: In function 'atomic_add':
| arch/mips/include/asm/atomic.h:52:6: error: 'cpu_has_saa'
| undeclared (first use in this function)
| if (cpu_has_saa) {
| ^
We define a disabled cpu_has_saa unless the machine specific feature
overrides define a value.
(From OE-Core rev: b2f786ca319714bd41d6f9e7ba9efaa8a6d412ab)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating to include the following commits:
a4d0c407cced dmaengine: dw: don't handle interrupt when dmaengine is not used
e92b2ce791b2 dmaengine: dw: define DW_DMA_MAX_NR_MASTERS
931304a6567e dmaengine: dw: provide DMA capabilities
468bad4f7a6f dmaengine: dw: Split device_control
b4afd7710db7 i2c: i801: Use managed pcim_* PCI device initialization and reservation
d81a8a11ecba i2c: i801: Remove pci_enable_device() call from i801_resume()
40e18604e70c i2c: i801: Use managed devm_* memory and irq allocation
b54f65dbe57b i2c: i801: Remove i801_driver forward declaration
e95740d4d079 i2c: i801: Don't break user-visible strings
423e98721e04 ACPI: Introduce has_acpi_companion()
291f620dc052 i2c: designware: Suppress error message if platform_get_irq() < 0
cf5ff51a8e3f i2c: designware-pci: no need to provide clk_khz
4f583ce420d3 i2c: designware-pci: remove Moorestown support
e000c549c9d8 i2c: designware: Add Intel Baytrail PMIC I2C bus support
7ffbd9ca19a7 i2c: designware: fixup return handling of wait_for_completion_timeout
5758d5a1df32 i2c: designware: Do not calculate SCL timing parameters needlessly
2f58fcae92db i2c: designware: Add i2c bus locking support
84a73e51e900 i2c: designware: use {readl|writel}_relaxed instead of readl/writel
f672bb8424e6 serial: 8250_dw: Fix get_mctrl behaviour
91bd64585489 serial: 8250: add support for ACPI-probed serial port for X-Gene platform
1190cba71f09 serial:8250:8250_pci: delete unneeded quirk entries
6405a4b71451 serial:8250:8250_pci: fix redundant entry report for WCH_CH352_2S
0a1a31bbbc19 serial: 8250_pci: remove one useless explicit type conversion
4edc52a55f82 intel_idle: Add support for the Airmont Core in the Cherrytrail and Braswell SOCs
934f85e8bfdb x86/irq, ACPI: Implement ACPI driver to support IOAPIC hotplug
c6a3440252a8 ACPI / LPSS: check the result of ioremap()
6aacc0c931b7 pinctrl: update direction_output function of cherryview driver
cb4a43a2177d pinctrl: cherryview: Configure HiZ pins to be input when requested as GPIOs
0df22c007ce1 pinctrl: intel: drop owner assignment from platform_drivers
07b16f04700b pinctrl: cherryview: Save and restore pin configs over system sleep
e8e5cfffa231 pinctrl: baytrail: Save pin context over system sleep
04cb3cc0ff21 pinctrl: baytrail: Rework interrupt handling
4cac25d2574d pinctrl: baytrail: Clear interrupt triggering from pins that are in GPIO mode
eacab9ab234a pinctrl: baytrail: Relax GPIO request rules
(From OE-Core rev: d2dd36bafdef7b0424041f5369706b9152ea13da)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The way that perf detects features has changed/moved via commit e6c76d620
[perf build: Move feature checks code under tools/build].
This code movement resulted in the definition of CC being dropped, and
in turn the passing of --sysroot not part of the build.
This results in feature tests failing with errors such as:
In file included from test-pthread-attr-setaffinity-np.c:1:0:
sysroots/x86_64-linux/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/4.9.2/include/stdint.h:9:26:
fatal error: stdint.h: No such file or directory
# include_next <stdint.h>
^
compilation terminated.
While the fix is going upstream, we can modify the perf recipe to add
the definition of CC into the Makefile, and we'll continue to work on
patched and unpatched kernels.
Upstream-status: Pending
(From OE-Core rev: 46f842039422aa35f62b03f11b648c02980ea1b1)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the configuration for the common x86 platforms to always
include core bluetooth support.
(From OE-Core rev: 388de1bfa1de1086d500aa8b2d4ece69cce6d5f6)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Gortmaker refreshed the 3.14-rt support to the latest rt stable
content.
With these SRCREV bumps, the 3.14 LTSI kernel is now at -rt37.
91dc6afcecd4 rt: bump localversion from 32 to 37
e69f7430b620 rt: bump localversion to 32
c060800318e4 netpoll: guard the access to dev->npinfo with rcu_read_lock/unlock_bh() for CONFIG_PREEMPT_RT_FULL=y
833c21beba79 Revert "timers: do not raise softirq unconditionally"
6c9337ff352c fs,btrfs: fix rt deadlock on extent_buffer->lock
2d542663bfb9 staging: Mark rtl8821ae as broken
988e4701df83 timers: Reduce future __run_timers() latency for first add to empty list
2549262883c5 timers: Reduce future __run_timers() latency for newly emptied list
073fac19d3e4 timers: Reduce __run_timers() latency for empty list
25ca11173e64 timers: Track total number of timers in list
277a4ae36580 fs/aio: simple simple work
7b2ebc4e590b lockdep: selftest: fix warnings due to missing PREEMPT_RT conditionals
9afc01954298 thermal: Defer thermal wakups to threads
84d35d05b236 locking: ww_mutex: fix ww_mutex vs self-deadlock
f0c8e4837a51 Revert "rwsem-rt: Do not allow readers to nest"
df0d51ecf13f sunrpc: make svc_xprt_do_enqueue() use get_cpu_light()
f069e339ca02 work-simple: Simple work queue implemenation
0d9e6cbead39 scheduling while atomic in cgroup code
8405cdab8c2c sas-ata/isci: dont't disable interrupts in qc_issue handler
dfb7e1ab2427 mips: rt: Replace pagefault_* to raw version
ddbe4584a13b ARM: cmpxchg: define __HAVE_ARCH_CMPXCHG for armv6 and later
607f2a27c2ee arm/futex: disable preemption during futex_atomic_cmpxchg_inatomic()
58de8f60159f ARM: enable irq in translation/section permission fault handlers
62d90b45607c x86: UV: raw_spinlock conversion
e8d164191f65 rtmutex: enable deadlock detection in ww_mutex_lock functions
9612daf936db rt,locking: fix __ww_mutex_lock_interruptible() lockdep annotation
47915a120d41 rtmutex.c: Fix incorrect waiter check
a6a68d53df5f locking/rt-mutex: avoid a NULL pointer dereference on deadlock
fb2c256f8a91 futex: Simplify futex_lock_pi_atomic() and make it more robust
7e59d4d5900e futex: Split out the first waiter attachment from lookup_pi_state()
45ccc2e3f25f futex: Split out the waiter check from lookup_pi_state()
c5133997a345 futex: Use futex_top_waiter() in lookup_pi_state()
4726c8b47964 futex: Make unlock_pi more robust
b55c2c7782ee rtmutex: Avoid pointless requeueing in the deadlock detection chain walk
ff7cfbb757d4 rtmutex: Cleanup deadlock detector debug logic
e80ba665fa71 rtmutex: Confine deadlock logic to futex
7a9e7c37ccf4 rtmutex: Simplify remove_waiter()
d664c14c1db3 rtmutex: Document pi chain walk
64bcb809c720 rtmutex: Clarify the boost/deboost part
02323ee362c4 rtmutex: No need to keep task ref for lock owner check
063983fb0497 rtmutex: Simplify and document try_to_take_rtmutex()
f87319b715f1 rtmutex: Simplify rtmutex_slowtrylock()
de9723ae23f9 gpio: omap: use raw locks for locking
705ad635f56a rt: bump localversion from 22 to 31
22b5a5cda73a mm/page_alloc: fixup warning from stable merges to -rt
(From OE-Core rev: aa1900021aa05ce1d5b8e607de094ae7cf3fcd10)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
An alternative approach with NO_GENERIC_LICENSE has been added
in license.bbclass to allow copying non-generic license,
add it for all firmware licenses.
(From OE-Core rev: f2e92c741bde70753163afe3839ff8d35ae5380e)
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is aready in the source.
(From OE-Core rev: 4ac3e70f8f39dc6b585e0acb3679d4137f60b296)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Confirmed with the author Qi, it isn't needed.
(From OE-Core rev: 6ee6c39df4dea2dcd99cccad771e1326465e96dd)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is possible that recipe specific tasks, or build processes drop
files into the kernel source directory. These files can cause problems
with the meta data detection in the kern-tools.
With this change, we have a single unified meta data detection routine,
that logs the result in a new file ".metadir", which subsequent scripts
can find, and use, thereby avoid repeating the same check many times.
We also enhance the check to look for a sentinel file in a proper meta
directory, to avoid false positives when an unexpected kernel process
leaves an uncommitted directory in the kernel dir.
[YOCTO: #7441]
(From OE-Core rev: 6b04ae2c0439b83c0445fd1b8cb9cba5cee6b9bc)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The linux-yocto.inc may remove the meta dir:
do_install_append(){
if [ -n "${KMETA}" ]; then
rm -rf ${STAGING_KERNEL_DIR}/${KMETA}
fi
}
Which may cause the error:
[snip]
find: `./meta/cfg/kernel-cache/bsp/altera-socfpga/0073-FogBugz-116676-Align-clk.c-with-kernel.org.patch': No such file or directory
find: `./meta/cfg/kernel-cache/bsp/altera-socfpga/0047-FogBugz-90657-Fix-SD-MMC-driver-for-VT.patch': No such file or directory
find: `./meta/cfg/kernel-cache/bsp/altera-socfpga/0006-spi-qspi-cadence-Add-spi-and-qspi-driver.patch': No such file or directory
[snip]
cpio: ./meta/scripts/kgit-config-cleaner: Cannot stat: No such file or directory
cpio: ./meta/scripts/kgit-s2q: Cannot stat: No such file or directory
cpio: ./meta/scripts/kgit-clean: Cannot stat: No such file or directory
[snip]
(From OE-Core rev: 0866086c6a9d9f518388f2962db784ab15d49330)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the linux-yocto 3.19 SRCREVs to integrate the 3.19.5 korg
stable updates, as well as the following meta data changes:
205aca0c1241 meta: intel-common: Enable USB-based Bluetooth hardware
b6a810e8e808 meta: features/bluetooth: add support for USB Bluetooth hardware
767f3fa34680 common-pc-drivers: Add CONFIG_EEPROM_AT24
e308b2c52519 intel-core*: Add Braswell soc support
8c1c74d5052b braswell: Add features/soc/braswell
(From OE-Core rev: 2b163b8bbe8363e24f951ec507691ac692bc80b0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This will ensure that compiler does not initialize the definitions
in header files
Change-Id: I1076201c667f96707c320a51a77d4a70e22df750
(From OE-Core rev: 2e9a4198fc9a9fcc78eddb6cd5c2ad51a2e8d3e7)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Remove 0002-In-the-3.13-rc1-Linux-kernel-the-INIT_COMPLETION-mac.patch
since it was a backported patch.
* Updated 0001-Add-the-compile-and-install-rules-for-cryptodev-test.patch.
(From OE-Core rev: 9347311ca444c3128653c96f9f2845713c646fa7)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Each firmware has their own license, it was a kind of a mess to
leave the license as Proprietary and we got a lot warnings like:
WARNING: The license listed Firmware-atheros_firmware was not in the
licenses collected for linux-firmware
To fix this and make it more clear:
- Fix some incorrect license names.
- Add all license files into common-licenses in previous commit.
- Add all licenses and their md5 values in alphabetical order.
- Add pn-*-license to split up per firmware package and pn-license for others.
- Re-order the codes for each split-out firmware as:
LICENSE_*, FILES_*, RDEPENDS_*
[YOCTO #7539]
(From OE-Core rev: 1ee083da0730408fffdbbf5f29abc299c0e61be9)
Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The following patches are rebased.
-- Change-to-calling-bswap_-instead-of-htobe-and-be-toh.patch
-- avoid_parallel_tests.patch
The ptest part of kmod is removed because new version of kmod port all tests to
use modules from module-playground instead of copying prebuilt modules to the
repository. So, we cannot use ptest as before. Remove it so that kmod can build
successfully.
(From OE-Core rev: f80d136bdd578468035a88125fa1b84973fd912b)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add autoconf test for detect when build is x32 ABI this enables to
test into purgatory Makefile to avoid use -mcmodel=large flag in CC.
Add ELFCLASS read and syscall number into kexec, see patch.
[YOCTO #7419]
(From OE-Core rev: 7b75430c2e3ffedb9ef4198fabf259b757b9ce5a)
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The kernel_configme task was added twice (once in the .bbclass, one in a .inc)
with different ordering constraints.
Change this to be just one definition in the bbclass with the stronger ordering
constraints.
(From OE-Core rev: b9646b9d31c3e0c70337a8c10ebfc087a0e2b829)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The autobuilder failed like this:
temp/run.do_kernel_metadata.25242: line 165: createme: command not found
createme is provided by kern-tools-native. do_patch has a dependency on
kern-tools-native, but do_kernel_metadata runs before do_patch. So move the
dependency from do_patch to do_kernel_metadata, moving the statement from the
.inc to the class so it's alongside the task definition.
[ YOCTO #7531 ]
(From OE-Core rev: 4a0371847ff0c30d9b60db63559d89dddfcb009f)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.19 meta branch to include the following configuration
change to deal with kernel configuration audit warnings:
9e70b482d377 romley: remove common video and media config items
8a4e096759ad intel-common: remove eg20t from common config
c2f5ab15620c drm-cdvpvr: Add STAGING_MEDIA
ac4693c1db39 media: Prefer modules(m) to yes(y) and update for 3.19 Kernel
(From OE-Core rev: aa57c02e12a3ecd26eff410f70de28013aed2e00)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.14 SRCREVs to import the v3.14.36 korg stable changes and
configuration changes to the meta branch.
(From OE-Core rev: 3ca86a30bcbdf59753b7ad611d5e307b65d3c0f6)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.19 SRCREVs to pick up the korg 3.19.2 release, as well
as the following meta data changes:
ed82e1ac3196 features: soc: fix typo in baytrail.cfg
76bc151242d7 tiny.cfg: Enable BINFMT_SCRIPT
(From OE-Core rev: 486c40b6d9566e882c841f0cb398612ba70256e7)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a patch for fix printing of time_t value that is long long int
in x32 ABI instead of long int.
[YOCTO #7423]
(From OE-Core rev: 194f0be44fa37605d0b5897138848fa378593d62)
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
perf has a dependency on bash in its utilities, which generate the
following warning:
WARNING: QA Issue: perf requires /bin/bash, but no providers in its RDEPENDS [file-rdeps]
Since perf is not installed on extremely small systems, we just add
bash to the RDEPENDS, rather than modifying scripts or removing content.
[YOCTO: #7445]
(From OE-Core rev: 6f39aae20d88a2d764c3a85617cd36b81af804f1)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating to the latest and greatest -stable release for the 3.19 series.
(From OE-Core rev: 1e60b5216a89a34eba7749244eeb53d5d12864eb)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When fixing a kernel configuration warning, it is often necessary to
modify the kernel's meta-data and re-run the tools to update and
re-audit the config. This implies that the patch, config and audit
steps are run multiple times.
The tools had a bug that would incorrectly restore old meta-data
versus using updated configuration. Updating the kern-tools SRCREV
to fix the issue.
(From OE-Core rev: b903559daa847d2c56bf729fc5ca885113d0eecc)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(From OE-Core rev: b9a97b56400d156bc670d933323d0e28ffb17960)
Signed-off-by: Maxin B. John <maxin.john@enea.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Applying the existing ARM patch for armeb makes it work.
(From OE-Core rev: 33a576a85b2d37dafadabf3f1472cd3c3b42f6b6)
Signed-off-by: Koen Kooi <koen.kooi@linaro.org>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This reverts commit 2d9763a1c8.
There are a few parallel issues:
1)
../rbtree.o: error adding symbols: Invalid operation
collect2: error: ld returned 1 exit status
Makefile:42: recipe for target 'btt' failed
2)
git/blkiomon.c:216: undefined reference to `rb_insert_color'
collect2: error: ld returned 1 exit status
Makefile:27: recipe for target 'blkparse' failed
3)
ld: rbtree.o: invalid string offset 128 >= 125 for section `.strtab'
4)
btreplay.o: file not recognized: File truncated
collect2: error: ld returned 1 exit status
btreplay/btreplay.c:47:18: fatal error: list.h: No such file or directory
(From OE-Core rev: 35bb619486d7f5721e8fa86c8744d4cea4d1746a)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This prevents the "Warning: No tracing group detected" message
from lttng when there is no group 'tracing' while using lttng
on the target.
(From OE-Core rev: 8fef1e991f9ea6f0ad6110aab77bc9ab0b4e7d23)
Signed-off-by: John Mehaffey <mehaf@gedanken.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The file ownership needs to be explicitly set otherwise it inherits
the user and group id of the build user.
(From OE-Core rev: 9ce5b600cb1663f8c2a625c7f7c08ab3e61b58c8)
Signed-off-by: Jonathan Liu <net147@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This address issues with the 3.19 kernel and the number of patches to
back port would be to great
[YOCTO #7401]
(From OE-Core rev: 7ec29a4dbcc62a928c517bd968c499e325580bfe)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update the SRCREV for the following incremental improvement in patch
processing time:
kgit-meta: skip patches on non-leaf nodes
In a similar way as commit 0768d697 [kgit-meta: dont run kgit-s2q
for
non-leaf nodes], we can save even more processing time by not even
analysing and linking patches if we aren't on the leaf node of the
tree.
This early exit can save nearly 95% of the time required to "patch"
a tree when no changes are actually applied.
(From OE-Core rev: 148c78e0f5de2689de3ad9beaa9f6de618d87758)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With these SRCREV updates, we add the following support to the kernel:
The following has been verified with the branch sources:
On 68xx:
* SGMII, XAUI Packet IO interfaces.
* PCIe devices
* EHCI/OHCI USB driver
On 78XX:
* Ran LTP testsuite
* SGMII, XAUI Packet IO interfaces
* MMC driver (which covers GPIO interrupts in the driver)
* PCIe devices
* XHCI USB driver
(From OE-Core rev: c32023e75b1cd722f3fca226ec8651dc10cf9dab)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We don't require that a yocto custom kernel + defconfig have a full BSP
description (but of course it would be better if they did). Since this
isn't a requirement, we shouldn't alarm users by generating a BSP
description warning.
To implement this, we add a bsp audit level flag (like the one that
exists for kconfig audits), and only set it to activate in the versioned
linux-yocto recipes.
[YOCTO: #7370]
(From OE-Core rev: d2fb7fff291b83700d487be093223c1533d915ce)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
During the 3.19 update a 32 bit option in the 64 bit config was missed,
which results in the option being dropped (and reported as a warning):
Value requested for CONFIG_PCI_GOANY not in final ".config"
Requested value: "CONFIG_PCI_GOANY=y"
Actual value set: ""
So we split the 32bit only drivers out of the common driver include and
the problem goes away.
[YOCTO: 7354]
(From OE-Core rev: 4dc9bde20602c7565979c7ebdea1a36c7ab3f458)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed:
lttng-tools-2.6.0: lttng-tools-ptest rdepends on libkmod, but it isn't a build dependency? [build-deps]
lttng-tools-2.6.0: lttng-tools rdepends on libkmod, but it isn't a build dependency? [build-deps]
(From OE-Core rev: a79d489a2fa532e6f87fe3cf0b55485fb08fd72e)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* refresh/cleanup the patch to apply cleanly on 2.0.9
* get rid of configure - it's autogenerated
* configure.ac: use aarch64* wildcard
(From OE-Core rev: 66457319e4050fee569aeccd1fe98fbf9f046f02)
Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Update to version 2.5.3 to match trace-cmd.
Changes include:
- Remove kernelshark-fix-syntax-error-of-shell.patch (the syntax error
is no longer present in the new version).
- Specify bindir_relative and libdir in EXTRA_OEMAKE as in the
trace-cmd recipe so files get installed to the right place.
Additionally, remove unnecessary EXTRA_OEMAKE options.
- Fix up the do_install steps to remove the plugins directory; that
directory now lives under /usr/lib.
- Set NO_PYTHON=1 because building the ctracecmd Python module requires
swig, which is not available in oe-core.
(From OE-Core rev: 2f177644dab083bc5306bce1bf2ff2ef8851c862)
Signed-off-by: Ben Shelton <ben.shelton@ni.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating adds new features including the very useful 'profile' option.
Changes include:
- Remove addldflags.patch (already upstream in the new version).
- Remove make-docs-optional.patch (docs are built in a separate target
in the new version).
- Update SRC_URI, SRCREV, PR, and PV in the .inc file and don't
override them in the recipe.
- Fix a typo in LIC_FILES_CHECKSUM so 'endline' is properly defined.
- Drop PR.
(From OE-Core rev: 30eba39bd3b915477c584d8bebd194446497175e)
Signed-off-by: Ben Shelton <ben.shelton@ni.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Introducing the v3.19.x recipes for the validated linux-yocto kernel.
Build, boot and sanity testing was performed on qemu for all major
architectures.
(From OE-Core rev: 329a028bec428e8dc8cf3420c6e462de2898c8aa)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In accordance with the kernel release criteria we support the latest
mainline kernel + the last LSTI kernel + a development kernel.
3.19 will be introduced as the latest mainline, and 3.14 is the released
LTSI kernel, which means that we remove the 3.10 and 3.17 variants.
(From OE-Core rev: 19203a95f4b65e0a009a738fb4fc216e985a0835)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After a linux-yocto style kernel is configured, a kernel configuration
audit is executed to detect common errors or issues with the config.
This output used to be visible, but was made less obvious to not alarm
users unnecessarily (since some configuration issues are acceptable).
There are some classes of configuration issue that are worth being
visible, and that is specified configuration values that do not make the
final .config. These dropped options can result in any number of runtime
failures, so flagging them at build time makes sense.
The visibility of auditing is controlled by KCONF_AUDIT_LEVEL:
0: no reporting
1: report options that are specified, but not in the final config
2: report options that are not hardware related, but set by a BSP
The default level is 1, with level 2 and above being for BSP development
only.
If these conditions are detected, warnings will be generated as follows:
WARNING: [kernel config]: specified values did not make it into the
kernel's final configuration:
Value requested for CONFIG_SND_PCSP not in final ".config"
Requested value: "CONFIG_SND_PCSP=y"
Actual value set: ""
or
WARNING: [kernel config]: BSP specified non-hw configuration:
CONFIG_BLOCK
CONFIG_CFG80211_WEXT
CONFIG_CORDIC
CONFIG_CRC8
CONFIG_EFIVAR_FS
CONFIG_EFI_PARTITION
CONFIG_NET
CONFIG_NETDEVICES
CONFIG_PARTITION_ADVANCED
CONFIG_WEXT_CORE
CONFIG_WEXT_PROC
CONFIG_WIRELESS
At this point thse are only a warnings, since there needs to be time for
layers and configuration fragments to be validated against this new
check.
[YOCTO: #6943]
(From OE-Core rev: ad4d59495194b37bc510e9891bd14c0a2ac30dba)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the libc-headers now that the kernel has released.
(From OE-Core rev: b3721560fe523c144690ebfeb203b3735d0f6843)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I used a for loop to build these packages more than 520 times, these
recipes never failed.
(From OE-Core rev: 7957c5bc2771a763d26e50e716733c6335cef3c2)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(From OE-Core rev: 521ec7e979409f213cd98ed6015fdba2fce89243)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Adjust the patch since it was partially applied upstream (in
a different form) but not completely since the ppc specific
part was not applied.
(From OE-Core rev: d397ba39e6a5a7d42641d489917033c779816a1a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the SRCREV to import the following kern-tools patch:
kgit-meta: always clear series file on branch transitions
This was triggered by the patch optimization changes, that no longer
run do_patch if a leaf/final branch is not being processed.
Without this change, invalid patches, or already applied patches in
an existig series file will be re-used which leads to missing files,
or patch errors.
(From OE-Core rev: 762cf3beea5ff374e2ddf491e541f07129443af3)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>