summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* j721s2 and j784s4: Correct serial console deviceRyan Eatmon2022-11-102-2/+2
| | | | | | | | | | | | | Serial console in J721S2/J784S4 EVM config was set to ttyS10. It should be ttyS2. This caused sysv based systems (eg, tiny) to apparently hang because of no login prompt. This didn't show up as a problem on systemd systems (eg, default) because systemd will automatically setup a serial tty with the console option passed in on the kernel command line (using console=...), which U-Boot correctly passes in as ttyS2 for J721S2/J784S4. Signed-off-by: Jonathan Humphreys <j-humphreys@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-driver: drop local patch as upstream is now fixedDenys Dmytriyenko2022-11-102-35/+0
| | | | | Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-*: Bump the graphics recipesRandolph Sapp2022-11-102-7/+3
| | | | | | | | | | | Bump the graphics recipes source revision and remove the old BVNC switch. The BVNC is now baked into the platform Makefile that is selected with PVR_BUILD_DIR / TARGET_PRODUCT. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* trusted-firmware-a: Update to latest upstream masterAndrew Davis2022-11-101-1/+1
| | | | | | | | | Notable changes include support for J784s4. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* machine: Add j784s4-evm configuration.Ryan Eatmon2022-11-109-6/+123
| | | | | | | | | | | | | | | Adding support for j784s4-evm: - Add configurations. - Add firmware. - Add u-boot. - Add gpu support. Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Hari Nagalla <hnagalla@ti.com> Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-driver: Fix git SRC_URIRyan Eatmon2022-11-101-1/+1
| | | | | | | | | We missed a spot when updating all of the git access for git.ti.com to use HTTPS. Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ipc: ti-rpmsg-char: Update library to 0.5.1Praneeth Bajjuri2022-11-101-3/+3
| | | | | | | | | | Update the ti-rpmsg-char library to 0.5.1 version that enables the support for R5F on am62x SoCs. Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-rtos-firmware: j721s2-hs-evm: add secure firmware imagesManorit Chawdhry2022-11-101-0/+49
| | | | | | | | | Adds support for secure firmware images in J721S2 HS EVM. Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-rtos-firmware: j7200-hs-evm: add secure firmware imagesManorit Chawdhry2022-11-101-0/+28
| | | | | | | | | Adds support for secure firmware images in J7200 HS EVM. Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-rtos-firmware: j721e-hs-evm: add secure firmware imagesManorit Chawdhry2022-11-101-1/+79
| | | | | | | | | Adds support for secure firmware images in J721E HS EVM. Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-mainline: unbreak devtoolDenys Dmytriyenko2022-11-101-3/+3
| | | | | | | | | | | | | | | | | | devtool has a long-standing bug where it cannot handle references to ${WORKDIR} due to externalsrc: https://bugzilla.yoctoproject.org/show_bug.cgi?id=12677 linux-ti-mainline clones additional ti-upstream-tools repo alongside the kernel sources into ${WORKDIR}, which exposes this devtool bug. Work around the issue by moving ti-upstream-tools inside the kernel source tree, i.e. inside ${S} Reported-by: Radoslav Pesek <radoslav.pesek@microstep-mis.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am64xx: Move multi-config targets into base SoC includeAndrew Davis2022-11-102-12/+13
| | | | | | | | | | | 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 <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am64xx-evm: Switch to SR2.0 HS-FS build by defaultAndrew Davis2022-11-107-19/+48
| | | | | | | | | | | | | | | 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 <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* cadence-mhdp-fw: Add dependency for j721s2Rahul T R2022-11-102-1/+2
| | | | | | | | | | cdns mhdp bridge is present in j721s2 soc. Add the dependency for the same Signed-off-by: Rahul T R <r-ravikumar@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: Use d.getVar() in DEPENDS expressionRandolph Sapp2022-11-101-1/+1
| | | | | | | | | | | | Switch the DEPENDS_append expression to use d.getVar() instead of the usual variable expansion to prevent the inline Python command from becoming mangled. Signed-off-by: Randolph Sapp <rs@ti.com> Acked-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee-os: Lower log level for AM62xAndrew Davis2022-11-101-1/+1
| | | | | | | | | | | | | | During resume from low power mode suspend OP-TEE prints some messages on the UART. It seems this UART is not powered at this point in the sequence breaking suspend/resume. We should track down the exact prints and quiet them. Until we get that fix upstream, lets lower the log level for this platform to unblock the LPM work. Signed-off-by: Andrew Davis <afd@ti.com> Acked-by: Anand Gadiyar <gadiyar@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee-os: Upgrade to upstream 3.18.0Andrew Davis2022-11-101-4/+2
| | | | | | | | | | Update to the latest upstream master which is 3.18.0. Signed-off-by: Andrew Davis <afd@ti.com> Reviewed-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* machine: add am62xx-lp-evm configurationAnand Gadiyar2022-11-105-3/+30
| | | | | | | | | | | | | | | 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 <gadiyar@ti.com> Cc: Hari Nagalla <hnagalla@ti.com> Cc: Andrew Davis <afd@ti.com> Cc: Praneeth Bajjuri <praneeth@ti.com> Cc: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am64xx-evm: Update default HS namesAndrew Davis2022-11-101-4/+0
| | | | | | | | | | | 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 <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* all: Stop using git://git.ti.comRyan Eatmon2022-11-1036-55/+55
| | | | | | | | | | | | Stop using un-encrypted git:// protocol to access TI repositories. This is inline with the same arguments as made by github in https://github.blog/2021-09-01-improving-git-protocol-security-github/ Signed-off-by: Nishanth Menon <nm@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am64xx-evm: Make HS-SE the defaultAndrew Davis2022-11-1010-53/+33
| | | | | | | | | | | | 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 <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti-staging: Update to the latest ti-u-boot-2021.01Andrew Davis2022-11-104-4/+8
| | | | | | | | | | | | | | 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 <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: Use ti-k3-secdev if TI_SECURE_DEV_PKG_K3 is not definedAndrew Davis2022-11-101-1/+3
| | | | | | | Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* recipies-ti: Add TI K3 Security Development PackageAndrew Davis2022-11-102-0/+38
| | | | | | | Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* trusted-firmware-a: upgrade to v2.7Praneeth Bajjuri2022-11-101-2/+2
| | | | | | | | | | upgrade arm-trusted-firmare to v2.7 Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Tested-by: Judith Mendez <jm@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: Add am65xx-evm-k3r5-sr2 to combined R5 boot listAndrew Davis2022-11-101-0/+2
| | | | | | | | | | | This machine was missed when making combined R5 boot the default. Add this machine to fix build failure. Reported-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* k3: also inherit kernel-fitimage class for FIT image generationDenys Dmytriyenko2022-11-101-0/+1
| | | | | | | In order to support fitImage image type, kernel-fitimage class is needed. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: k3: Add fitImage to the default kernel image typesAndrew Davis2022-11-101-1/+1
| | | | | | | | | | | 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 <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am64xx-hs-evm: Add extra machine to build GP SYSFWAndrew Davis2022-11-103-0/+25
| | | | | | | | | | | | | 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 <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: Only deploy the raw SYSFW images for one machine targetAndrew Davis2022-11-101-2/+2
| | | | | | | | | | | | This recipe deploys the raw SYSFW unconditionally which causes issues when doing multiconfig builds. What should happen is only one deploys these, select that the same way we select which one deploys the default SYSFW symlink. Move the deploy step there. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Move K3 TI_SECURE_DEV_PKG definition to common includeAndrew Davis2022-11-1012-20/+4
| | | | | | | | | | | 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 <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: Only install and deploy combined boot symlink when setAndrew Davis2022-11-101-2/+7
| | | | | | | | | | | Add SYSFW_TIBOOT3_SYMLINK and use it the same way we use SYSFW_SYMLINK for the non-combined boot flow, to allow not setting the default for some machine types. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: Make combined R5 boot the defaultAndrew Davis2022-11-102-16/+15
| | | | | | | | | | | | | | 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 <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: Use SYSFW_TIBOOT3 to point to the SYSFW imageAndrew Davis2022-11-101-8/+8
| | | | | | | | | | | | Currently we reuse UBOOT_* names which usually are the same we want to give to the name of the SYSFW binary. This isn't always correct, we should use a SYSFW specific variable in case the UBOOT names are changed. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: Deploy all SYSFW firmware typesAndrew Davis2022-11-101-16/+12
| | | | | | | | | | This allows us to rebuild and re-sign the SYSFW image if needed from the deploy directory for any SoC type. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: Use new SOC_TYPE and SYSFW_DIR to simplify recipeAndrew Davis2022-11-102-121/+28
| | | | | | | | | | | | | | | | | | | The k3-image-gen now has two new helper flags SOC_TYPE and SYSFW_DIR that we can use to simplify this recipe. With these we do not need to do anything different here for HS builds, the SOC_TYPE selects this now. DL_URL also do not need cleared anymore, the k3-image-gen will no longer download missing files when not needed for the current build type. do_install and do_deploy can also check for the existence of either sysfw.itb or tiboot3.bin and install/deploy as needed. k3-image-gen only gerneates the right one now depending on the SoC. Merge all these steps for all SoCs. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* machine: k3r5: Make combined R5 boot the defaultAndrew Davis2022-11-106-48/+33
| | | | | | | | | | | | | Going forward, the combined tiboot3.bin is going to be the standard. Only AM65x and J721e will still use the split boot. Set the output of U-Boot to be u-boot-spl.bin by default 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 <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-next: add recipe for building linux-nextDenys Dmytriyenko2022-10-241-0/+43
| | | | | | | | | | | | | Required for daily test plans. Can be enabled in local.conf or <distro>.conf: PREFERRED_PROVIDER_virtual/kernel = "linux-ti-next" SRCREV:pn-linux-ti-next = "${AUTOREV}" Only uses in-tree defconfigs, does not support config fragments, builds and packages in-tree DTBs. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti-mainline: update to the latest 2022.10Denys Dmytriyenko2022-10-241-3/+3
| | | | | | | | Update to the latest release version. bzip2 license was added to the list, update checksum. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot: drop 2020.01Denys Dmytriyenko2022-10-241-7/+0
| | | | | | | Deprecated in favor of 2021.01 Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux: drop 5.4 kernelDenys Dmytriyenko2022-10-2420-75/+0
| | | | | | | Deprecated in favor of 5.10 Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* layers: Add langdale to LAYERSERIES_COMPATKhem Raj2022-10-122-2/+2
| | | | | Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* prueth-fw: Deploy for AM64xx based on SoC not EVMAndrew Davis2022-09-222-2/+2
| | | | | | | | | | This makes sense but looks like was done wrong to match AM65xx which needed the exact EVM specified due to this only working on SR2. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* trusted-firmware-a: Allow build to continue without TI_SECURE_DEV_PKG setAndrew Davis2022-09-221-22/+16
| | | | | | | Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee-os: Allow build to continue without TI_SECURE_DEV_PKG setAndrew Davis2022-09-221-1/+6
| | | | | | | Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti: Do not prepend output files with DEPLOYDIRAndrew Davis2022-09-221-18/+18
| | | | | | | | | | We already cd into DEPLOYDIR so this is not needed. This now matches the keystone version below. Also fixes build in some odd situations. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Make multi-certificate image the defaultAndrew Davis2022-09-228-18/+8
| | | | | | | | | | | | 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 <afd@ti.com> Reviewed-by: lines be preserved? Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-linux-fw: Bump to 08.04.01.001 releaseRyan Eatmon2022-09-221-1/+1
| | | | | | | | Updated the ti-linux-fw version for 08.04.01.001 Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging-rt: Bump to 08.04.01.001 releaseRyan Eatmon2022-09-221-1/+1
| | | | | | | | Updated the linux rt version for 08.04.01.001 Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging: Bump to 08.04.01.001 releaseRyan Eatmon2022-09-221-1/+1
| | | | | | | | Updated the linux version for 08.04.01.001 Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-09 23:26:11 +0000