* rework machine conf to only build necessary stuff
* in *.wks file switch from ondisk to use-uuid the solves an issue that during
boot the user data partition could not be mounted because user data was set
to mmcblk1 in fstab but actually was sda
* kenrel options were missing for dmcrypt to create secure storage. those are
now added to all machines using linux-yocto source and use the
meta-belden-coreos-bsp layer
Merge in ICO/coreos from refactor_marvell_trusted_firmware_a to master
* commit 'c7c3793c9e732c568202262c189014b5b8468320':
refactor(trusted-firmware-a): update patches and cleanup
The certificates and keys are stored in a repository and taken from there.
It is a neative repository that puts the keys into the sysroot where other
recipes can take them
All the key related scripts where deleted or put in the development-keys
repository.
Basic simplifications where done, there is yet still room for improvement.
The secure-storage feature provides a encrypted filesystem to securely store
data in rest. It will be auto-mounted under /usr/local/data/secure-storage.
The loopbackfile will be stored under /usr/local/data/loopdevices.
The keyfile is located under /usr/local/data/.crypto.
The userdata partition is mounted under /usr/local/data. It is and will stay
read-write and its purpose is to store userdata like config, secure-storage.
* all creation dates of the files are set to the 01.01. of the current year
* the file /usr/lib/clock-epoch is created. It is used by timedatectl to
get the initial time and date (creation time of file).
* a sanity check was added to check if the hardcoded timestamp is outdated
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
Patrick Vogelaar
Holger Dihlmann
Dimitry Shapovalov
Samuel Dolt
Uli Stein