summaryrefslogtreecommitdiffstats
path: root/meta-ti-bsp/conf
Commit message (Collapse)AuthorAgeFilesLines
* conf: machine: am62xx-lp-evm.conf: Pick LPM wkup sources overlayPraneeth Bajjuri2023-11-291-1/+1
| | | | | | | | | | | | | | | commit [1] created a common LPM wkup sources overlay and removes k3-am62x-sk-mcu-gpio-wakeup.dtso for am62 device family. k3-am62x-sk prefix picks this overlay for am62xx, am62axx and am62xxsip already. This patch picks the necessary overlay for am62xx-lp-evm since it doesnt use the same prefix as other am62 platforms. [1]: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?&id=4ba1886b886d Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Reviewed-by: Judith Mendez <jm@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-extras: Add support for extra kernel/u-boot features for am62pxxParesh Bhagat2023-11-242-0/+2
| | | | | | | | | | | | Add support for ti-extras for am62pxx to control the kernel and u-boot repos, branches, and srcrevs via the TI_EXTRAS variable in the local.conf file. Also add am62pxx as compatble machine in jailhouse recipe. So the am62pxx jailhouse build can be done by adding TI_EXTRAS=tie-jailhouse in local.conf. Signed-off-by: Paresh Bhagat <p-bhagat@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* k3r5: ensure separate TMPDIR used for this multiconfigDenys Dmytriyenko2023-11-221-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This k3r5 multiconfig builds baremetal components (and corresponding native, nativesdk and cross tools) and sets TCLIBC accordingly to "baremetal". The expectation is that those components and tools will use a separate TMPDIR to isolate from the main Linux build that uses "glibc" TCLIBC and to avoid potential conflicts. OE-Core "nodistro" default configuration already sets TCLIBCAPPEND facility to automatically add a suffix to TMPDIR, resulting in "tmp-baremetal" temp directory for this multiconfig and "tmp-glibc" for the main Linux one. Other distros like Arago follow this convention and even extend a bit (e.g. Arago also adds TCMODE suffix to TMPDIR for external toolchain support separation). But Poky (and derivative distros, like AGL or YoE) disable TCLIBCAPPEND and result in a combined TMPDIR, leading to potential conflicts, such as: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15273 And that's just the beginning, there were other conflicts observed later in the build, e.g. during nativesdk builds - that's why we also set a unique SDKPKGSUFFIX here. To force a separate TMPDIR for k3r5 multiconfig, we have to directly append a suffix to it. Multiple other options were tested in hopes of making it slightly cleaner, but they either didn't work or were dismissed. For example, trying to override TCLIBCAPPEND getting cleared by a distro would require using a machine/soc-override, which doesn't have enough scope (nativesdk) or forcing it with :forcevariable would also change the main Linux TMPDIR and affect existing CI flows. Also, using TCLIBC itself as a suffix to add to TMPDIR may result in getting it appended twice (tmp-baremetal-baremetal) when normal TCLIBCAPPEND facility is used. Hence the least invasive/confusing option is to always append "-k3r5" suffix to this multiconfig TMPDIR. That results in "tmp-k3r5" in Poky (leaving main TMPDIR as "tmp"), while OE-Core "nodistro" and Arago would end up with "tmp-baremetal-k3r5" (and "tmp-glibc" for the main). Also note, meta-ti-bsp layer.conf sets up images and sdks to be deployed into a common location outside of TMPDIRs, but TI_COMMON_DEPLOY variable that controls it is set weakly, allowing to be modified from a distro configuration or local.conf. It means that all images and sdks can be deployed into the main TMPDIR if one's CI flow expects tmp/deploy/ as the final destination, by using := for immediate variable expansion: TI_COMMON_DEPLOY := "${TMPDIR}/deploy" Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62xx-lp-evm.conf: Pick MCU GPIO wakeup overlayPraneeth Bajjuri2023-11-151-0/+1
| | | | | | | | | | | | | | commit [1] renamed the MCU GPIO wakeup overlay as k3-am62x-sk-mcu-gpio-wakeup.dtbo k3-am62x-sk prefix picks this overlay for am62xx, am62axx and am62xxsip already. This patch picks the necessary overlay for am62xx-lp-evm since it doesnt use the same prefix as other am62 platforms. [1]: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?&id=24bd6ce832cd Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Reviewed-by: Judith Mendez <jm@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62*: extend picking common overlays by prefixPraneeth Bajjuri2023-11-094-6/+4
| | | | | | | | | | | | | | | | | | | | | commit f5851386 ("conf: machine: am62*: Pick common overlays by prefix") picks common HDMI and CSI overlays for am62 platform variants. Adding capability to extend the same prefix for common overlays for applicable am62 platforms in more generic way to include new mcan overlays added [1] [1]: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?&id=3b01c392627f given the differences in SK-AM62-LP containing B2B HDMI Samtec connector, just added the kernel prefix to pick common mcan overlay. for am62pxx: It has 4 MCANs vs all other am62xx devices have 3 MCANs, hence keeping this prefix seperate for am62pxx to pick right overlay. Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Reviewed-by: Jai Luthra <j-luthra@ti.com> Reviewed-by: Judith Mendez <jm@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Move IMAGE_BOOT_FILES to the SoC inc for J721s2 and J784s4Andrew Davis2023-11-085-12/+21
| | | | | | | | | | | These defines are specific to a SoC, not any specific board. Move these to the SoC level for these boards to be consistent with boards already doing this correctly. J7200 didn't have these at all, add them while we are here. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* k3r5: Remove ?= default assignment for the kernelRyan Eatmon2023-11-051-1/+1
| | | | | | | | The previous allowance for overriding the value for the kernel is incorrect. The kernel should not be changed from linux-dummy for the k3r5 multiconfigs. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* k3r5: Use the ?= default assignment to allow for overridesRyan Eatmon2023-11-021-3/+3
| | | | | | | | | | | Move to setting the values for PREFERRED_PROVIDER using the ?= default assignment so that we can override the setting if we would like to. Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Massimiliano Minella <massimiliano.minella@se.com> Acked-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Update OPTEEMACHINE for am62pxxChirag Shilwant2023-10-301-1/+1
| | | | | | | - OPTEEMACHINE for am62pxx should be k3-am62x. Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* am62pxx: set default gpudriver to ti-img-rogue-driverRandolph Sapp2023-10-281-1/+1
| | | | | | | Enable the GPU on the am62pxx-evm machine target. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62*: Pick common overlays by prefixJai Luthra2023-10-275-3/+18
| | | | | | | | | | | | | | | | | | SK boards of AM62 SoC family share peripheral expansions for camera and audio-over-HDMI. The HDMI bridge is common across all SK-AM62* boards. The CSI2 FFC camera connector is common across all except SK-AM62-LP which only has a B2B Samtec connector. As the kernel now uses the same prefix "k3-am62x-sk-" for the devicetree overlays for these peripherals, make sure we pick them by prefix for applicable boards. Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=b50ccab9e07c Link: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?&id=0432df3d2ae7 Signed-off-by: Jai Luthra <j-luthra@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: Add Support for am62pxx-evmChirag Shilwant2023-10-263-0/+43
| | | | | | | | | | | - Add A53 and R5 machine configurations for am62pxx-evm. - Add firmware overrides. - Add u-boot overrides. - Add cnm-wave support. Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Brandon Brnich <b-brnich@ti.com>
* conf: machine: move RDEPENDS and RRECOMMENDS from kernel-rdepends.incDenys Dmytriyenko2023-10-2419-15/+39
| | | | | | | | | | | | | | | Instead of making kernel RDEPENDS on devicetree and different FW images with lots of machine-override appends that are hard to modify downstream, use proper MACHINE_ESSENTIAL_EXTRA_RDEPENDS and MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS vars that are specifically designed for this purpose. This also makes such dependencies generic and not tied to a particular kernel recipe including kernel-rdepends.inc with the entire machine-specific list. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Acked-by: Andrew Davis <afd@ti.com> Acked-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: beagle*: recommend essential FW images for Beagle devicesDenys Dmytriyenko2023-10-204-0/+10
| | | | | | | | | | Set MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS per platform to list recommended essential FW images to be added to rootfs by default. Correct beagle-x15 to pull devicetrees and kernel image as well. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-bb.org: add back Beagle-specific U-boot 2023.04Denys Dmytriyenko2023-10-202-0/+5
| | | | | | | | | | | | | Majority of Beagle devices use ti-u-boot repo from u-boot-ti-staging directly. But some latest devices may need to point to own tree with additional support added that is not yet upstream, e.g. BeaglePlay. Add the Beagle-specific recipe and point beagleplay to use it. Other devices can switch to using it as well, if desired, but right now the code base is the same for other Beagle devices. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: beagleplay: trim down the DTB listDenys Dmytriyenko2023-10-201-33/+7
| | | | | | | | | Update DTB/DTBO list to only upstreamed devicetrees and overlays. This help with migration to kernel 6.1, which doesn't have BB.org specific overlays. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: beaglebone-ai64: trim down the DTB listDenys Dmytriyenko2023-10-201-53/+8
| | | | | | | | | Update DTB/DTBO list to only upstreamed devicetrees and overlays. This help with migration to kernel 6.1, which doesn't have BB.org specific overlays. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: include TI_COMMON_DEPLOY in PSEUDO_IGNORE_PATHSMatthias Schiffer2023-10-201-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since the introduction of TI_COMMON_DEPLOY, we've been seeing frequent Pseudo errors [1] breaking image build during development, in particular with partial rebuilds due to the externalsrc bbclass. The relevant part of the error log seems to be the following: ERROR: Task (/home/schifferm/Devel/src/ci-meta-tq-kirkstone/sources/meta -tq/meta-dumpling/recipes-images/images/tq-image-generic-debug.bb:do _rootfs) failed with exit code '1' Pseudo log: path mismatch [1 link]: ino 12215614 db '/home/schifferm/Devel/src/ci-me ta-tq-kirkstone/build-mba64xx/deploy-ti/images/tqma64xxl-mbax4xxl/tq -image-generic-debug-tqma64xxl-mbax4xxl-20231020091917.testdata.json ' req '/home/schifferm/Devel/src/ci-meta-tq-kirkstone/build-mba64xx/ tmp/work/tqma64xxl_mbax4xxl-tq-linux/tq-image-generic-debug/1.0-r0/r ootfs/usr/share/stress-ng/example-jobs/device.job;65324e26'. My understanding is that all deploy dirs should be ignored by Pseudo, as openembedded-core/meta/bitbake.conf includes the whole of DEPLOY_DIR in PSEUDO_IGNORE_PATHS. With the introduction of TI_COMMON_DEPLOY, DEPLOY_DIR_IMAGE is not covered by that setting anymore, so we add it in meta-ti to avoid the issue. [1] https://wiki.yoctoproject.org/wiki/Pseudo_Abort Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com> Acked-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* machine: include: enable sgx on tested platformsRandolph Sapp2023-10-174-4/+4
| | | | | | | Enable SGX Graphics on the currently tested platforms. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* k3r5: u-boot: prevent overlapping deployed SPL symlinksDenys Dmytriyenko2023-09-221-2/+2
| | | | | | | | | | | | Make sure shortname R5 SPL symlink is not the same as the main K3 SPL one, as they will overlap/overwrite each other when deployed into a common location. Latest code in master now checks for this and errors out. Also remove unused UBOOT_SPI_* variables. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: switch k3r5 multiconfig to baremetalDenys Dmytriyenko2023-09-212-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are couple of k3r5 components that need to be built for the target and they are self-contained and don't use glibc. Moreover, when building a cross-compile toolchain for k3r5, there's no need to build glibc and all its dependencies. While build-time speed up is nice, the main benefit comes when packaging a nativesdk toolchain for distribution, reducing the number of packages and the resulting size of the toolchain installer. To avoid potential namespace conflict in package feeds between nativesdk binary packages of Linux glibc and k3r5 baremetal toolchains, adjust the package suffix accordingly. This also requires a rather impactful change in the deployment structure, which affects CIs and user experience. By default different TCLIBC builds (e.g. glibc and baremetal in this case) are built in separate TMPDIRs to avoid conflicts, especially on the nativesdk side. Also the default config has DEPLOY_DIR residing under corresponding TMPDIR. Of course, this can be changed by local.conf or <distro>.conf, which meta-ti-bsp has no control over. Unlike multiconfig-image-packager example that can access deployed artifacts across multiconfigs to package in an image, we use wic and its IMAGE_BOOT_FILES list to package a final image. Unfortunately, wic cannot access deployed artifacts across multiconfigs in separate TMPDIRs, as it uses DEPLOY_DIR_IMAGE to collect the artifacts. To overcome this, we need to set up a "common" deploy directory for images and sdks produced by multiconfigs, which is located outside of TMPDIRs, set by TI_COMMON_DEPLOY variable that can be changed or adjusted by distros as needed. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Add am62xxsip-evm configurationChirag Shilwant2023-09-202-0/+29
| | | | | | | | | | - Add A53 and R5 machine configurations for am62xxsip-evm. - Use UBOOT_CONFIG_FRAGMENTS as am62xsip_sk_r5.config in R5 machine configuration. This will ensure we build u-boot-r5 with baseconfig as am62x_evm_r5_defconfig and config fragment as am62xsip_sk_r5.config. Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Reviewed-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* mesa-pvr: add dynamic-layer append for llvmpipeRandolph Sapp2023-09-121-0/+4
| | | | | | | | | | | | | | | Meta-clang provides a bbappend for mesa to use clang to accelerate it's rasterization with runtime code generation through the use of llvmpipe. With the addition of mesa-pvr we no longer get this for free with the blanket mesa bbappend on the devices that explicitly request mesa-pvr so lets add a dynamic layer to append the same args meta-clang does. Though the number of devices that would select pvr-mesa and still want to use software rendering is small, it's not zero due to debug and testing purposes. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/am65xx-hs-evm: Fix UBOOT_MACHINE to match u-boot configRyan Eatmon2023-08-302-2/+2
| | | | | | | | The uboot config for am65 is moving to a merged build for both GP and HS. Until the yocto configs catch up, we need to keep am65xx-hs-evm working. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: am335x-evm and am437x-evm: bump max_leb_cntRyan Eatmon2023-08-232-2/+2
| | | | | | New features added require another increase to max_leb_cnt. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: ti33x: Add earlycon parameter to kernel command lineJulien Panis2023-08-231-0/+1
| | | | | | | | | Sometimes on am335x devices, no more output is printed after "Starting kernel..." message. Modify UBOOT_EXTLINUX_KERNEL_ARGS to enable the console before standard serial driver is probed. Signed-off-by: Julien Panis <jpanis@baylibre.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/k3: switch mcdepends from do_image_completeDenys Dmytriyenko2023-08-081-1/+1
| | | | | | | | | | Previously k3 mcdepends for k3r5 artifacts has been changed from do_image_wic to support non-wic builds in other layers and do_image_complete was believed to be sufficient. Switching k3r5 to baremetal builds has exposed another race when some pieces come from sstate and hence requires using do_image instead. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-next,conf/machine: Add support for new vendored dts dirRyan Eatmon2023-07-315-2/+14
| | | | | | | | | | The latest kernel has made the change to add vendor subdirectories into the arch/arm/boot/dts directory. This effectively breaks the KERNEL_DEVICETREE settings in the machine configs for 32bit platforms, so switch them over to using the PREFIX variable. Also change the linux-ti-next to use the PREFIX setting for KERNEL_DEVICETREE. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am65xx: Remove SYSFW_SUFFIX from non-k3r5 configsAndrew Davis2023-07-212-4/+0
| | | | | | | This definition is only needed in the "-k3r5" multiconfig files. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: Remove old and no longer used MACHINE_FEATURESAndrew Davis2023-07-215-5/+5
| | | | | | | | | | The following MACHINE_FEATURES are not matched against anywhere, remove: * kernel26 * ethernet * mmc Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: Remove leftover UIO Device Tree overlay filesAndrew Davis2023-07-212-4/+0
| | | | | | | We do not use UIO anymore, remove these files. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti: conf: am62xx-lp-evm: Use common include am62xx.incPraneeth Bajjuri2023-07-132-16/+1
| | | | | | | | | | | | | | | | commit 5f9be228390b ("machine: Add AM62Q HS-SE evm configuration") has added am62xx-lp.inc which is used by am62xx-lp-evm machine. The features listed in am62xx.inc are common between machines am62xx-evm and am62xx-lp-evm. (Ex: MACHINE_FEATURES = "gpu") Hence updating the necessary include file to have common features to be enabled between these two platform variants. Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Suggested-by: Randolph Sapp <rs@ti.com> Reviewed-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: k3: Use ARM64 kernel load address in FITAndrew Davis2023-07-051-2/+2
| | | | | | | | | | | | | | | The address 0x80008000 was used in pre-K3 devices. ARM64 requires the kernel loaded to a 2MB aligned address when not using KASLR. For FIT set the address to 0x81000000 which gives the kernel 32MB before running into the FDT at 0x83000000. If you get this error someday then your kernel is too large and either it or FDT needs relocated in memory: ERROR: image is not a fdt - must RESET the board to recover. Signed-off-by: Andrew Davis <afd@ti.com> Tested-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j7*: Update KERNERL_DEVICETREE_PREFIX to match latest filenamesAniket Limaye2023-06-293-3/+6
| | | | | | | | 1) The k3-fpdlink-* dtbs were missing. 2) k3-j7200-mcspi-loopback.dts -> k3-j7200-evm-mcspi-loopback.dtso Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: include: k3 enable fit signing for ubootManorit Chawdhry2023-06-201-0/+7
| | | | | | | Enables FIT Image signing for K3 platforms Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: am335x-evm and am437x-evm: bump max_leb_cntRyan Eatmon2023-06-202-2/+2
| | | | | | New features added require another increase to max_leb_cnt. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62xx: Add TI logo as image boot fileDevarsh Thakkar2023-06-191-0/+3
| | | | | | | | | Add TI logo bitmap image as image boot file so that it gets copied to boot partition and A53 SPL or U-boot proper can load it and display during board bootup. Signed-off-by: Devarsh Thakkar <devarsht@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-extras: Add support for extra kernel/u-boot featuresParesh Bhagat2023-06-143-0/+7
| | | | | | | | | | | | | | | | There are some features that will either never be accepted into the upstream kernel, or are not ready to be accepted. ti-extras allows for controlling the kernel and u-boot repos, breanches, and srcrevs to gain access to those features via the TI_EXTRAS variable in the local.conf file. Initial support for TI_EXTRAS=tie-jailhouse is being added by this patch. Signed-off-by: Paresh Bhagat <p-bhagat@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Acked-by: Paresh Bhagat <p-bhagat@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: am335x-evm and am437x-evm: bump max_leb_cntRyan Eatmon2023-06-102-2/+2
| | | | | | New features added require an increase to max_leb_cnt. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am65xx: Update GP to SR2 firmwareAndrew Davis2023-06-062-3/+3
| | | | | | | SR2.0 firmware binaries should be used here as SR1.0 has been descoped. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62xx-lp: Default to HS-FS instead of GPAndrew Davis2023-06-061-1/+1
| | | | | | | This matches how we had the symlink for tiboot3.bin before binman. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62xx: Default to HS-FS instead of GPAndrew Davis2023-06-061-1/+1
| | | | | | | This matches how we had the symlink for tiboot3.bin before binman. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j721e: Also deploy full named tiboot3.bin filesAndrew Davis2023-06-061-3/+6
| | | | | | | | The platforms with combined boot image have full names for tiboot3.bin and to keep things consistent we can do the same here. Deploy these files. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am65xx: Also deploy full named tiboot3.bin filesAndrew Davis2023-06-061-2/+4
| | | | | | | | The platforms with combined boot image have full names for tiboot3.bin and to keep things consistent we can do the same here. Deploy these files. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Do not override SPL_BINARY on AM65x and J721eAndrew Davis2023-06-064-8/+0
| | | | | | | | In U-Boot the names of these files have been updated to match our expected defaults. Remove these fixups. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62xx: Remove old SPL_BINARY and UBOOT_BINARY overridesAndrew Davis2023-06-061-4/+0
| | | | | | | The defaults set in am62xx.inc are correct now and these can be dropped. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j784s4: Include the non-HS config in the HS configAndrew Davis2023-06-061-23/+1
| | | | | | | Everything is the same, so just include the non-HS config to set vars. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j721s2: Include the non-HS config in the HS configAndrew Davis2023-06-061-16/+1
| | | | | | | Everything is the same, so just include the non-HS config to set vars. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am65xx: Deploy SR2 version of SYSFWAndrew Davis2023-06-062-2/+2
| | | | | | | | The HS boards use the SR2 version of the silicon, ship that version of the sysfw.itb image. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Remove leftover k3r5 SOC_FAMILY namesAndrew Davis2023-06-063-3/+0
| | | | | | | | These are not used anymore and most have been removed, these look to be leftovers, remove them. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-14 03:02:35 +0000