It is suspected that having this variable containing a local path is the
reason why when building from sstate, the kernel sometimes need to be
rebuild.
BugzID: 80858
Deploying directly the DEPLOY_DIR_IMAGE bypasses the shared state
mechanism implemented in the deploy class, leading to the image not
being properly deployed when building entirely from sstate.
BugzID: 80331
As for the kernel, we don't need to build them for every MACHINE and
will save some build time when building them only once per architecture.
BugzID: 80015
As explained in the comments, in yocto the kernel is expected to be
built for each MACHINE and not for each architecture as we do.
Therefor all tools related to kernel must also be adapted.
BugzID: 80015
These dependencies lead to a partial rebuild of the kernel when
switching machine, even where they are actually using the exact same
kernel sources and config.
BugzID: 80015
Instead of having one kernel recipe with two hashes, it makes more sense
and is easier to maintain two recipes with the same name but different
versions. The shared part is in an include file.
Each machine then chooses which version it wants to use with
PREFERRED_VERSION variable.
BugzID: 79987
With this change we are building the same kernel config for all
hardwares belonging to the same platform. The configs only differ from
one or two drivers which are enabled or not and they are anyway not
loaded as long as the devicetree is not matching.
But having only one config for several hardwares is reducing maintenance
(like enabling or disabling kernel security features) and also reducing
build time when building for different machines.
BugzID: 75223
The two "ifs" are covering cases where the fitImage is not used and we
don't support this case.
And as the Module.symvers comment says, this has been fixed upstream in
kernel.bbclass.
BugzID: 75220
These values are out of date with the real kernel versions and may be
misleading. Since we have only one version of the kernel, we can remove
them and "git" will be used as default value.
BugzID: 74959
These symlinks were required for compatibility with NRSW u-boot.
Since we are now using fitimage, the name of the devicetree is not
relevant since it is directly part of the fitimage.
BugzID: 74958
Instead of rewriting the full fitimage_assemble, we can just append to
the part generating the kernel entry, therefore reducing the duplicated
code.
BugzID: 74530
Because we don't have the kernel class in the netmodule-fitimage recipe,
we have to add this line there.
Signed-off-by: Lucien Mueller <lucien.mueller@netmodule.com>
This recipe lets us create a fitimage outside of the kernel recipe.
For this to work we need to create just the zImage from the standard
kernel recipe.
BugzID: 73616
Signed-off-by: Lucien Mueller <lucien.mueller@netmodule.com>
system-state-framework: added recipes for the broker, extmod and
sysstate parts.
move include files to ${STAGING_KERNEL_BUILDDIR}/include/broker/
Signed-off-by: Lucien Mueller <lucien.mueller@netmodule.com>
Co-authored-by: Ramon Moesching <ramon.moesching@netmodule.com>
Reviewed-on: https://git.netmodule.intranet/yoctoproject/meta-netmodule-bsp/pulls/70
This patch is removing wlan config to use the backports instead. But the
backports are not compatible with other kernel than virtual/kernel.
We must therefor rely in the default wlan for the moment
BugzID: 69147
Changing KERNEL_PACKAGE_NAME allows this variant of the kernel to live
its own life in tmp/work/ instead of being shared in tmp/work-shared.
It is also not providing virtual/kernel.
This way, the "official" kernel (virtual/kernel) is never modified and
rebuilt, leading to strange behavior regarding deployed licenses.
BugzID: 69147
Mr Jenkins
Alexandre Bard
Marc Mattmueller
Lucien Mueller
Stefan Eichenberger
Ramon Moesching