linux/meta-ti.git/conf/machine/include/k3.inc, branch 08.04.01.005

conf: machine: k3: Add fitImage to the default kernel image types

2022-08-09T01:07:47+00:00

FIT Image based kernels are valid for all K3 devices, not just HS, deploy this kernel image type by default so it doesn't have to be appended on a per-device-type basis. Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon

conf: machine: Move K3 TI_SECURE_DEV_PKG definition to common include

2022-08-07T00:04:37+00:00

The K3 TI_SECURE_DEV_PKG is the same for all devices, move this out of each machine file and into the common K3 includes. This doesn't have any effect on the GP machines as they make no use of it. Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon

conf: machine: Make multi-certificate image the default

2022-08-05T13:29:17+00:00

Only the first two K3 devices do not support multi-cert boot so lets make multi-cert the default and only add back sysfw.itb for these two devices. Signed-off-by: Andrew Davis Reviewed-by: lines be preserved? Signed-off-by: Ryan Eatmon

conf: machine: wic: Fix HS image boot partition

2022-06-23T14:22:05+00:00

IMAGE_BOOT_FILES was being overwritten in the HS recipes leading to incomplete binaries in /boot and the naming of the binaries were not correct. Fixes /boot partition for HS devices. Signed-off-by: Manorit Chawdhry [afd: Extended fix to all HS platforms] Signed-off-by: Andrew Davis Acked-by: Manorit Chawdhry Signed-off-by: Ryan Eatmon

wic: revert grub-efi patch

2021-11-19T02:27:48+00:00

Revert "conf/machine: k3: Enable grub-efi by default in wic images" This reverts commit d0b09833b44fa23cce86fd99dd8ca6631c61c476.

conf/machine: k3: Enable grub-efi by default in wic images

2021-08-09T15:39:11+00:00

All of our platforms here support running EFI binaries. We can have wic generate a simple grub.cfg file for us that will find the root partition via PARTUUID and utilize the device tree that is already discoverable via the EFI configuration tables. Assuming the EFI loader is U-Boot, this device tree can be replaced at run-time by the normal mechanism of loading in to memory and passing that address as an argument to bootefi. Signed-off-by: Tom Rini Reviewed-by: Denys Dmytriyenko Signed-off-by: Yogesh Siraswar

conf/machine: k3: Lets build bmap files by default

2021-04-01T02:45:25+00:00

Lets generate bmap files for bmaptool to use as well as default to use with wic files. NOTE: bmaptool can speed up flashing SD cards by 2x-3x by skipping empty blocks of the image. https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#flashing-images-using-bmaptool Signed-off-by: Nishanth Menon Reviewed-by: Denys Dmytriyenko

conf/machine: k3: Add multi-certificate boot image support

2021-04-01T02:42:59+00:00

Lets keep things consistent by providing two possibilities for platforms to pick from - legacy boot and multi-certificate boot. In legacy boot, the base bootloader and system firmware are maintained as separate binaries (tiboot3.bin and sysfw.itb). In multi-certificate boot that newer K3 devices support, ROM is smarter and can handle multiple x509 certificate based images: so we can strip out the sysfw.itb and integrate it as part of tiboot3.bin itself. This improves authentication and overall system boot times since we are now able to boot both the system controller and the boot processor in parallel. We do have a scheme currently to identify the images necessary for boot etc, but things are handled on a platform conf file basis. We can improve that by introducing the pattern at the top level include and use the relevant pattern in platforms as needed. Signed-off-by: Nishanth Menon Reviewed-by: Denys Dmytriyenko

conf/machine: clean up MACHINE_FEATURES for k3/j7/am65 families

2020-08-06T20:55:36+00:00

Signed-off-by: Denys Dmytriyenko

trusted-firmware-a: upstreamed and unified to meta-arm, drop locally

2020-05-19T20:30:29+00:00

Signed-off-by: Denys Dmytriyenko