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
* compatible node in device tree is adjusted
* config for cn9131 Falcon is removed since it is based on cn9130
* config for cn9130 based Falcon is added
commit 367814e94c introduced a change in the default
configuration of swupdate that broke our default update
system.
This commit revert this part of the emmc flasher support
for now
Merge in ICO/coreos from feat/package-group to master
* commit '5bddcaad7adf75ec63c18f72d8455204edf39cf4':
feat(coreos-container-image.bbclass): use coreos specific package-group for IMAGE_INSTALL
feat(coreos-image.bbclass): use coreos specific package-group for IMAGE_INSTALL
Merge in ICO/coreos from feat/devtool-kernel to master
* commit '1c8f7e9163ba5fec161bb858643a57274ea07882':
feat(devtool): add a generate-uki command
fix(coreos-image-uki.bbclass): use APPENDS to set the kernel arguments
refactor: use black to format python code in vscode
The generate-uki command can be used to build and sign new UKI (Unified
Kernel Image). By default all parameters are taken from bitbake but the
kernel command line and the device tree used can be customized
This introduce a new coreos-emmc-flasher-beaglebone
recipe that create a SWU file that can be used to
create the partition in the internal emmc of a beaglebone
and flash both u-boot and efibootguard.
Support for create efibootguard configuration partition
and flashing kernel and rootfs is not included.
Samuel Dolt
Patrick Vogelaar
Dimitry Shapovalov
Darko Trogrlic