The routine calculating the -native depdenency for configuration
fragments had issues with variations in kernel PV definitions.
To avoid making the routine even more complex, this commit switches
to using the same variables that include the correct virtualization
include file. This way, if bitbake has located and included the
file that adds the -native dependency, we know that the variables
will find the correct recipe.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
* it was introduced in:
https://git.yoctoproject.org/meta-virtualization/commit/?id=a940a0e873f9163d4585555b3f3d38e99400d237
but it doesn't work well when PREFERRED_VERSION is set to e.g. "6.6.%",
you remove the '%' but not the trailing dot, causing:
ERROR: Nothing PROVIDES 'yocto-cfg-fragments-6.6.-native'. Close matches:
yocto-cfg-fragments-6.10-native
yocto-cfg-fragments-6.6
yocto-cfg-fragments-6.6-native
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
When more than one kernel is supported in oe-core, we may have
situations where the options from an older (or newer) kernel
are not appropriate for the other version (i.e. options have
been added, removed or renamed).
To support this we check the preferred version of the kernel
and depend on a specific yocto-cfg recipe.
This is similar to how the virtualization .inc files are
chosen.
If this technique proves to be correct, we can factor the
common routines into a .inc and just set SRCREVs in the
individual .bb files.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
kernel version 6.10 will be the next reference kernel, so we
add the .inc file to enable the configuration
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Now that UNPACKDIR is used to unpack sources we have an
extra level of indirection to locate our cloned fragments.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
distro optional features need to ensure that they are space
separated or we'll have configuration failures.
Additionally, always add a local configuration fragment for
easy debug and enablement of options.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
We've had duplicate fragments in the kernel-cache and the meta-virt
layer for quite some time (i.e. docker).
To more easily keep these in sync, promote the sharing of fragments
and to allow them to be used even when meta-virt isn't part of
a build, we change our feature additions to use the yocto-kernel-cfg
clone of the kernel-cache instead of the ones in our layer.
It remains to be seen if any other kernel recipes will run into
issues with this movement of the fragments, so we mark this as a
WIP/RFC.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Currently Xen expected a tun module to be packaged. We need
a better way to resolve dependencies such as this (perhaps
by the kernel providing the package requested when functionality
is built in).
But for now, without a compelling need for criu to have tun
built in, we tweak this config to match and keep the xen builds
happy and with no conditional package requirements.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
criu needs to turn on sock diag features in kernel to do the system dump[1].
Ref:
[1] https://criu.org/Linux_kernel
Signed-off-by: Xiangyu Chen <xiangyu.chen@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Adding support for the 6.6 kernel series as testing has been
completed against linux-yocto v6.6/*
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Allow the kernel include file to be skipped, even if a
kernel is capable of merging and using the fragments in
the layer and kernel-cache.
Setting SKIP_META_VIRT_KERNEL_INCLUDE="t" in a kernel
bbappend, or in a configuration file will inhibit the
generated / detected include file.
BUT
If that opt-out is done, we warn, as the user has
explicitly disabled safeguards that help ensure that
subtle runtime issues aren't introduced.
BUT
If someone really knows what they are doing, they
don't want the warning to be present in each build.
So setting META_VIRT_KERNEL_CHECK_WARNING_INHIBIT="t"
will inhibit the message.
At that point, you have jumped through all the hoops
and you are free to ensure your kernel configuration
is correct using other means.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
The 6.5 kernel has now been tested against core and meta-virtualization
so we add the .inc file to show that status.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
bitbake has been enhanced such that SRCPV is no longer needed in
PV to handle updating git hashes and task signatures.
We can simplify our PV by dropping SRCPV
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
5.15 hasn't been in master for quite some time, so we drop
our version matching .inc
Support for 5.15 can be found on release branches.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
oe-core commit 123077ecd9f3c1839d [python3-dtc: add from
meta-virtualization] brings this recipe into core, so we drop
our version.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
While the insane.bbclass upstream-status check hasn't been made
default, users of meta-virtualization may have it enabled in their
distros .. so the effect is the same. We must have this tracking
tag in out patches.
This is a bulk update to add the tag and silence the QA message.
As packages get updated, the normal/routine process of checking
the patches will continue, and the status fields may (or may not)
get more useful.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
The more generic linux-%.bbappend will match on linux-yocto-dev.
If we have the version specific .inc files in the layer, then we
will have support for linux-yocto-dev. Since we already track
the linux-yocto-tested versions, it isn't hard to track the -dev
kernel version.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
The major stacks have been tested against 5.19, so we add the
tracking .inc to indicate support.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
K3s (and Kubernetes) supports load balancing via IPVS, and by default reports
errors when IPVS kernel modules cannot be loaded.
This patch adds the missing reported kernel modules to the k3s recipe:
* ip-vs
* ip-vs-rr
* ip-vs-wrr
* ip-vs-sh
The modules are configured by including the ip_vs kernel feature.
Signed-off-by: Richard Neill <richard.neill@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Bumping lopper to latest, which comprises the following commits:
c7b22ce lopper/subsystem: update access to latest specification
716fe89 lopper/init: pass permissive to dt_compile if specified on the command line
2575d66 dt_compile: allow duplicate label errors to be skipped with --permissive
22b2515 lopper: drop duplicate labels due to node merging
f70eb86 lopper: bump version to 1.0.2
9b72de5 lopper: only execute main() when __main__ is called directly
b0b19a1 lopper: improve label round trip handling
d4b7706 docs: clarify lop versioning an compatible strings
e44204b README: add phandle-desc-v1 description
17350a7 version: bump to 1.0.1
0a4fcac tree: fix tree export and reload
520dea8 lopper/base: add secure-address-map description
6e660c5 lopper/lops: resolve tree when copying
8d46634 lopper: allow select to match labels
7aac1e3 openamp: add stub for OpenAMP Domain processing landing function
82986bb lopper: add the ability to extend phandle meta-data table
914c7e2 yaml: add alias/anchor based node naming
d9f1abb spec: update remoteproc example per latest spec
40cc05d lop-load: add back CDO
d5d23ab xlnx: subsystem: rename lopper_tree to lopper.tree in imports
7d23ba6 lop-load: update for latest master
4caa022 openamp: add stubs for picking up domain to domain YAML property
d8dae9d openamp_xlnx: rename fily openamp_xlnx.py to allow includes from this file
0358879 yaml-xlate: add stub for domain-to-domain property
903b16a spec: remove resource-groups
1dd1e67 README: update to add mailing list information
5da82a1 lopper/yaml: add lopper processing for "<<+" extension marker
3d05302 assists: domain_access: Fix update_mem_node handling for higher address
3c81fcc fdt: handle large integers
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
There is a bug in SWIG/setuptools where 'pip install' doesn't build
libfdt.py unless the build tree is already dirty, which makes using
the library impossible.
Bump the SRCREV to incorporate the upstream workaround for this issue.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
The wheel that is built is:
lopper-1.0-py3-none-any.whl
Set BASEVERSION to 1.0 and use this to set PV and the value for PYPA_WHEEL
(the path to the wheel filename).
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
The wheel that is built is ${S}/dist/libfdt-1.6.2.dev39+g4048aed.d20220103-cp310-cp310-linux_x86_64.whl
Set PYPA_WHEEL to match this.
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
These changes are the result of running the convert-spdx-licenses.py
oe-core script.
There's no impact to the build, but we will avoid issues when
interacting with core QA by the alignment.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
We need some of the latest dtc functionality for lopper, but that
puts us out of sync with the main dtc recipe in oe-core master.
To show that we are running ahead, bumping the PV to include SRCPV.
To fix the following missing symbol:
| ImportError: qemuarm64-poky-linux/xen-image-minimal/1.0-r0/recipe-sysroot-native/usr/lib/python3.10/site-packages/_libfdt.cpython-310-x86_64-linux-gnu.so: undefined symbol: fdt_overlay_target_offset
We revert the commit that introduces it (since we don't need that
functionality), and will drop our revert when oe-core updates to
a similar version.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
As part of this update:
- we drop our backported patches
- simplify the recipe to use setuptools-scm
- remove the need to generate version_gen.h
- adapt to setup.py at ${S}
- and include following commits:
4048aed setup.py: fix out of tree build
ff5afb9 Handle integer overflow in check_property_phandle_args()
ca72944 README: Explain how to add a new API function
c0c2e11 Fix a UB when fdt_get_string return null
cd5f69c tests: setprop_inplace: use xstrdup instead of unchecked strdup
a04f690 pylibfdt: add Property.as_*int*_array()
8310271 pylibfdt: add Property.as_stringlist()
d152126 Fix Python crash on getprop deallocation
17739b7 Support 'r' format for printing raw bytes with fdtget
45f3d1a libfdt: overlay: make overlay_get_target() public
c19a4ba libfdt: fix an incorrect integer promotion
1cc41b1 pylibfdt: Add packaging metadata
db72398 README: Update pylibfdt install instructions
383e148 pylibfdt: fix with Python 3.10
23b56cb pylibfdt: Move setup.py to the top level
69a7607 pylibfdt: Split setup.py author name and email
0b106a7 pylibfdt: Use setuptools_scm for the version
c691776 pylibfdt: Use setuptools instead of distutils
5216f3f libfdt: Add static lib to meson build
4eda259 CI: Cirrus: bump used FreeBSD from 12.1 to 13.0
0a3a9d3 checks: Add an interrupt-map check
8fd2474 checks: Ensure '#interrupt-cells' only exists in interrupt providers
d8d1a9a checks: Drop interrupt provider '#address-cells' check
52a16fd checks: Make interrupt_provider check dependent on interrupts_extended_is_cell
37fd700 treesource: Maintain phandle label/path on output
e33ce1d flattree: Use '\n', not ';' to separate asm pseudo-ops
d24cc18 asm: Use assembler macros instead of cpp macros
ff3a30c asm: Use .asciz and .ascii instead of .string
5eb5927 fdtdump: fix -Werror=int-to-pointer-cast
0869f82 libfdt: Add ALIGNMENT error string
69595a1 checks: Fix bus-range check
72d09e2 Makefile: add -Wsign-compare to warning options
b587787 checks: Fix signedness comparisons warnings
69bed6c dtc: Wrap phandle validity check
9102211 fdtget: Fix signedness comparisons warnings
d966f08 tests: Fix signedness comparisons warnings
ecfb438 dtc: Fix signedness comparisons warnings: pointer diff
5bec74a dtc: Fix signedness comparisons warnings: reservednum
24e7f51 fdtdump: Fix signedness comparisons warnings
b6910be Bump version to v1.6.1
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Inheriting setuptools3-base doesn't actually define any tasks, so commit
1ef6050 to drop distutils3 had the side-effect of not building any code.
Backport a commit from upstream to switch to setuptools, inherit
setuptool3, and change DISTUTILS_SETUP_PATH to SETUPTOOLS_SETUP_PATH.
Signed-off-by: Ross Burton <ross.burton@arm.com>
The removal of the .inc was pushed prematurely. We'll remove it
again, once 5.14 is removed from core and 5.15 is the default.
This reverts commit 79e0e4598c.
5.14 has been removed from core, and is EOL upstream. We drop our 5.15
.inc file to match that status.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Switching to lopper 1.0 brings us a more standard setuptools
based project for install and packaging.
This update also fixes the experimental update to master-next,
which was incomplete and broken.
The only signficant user visible change with this update is
that lopper.py is now 'lopper' and any calling recipes need
to be updated accordingly.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Adds the following kernel modules for k3s:
* xt-physdev
* xt-nflog
* xt-limit
* nfnetlink-log
Without them, the k3s network-policy-controller reports failures in the log
related to iptables-restore.
Signed-off-by: Richard Neill <richard.neill@arm.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
