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

conf: machine: am64xx: Move multi-config targets into base SoC include

2022-09-08T12:35:17+00:00

The supported device types depends on the SoC, not on any specific board or EVM. Any board can be populated with any of the 3 supported AM64x types. Move these into the AM64x common include. Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon

conf: machine: am64xx-evm: Switch to SR2.0 HS-FS build by default

2022-09-08T12:35:17+00:00

AM64x devices will only be available as SR2.0 HS-FS. Set this as the default type provided by the SDK. To allow SR2.0 HS-SE to continue to boot, like we did with GP, we add an extra machine to build SR2.0 HS-SE SYSFW. To use on SR2.0 HS-SE boards simply switch out the SYSFW image: $ cd /mnt/sd-card/boot $ mv tiboot3-am64x_sr2-hs-evm.bin tiboot3.bin Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon

machine: add am62xx-lp-evm configuration

2022-08-29T17:15:03+00:00

This platform is similar to the currently supported am62xx-evm, except that we currently need new defconfigs for u-boot and new dtbs in the filesystem. Signed-off-by: Anand Gadiyar Cc: Hari Nagalla Cc: Andrew Davis Cc: Praneeth Bajjuri Cc: Ryan Eatmon Signed-off-by: Ryan Eatmon

conf: machine: am64xx-evm: Update default HS names

2022-08-28T22:37:36+00:00

In the latest U-Boot the HS images for AM64x have been renamed to the default names, and the GP have been changed to *_unsigned. Remove the overrides to pull the now default HS images. Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon

conf: machine: am64xx-evm: Make HS-SE the default

2022-08-26T19:33:15+00:00

The HS-SE AM64xx machine can now be run on GP devices and built without needing the TI_SECURE_DEV_PKG for the same. AM64xx will only be available in the HS-FS type going forward. Make the HS-SE the default and remove the original GP machine. Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon

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: am64xx-hs-evm: Add extra machine to build GP SYSFW

2022-08-07T00:07:44+00:00

Use multiconfig to generate a GP SYSFW image. This allows the HS SDK to be used on GP boards by simply switching out the SYSFW image: $ cd /mnt/sd-card/boot $ mv tiboot3-am64x-gp-evm.bin tiboot3.bin Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon

u-boot-ti-staging: Update to the latest ti-u-boot-2021.01

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

Update to the latest commit of ti-u-boot-2021.01. As part of this U-Boot update the non-HS AM64x-evm defconfig was removed. This is okay as building this defconfig without defining TI_SECURE_DEV_PKG will still result in usable binaries for the non-HS devices. Use the HS defconfig for both the HS and non-HS machines. 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

ti-sci-fw: Make combined R5 boot the default

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

Going forward, the combined tiboot3.bin is going to be the standard. Only AM65x and J721e will still use the split boot. Set DEPENDS and EXTRA_OEMAKE for combined boot and override only for the two split boot platforms. This makes it easier to add new platforms and simplifies deployment logic. Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon