5.18-rc2 has been released, so we bump the -dev kernel to allow
easier testing of our components against the latest korg.
(From OE-Core rev: 091f1356d0245dcafe2f01bd5dcccf3802aaccfb)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the -dev kernel to v5.17 to test the latest upstream
kernel.
(From OE-Core rev: c75b6116fae479abd2dbf0d5950e38a0b31b1832)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The "?=" assignment to KBRANCH in kernel-yocto.bbclass is selected prior to
the one in this recipe and makes it "master" as a result.
Change the KBRANCH assignment back to "=" as how it was done before.
(From OE-Core rev: c7a1004c7f7e86506ccd7d6d40f148931096461a)
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The -dev kernel used to only have standard/* branches, which were
managed similarly to linux-next. Which means, they are for testing
integration of patches, and are rebased as needed (typically on
version changes).
We now do some leading edge BSP development on the -dev kernel,
so the standard/* branches are not deleted, but are instead
archived with a version prefix v<kernel version>/standard/*
The branch renaming causes problems for maintained releases
(they'll jump forward to newer kernels), and for anything that
wants to specify a particular commit (-dev is AUTOREV by
design).
There's no reason why the branches can't start versioned at
this point, and that solves both problems. So we switch our
default branch to v5.16/standard/base now, and it will be
updated with each new version (we bump the version anyway).
(From OE-Core rev: 73174b29d414ab0b5921f4fcdf5aebb988f0daf5)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a PACKAGECONFIG to control which type of dt-validation
is installed (full, or wrapped).
This is currently in linux-yocto-dev, as 5.16 introduces
the functionality of required dt schema validation.
Other v5.16 providing recipes can use the base functionality
as they desire (with or without PACKAGECONFIG).
Over time, we can migrate the support the the core
kernel classes .. in particular when more providers are at
v5.16+
(From OE-Core rev: c12a91827e88230b4ec702a88534d4c51c1aabe3)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the version of -dev ot 5.16. We also pickup two new
dependencies to support kernel dtschema validation. This
requirement was introduced by kernel commit:
commit 53182e81f47d4ea0c727c49ad23cb782173ab849
Author: Rob Herring <robh@kernel.org>
Date: Mon Sep 13 09:51:46 2021 -0500
kbuild: Enable DT schema checks for %.dtb targets
It is possible to build a single dtb, but not with DT schema validation
enabled. Enable the schema validation to run for %.dtb and %.dtbo
targets. Anyone building a dtb for a specific platform *should* pay
attention to schema warnings.
This could be supported with a separate %.dt.yaml target instead.
However, the .dt.yaml format is considered an intermediate format and
could possibly go away at some point if schema checking is integrated
into dtc. Also, the plan is to enable the schema checks by default once
platforms are free of warnings, and this is a move in that direction.
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Tom Rini <trini@konsulko.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org
Signed-off-by: Rob Herring <robh@kernel.org>
Acked-by: Masahiro Yamada <masahiroy@kernel.org>
Link: https://lore.kernel.org/r/20210913145146.766080-1-robh@kernel.org
(From OE-Core rev: 37fb1592eb8bcc4a8bbfc3f4b1dc6373733827f0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
DEPENDS here should match what 5.14 is using.
(From OE-Core rev: 899fd41723f41fe0a0cc24373c326b88cb385fe9)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The main reference kernel has moved to 5.14, so we bump -dev to
5.15 for the release.
(From OE-Core rev: 36e3ae14af7df8584063e5aac4fa32a57542c3a3)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is the result of automated script conversion:
scripts/contrib/convert-overrides.py <oe-core directory>
converting the metadata to use ":" as the override character instead of "_".
(From OE-Core rev: 42344347be29f0997cc2f7636d9603b1fe1875ae)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add features/scsi/scsi-debug.scc and features/gpio/mockup.scc to
KERNEL_FEATURES to meet ptest requirement as what we did for other
linux-yocto*.
(From OE-Core rev: fd27f302df886c27cb424191c27152ad9d0e8d80)
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The -dev kernel has moved to v5.12, as it will be the latest avialable
in the upcoming release. core-image-kernel-dev sanity has passed for
the supported arches.
So we bump the version to match the active branches.
(From OE-Core rev: 51401e0180f4f27ac9b6c8149332d4021d393d0d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We'll have the full v5.11 upstream kernel in linux-yocto-dev at
the time of release, so lets drop the -rc from the PV.
(From OE-Core rev: ee8f778252d1c741b45aca419867ef29d3398890)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Multiple files have " ," instead of ", " in expressions. This changes
them to conform to the way the rest of them are done.
Found and corrected via:
git ls-files | xargs sed --follow-symlinks -i 's/ ,d/, d/g'
(From OE-Core rev: 36c3afd2dd8bded02ea8f255e89a09ebd75c795b)
Signed-off-by: Jon Mason <jon.mason@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The dev branches have moved ahead, bump the version number to
match.
(From OE-Core rev: 544984925918f6f7fcadf78d44338898a2dda178)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the revision on linux-yocto-dev to reflect the updated state
of -dev.
The aufs/yaffs2 features are in place, but -rt is not yet available,
so the branches are placeholders for future updates.
This has been tested across all supported architectures and reference
qemu platforms, as well as with closely coupled userspace packages.
We tweak the LICENSE_CHECKSUM as well, since upstream has added an
informational note to the file, but the license is otherwise unchanged.
(From OE-Core rev: ca3d2db0e87168f3e1d6baa2e691ee0399db81d7)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This feature includes paravirtualized KVM guest support, including
KVMCLOCK for enhancing clock accuracy of guest OS. With it we can prevent
the following error.
"clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as
unstable because the skew is too large"
(From OE-Core rev: 74ffa7730e194e7b5dc71e63939b4a4a9843be93)
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The original BSP qemuarm has been renamed to qemuarmv5. Update the machine
overrides accordingly to avoid not generating dtb.
(From OE-Core rev: a1ac097686daf0769e7ff94ff2c8795e1e8ae790)
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the -dev kernel to 4.18 in preparation for the next
release kernel.
(From OE-Core rev: 3d7da5d8083b38a9b08fc187a41f8b6691f19091)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the -dev kernel to v4.17+. We also tweak the License checksum
in the -dev kernel since SPDX headers have been inserted upstream and
that has changed the hash value.
(From OE-Core rev: 851734af3ddf19c92e7c82c321adf9da988746b5)
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>
Outside of the normal patch refreshes and boot issues, there are new
build time tools within the kernel that required the following
dependencies:
For ORC_UNWINDER support in x86-64:
DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
And for certificate processing during the build, we need ssl headers
and hexdump:
DEPENDS += "openssl-native util-linux-native"
(From OE-Core rev: 70f3d81e414a101032c05773c33500e7d723ab02)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Having no opt-out method and adding the task to linux-yocto.inc was
causing issues. For example, linux-yocto-dev would often fail because
it uses AUTOREV with no way to dynamically change the PV.
Add a variable to turn off the sanity check, allowing an easy opt out,
and set the opt-out variable in linux-yocto-dev, fixing the issue with
AUTOREV.
(From OE-Core rev: 1b6a3c17874ead7ee0957e67329aa3bd019fa129)
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Other linux-yocto recipes have the virtio fragment added to qemu* targets.
If you plan on booting a kernel with qemu, we need these options .. or
things like the virtual disk won't be present.
(From OE-Core rev: 7e30a0db7b587a72a50d6d981ba8cf275ca61b23)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This check ensures that when the PREFERRED_PROVIDER for virtual/kernel
changes, the previous instances gets removed correctly so when the new
instance installs files into the shared area there is not an overlap of
old and new.
[YOCTO #10278]
(From OE-Core rev: 6b67018c2c0229a91fbc55c6aafb86781caf2499)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
4.7+ requires a device tree for the arm versatile family of platforms.
We add the definition to our 4.8 linux-yocto recipes so we can continue
to boot!
(From OE-Core rev: 8c5cf8193441814e46b7e118655b4e622f785ce5)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The use of the ${AUTOREV} variable means bitbake would always re-parse the
recipe. This isn't desirable when its disabled so undo the always parsing
flag in this case.
(From OE-Core rev: f1fce69766576ab62bfc5919af2af04028180950)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This recipe no longer functions after this change, revert it.
This reverts commit 3e0137113e.
(From OE-Core rev: 5e8cf6e568ab90365894478a272b5c28dc941031)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After commit 0437a59e3c, the linux-yocto-dev
recipe is being parsed every time we run "bitbake -p". This was spotted
on some performance benchmarks and showed up as a performance regression.
We can tweak the recipe to ensure this doesn't happen and that its only
used if selected.
(From OE-Core rev: 5c21fd5eb8b689504e7f6a4ee2f674c32e3d928b)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
