When introducing CN913x devices by using the meta-belden-marvell-bsp layer
trusted-firmwarre-a recipe was copied from meta-arm and modified. Now the
original recipe is used from meta-arm and the changes were put into a
bbappend.
Also trusted-firmware-a version changed from 2.3 to 2.6.
The defaul qemu devices have not set efi as MACHINE_CONFIG which causes
the CoreOS build to fail because efi is required.
This change disables CoreOS sepcific features like swupdate for all
qemu MACHINES.
Merge in ICO/coreos from feature/up/integration/meta-netmodule-wlan to master
* commit 'ecc4ca19f415616e101b65aca3e4bf137b5ae34c':
refactor(0001-refactor-cn913x-defconfig-cleanup.patch): patch refactored. defconfig is properly generated using savedefconfig yocto task
feat(0001-refactor-cn913x-defconfig-cleanup.patch_and_cn913x_additions.cfg): remove mac80211, cfg80211 and qrtr from standard Linux kernel config. Use the counterparts from meta-netmodule-wlan layer.
Merge in ICO/coreos from rename_eagle40_03 to master
* commit '3bf28622c1b2207e752b6e0b9725b4d27fa328a0':
refactor(eagle40-03): rename MACHINE from eagle40_03 to eagle40-03
Merge in ICO/coreos from add_variable_for_kernel_in_wks_file to master
* commit 'afa1a784c1637ad2965f93061794f10577e992a2':
refactor(partitions.inc): use variable for kernel in wks file
the changed image is
layers/meta-belden-coreos-demo/recipes-core/image/cores-image-demo-k3s
k3s is a orchestration tool and a slimed down version of kubernetes
k3s agent is a tool to control pods
the commands come a k3s server in a cluster
Now the distro settings is splitted into two config smaller config
file. PACKAGECONFIG for the system package is set to include a
reduced set of features by default.
Some EFI related feature are now dependant of the EFI DISTRO_
and MACHINE_FEATURES.
Now a single unified kernel image is built using a new CoreOS
specific functionality added in the efibootguard UKI stub to
automatically insert root=PARTLABEL=rootfs0 (or rootfs1) in the
kernel command line
BREAKING CHANGE: coreos-image-uki.bbclass now only generate a
single kernel image named kernel-${MACHINE}.efi
Merge in ICO/coreos from fix_pci_issue_on_cf_pro_eval_board to master
* commit '1d8551459f909b00e0156959a40ac3cbc9773ef5':
fix(u-boot): revert to u-boot 2019.10 because of several issues with 2023.04
Merge in ICO/coreos from feat/extlayers to master
* commit '0d5beff86fd830f8b3eec81afdf51f94132530b6':
feat(layers): move third party layers to external-layers
* the swupdate version has been updated and therefore caused a regression
because the bbappend didn't match anymore.
* changed the bbappend to match any swupdate version.
BREAKING CHANGE: bblayers.conf / bblayers.conf.sample of project
using CoreOS should be adapted to use external-layers instead
of layers for each moved layers
Reason was that the actual firmware was just added to the coreos-image-all-feature.
* use MACHINE_ESSENTIALS_EXTRA_RDEPENDS instead of IMAGE_INSTALL and move to machine config
* refined linux-firmware recipe to just have microchip on its own.
Merge in ICO/coreos from fix_falcon_phy_firmware to master
* commit 'e003ccb91319299b73eaf8029288e3fde55fc71f':
fix(cn9131-bldn-mbv): add phy firmware handling
Merge in ICO/coreos from fix_falcon_machine_name to master
* commit 'e04b6cf215a61288f058970e4ca6031acea8f4a2':
fix(cn913x-bldn-mbv): fix machine and phy
* change the MACHINE from cn9130-bldn-mbv to cn9131-bldn-mbv
* update trusted platform to support falcon board and represnt the solidrun settings
* add patch that fixes phy issues
Now we use fw0, fw1, efi, ebg0, ebg1, rootfs0 and rootfs1 partition
name.
BREAKING CHANGE: bootX partition are now named ebgX
BREAKING CHANGE: platformX partition are now named rootfsX
sw-description files
The COREOS_SWUPDATE_EXTENDS_FOR and COREOS_IMAGE_SWUPDATE_EXTRACLASSES
variable can now be used to configure the coreos-image-swupdate to
dynamically extends some part of the sw-description by calling some
python function
This also change the beaglebone target to use a GPT
partitioned disk
BREAKING CHANGE: .swu image generated can not be used on old
device, thus the device has to be reflashed.
BREAKING CHANGE: Support for MBR formatted disk is removed, as
it was only used for Beaglebone
COREOS_EFI_SECUREBOOT_KEYDIR_HASH was intended to store a hash
of each file present in build/key in order to discard the sstate
cache on key changes. But this variables was wrongly always empty
due to a wrong check in a loop.
Merge in ICO/coreos from fix/devtool_efibootguard_script to master
* commit 'c003449178fdb31ca8f39c15516129774591944a':
fix(coreos-efibootguard.py): fix the script for older python version
Patrick Vogelaar
Holger Dihlmann
Dimitry Shapovalov
Samuel Dolt
Uli Stein