summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* ti-rtos-firmware: Fix use of base_libdir with nonarch_base_libdirAndrew Davis2023-03-011-56/+56
| | | | | | | Firmware belongs in the nonarch lib directory. Use the right variable. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-rtos-firmware: Use a table instead of a list of copy commandsAndrew Davis2023-03-011-209/+67
| | | | | | | | | | | | | | | Using a table makes it easier to see what firmware is included with each machine build. It also helps prevent errors here. Since the same functions run across machines we now sign all the firmware without needing to add a new signing function for each new machine. Another fix is that we install the DM firmware to the deploy directory for all machines that use need it. This was added for J7x machines but missed for AM62x. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-rtos-firmware: Use defines to set firmware namesAndrew Davis2023-03-011-184/+201
| | | | | | | | This allows us to change the name in one spot and avoid duplication. It also helps prevent hard to see changes/typos in the firmware names. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-rtos-firmware: Do not break the source directory by renaming filesAndrew Davis2023-03-011-6/+6
| | | | | | | | If we rename files in the source directory the next time we need to rebuild the original files will be gone and build will fail. Use symlinks instead. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-rtos-firmware: Fix name for AM64x and AM62x firmwareAndrew Davis2023-03-011-18/+18
| | | | | | | | | | | | The firmware for AM64x and AM62x are renamed to match the other platforms, but we don't actually change them to match. Remove baremetal from the names. These are only referenced to by softlink, so this change will have no effect on Linux users. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-rtos-firmware: Remove unneeded per-machine TARGET definesAndrew Davis2023-03-011-147/+66
| | | | | | | | | Since these TARGET defines are only used on the machine for which an ALTERNATIVE is defined and always have the same name, these provide nothing. Drop them. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-k3-secdev: Remove inclusion of ti-paths.incAndrew Davis2023-03-012-5/+2
| | | | | | | | Since this directory path will not change, let's avoid use of ti-paths.inc which is set to be removed. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: k3: Remove unneeded TI_SECURE_DEV_PKG_K3 assignmentsAndrew Davis2023-03-018-16/+2
| | | | | | | | | For K3 machines the SECDEV selection happens in the recipes that use it. This assignment is therefor no longer needed. Remove it. Suggested-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: Use new ti-secdev class to sign the imagesAndrew Davis2023-03-011-6/+2
| | | | | | | | Use the new ti-k3-secdev package to pull in the signing tools if they are not provided by the environment. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-rtos-firmware: Use new ti-secdev class to sign the imagesAndrew Davis2023-03-011-6/+1
| | | | | | | | | | Use ti-k3-secdev native package to provide secure-binary-image.sh script when it is not passed on as an environment variable. This fixes an issue with AM64xx which is always HS but should not require TI_SECURE_DEV_PKG when building for HS-FS or GP platforms. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti: Use new ti-secdev class to sign the imagesAndrew Davis2023-03-011-2/+1
| | | | | | | | | | | | Use the new ti-k3-secdev package to pull in the signing tools if they are not provided by the environment. This allows us to use these tools unconditionally. Remove the checks for the script and do the signing for all K3 machines. The signature is automatically stripped from the binaries on non-HS devices at boot time as needed so this change is harmless for GP devices. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee-os: Use new ti-secdev class to sign the imagesAndrew Davis2023-03-011-36/+7
| | | | | | | | | | | | Use the new ti-k3-secdev package to pull in the signing tools if they are not provided by the environment. This allows us to use these tools unconditionally. Remove the checks for the script and do the signing for all K3 machines. The signature is automatically stripped from the binaries on non-HS devices at boot time as needed so this change is harmless for GP devices. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* trusted-firmware-a: Use new ti-secdev class to sign the imagesAndrew Davis2023-03-011-32/+7
| | | | | | | | | | | | Use the new ti-k3-secdev package to pull in the signing tools if they are not provided by the environment. This allows us to use these tools unconditionally. Remove the checks for the script and do the signing for all K3 machines. The signature is automatically stripped from the binaries on non-HS devices at boot time as needed so this change is harmless for GP devices. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: Add helper class for TI Security Development ToolsAndrew Davis2023-03-011-0/+21
| | | | | | | | | The setup here is common to all packages that require signing with the TI Security Development Tools. Add a helper class to factor out this commonality. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-linux-fw: update to the latestAndrew Davis2023-03-011-10/+6
| | | | | | | | | While here update FW versions and remove those no longer used. Signed-off-by: Andrew Davis <afd@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com> Tested-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-umlibs: handling the firmware installation with usrmergeJose Quaresma2023-03-011-0/+4
| | | | | | | The ti-img-rogue-umlibs package is not obeying usrmerge distro feature. /lib should be relocated to /usr. [usrmerge] Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine: fix use of screen and touchscreen machine featuresDenys Dmytriyenko2023-02-245-6/+4
| | | | | | | | Some machine configs didn't specify their use of screen and touchscreen machine features correctly, fix them. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Fallback to software renderingRyan Eatmon2023-02-244-4/+4
| | | | | | | | | | | While we are working to update our platforms to support Weston 10 and beyond, we are falling back to software rendering for platforms that do not currently have a solution for GPU drivers (namely the boards that use SGX). Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: machine: set SGX display controller aliasRandolph Sapp2023-02-243-0/+9
| | | | | | | | | Set SGX display controller alias variables accordingly, as SGX has a few different aliases across platforms. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: machine: remove default preferences for egl,gles,gbmRandolph Sapp2023-02-249-34/+0
| | | | | | | | | | | Remove default preferences for virtual/egl, virtual/libgles and virtual/libgbm from machine configs to follow the new dependency chains via mesa in oder to support accelerated and software-rendered graphics, which is selected by virtual/gpudriver preference. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: graphics: Resolve dependency chainRandolph Sapp2023-02-248-113/+105
| | | | | | | | | | Patched mesa will now be configured based on what virtual/gpudriver preferred provider is selected. The gpu drivers will now runtime recommend the associated UM components. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* mesa: locally overlay 22.0-specific patches from oe-core/kirkstoneDenys Dmytriyenko2023-02-246-0/+367
| | | | | | | | | | Locally overlay verbatim copies of mesa 22.0 patches from oe-core/kirkstone, so the same codebase works in kirkstone and master. Since upstream version of mesa in master is now 22.3 and no longer carries these patches, but they are still needed for 22.0-based PVR fork of mesa used with Rogue driver. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Revert "meta-ti-bsp: graphics: Resolve dependency chain"Denys Dmytriyenko2023-02-219-97/+141
| | | | | | | | | Merged by accident. This reverts commit 15417ca726f75881a2c51c08d258ea923803cbb9. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Revert "meta-ti-bsp: machine: Remove all gpu features"Denys Dmytriyenko2023-02-219-5/+45
| | | | | | | | | Merged by accident. This reverts commit 51bb56b74cd2e7f7e922cce84a023f669291ef00. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Revert "meta-ti-bsp: machine: Attempt to update DC alias"Denys Dmytriyenko2023-02-213-9/+0
| | | | | | | | | Merged by accident. This reverts commit 0dd6a86b9a20bc1117d19bec3e642602b6c54b8c. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Revert "conf: machine: Fallback to software rendering"Denys Dmytriyenko2023-02-214-4/+4
| | | | | | | | | Merged by accident. This reverts commit 5ae790999e762063446ec4623693eecd8ecd6be9. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Fallback to software renderingRyan Eatmon2023-02-164-4/+4
| | | | | | | | | While we are working to update our platforms to support Weston 10 and beyond, we are falling back to software rendering for platforms that do not currently have a solution for GPU drivers (namely the boards that use SGX). Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: machine: Attempt to update DC aliasRandolph Sapp2023-02-163-0/+9
| | | | | | | | | Attempt to update the SGX display controller alias variable according to what Andrew told me. SGX apparently had a few different aliases across platforms. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: machine: Remove all gpu featuresRandolph Sapp2023-02-169-45/+5
| | | | | | | | | Remove all gpu machine features and instead rely on the new dependency chain for resolving gpu dependencies. Set preferred providers for virtual/gpudriver where needed. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: graphics: Resolve dependency chainRandolph Sapp2023-02-169-142/+97
| | | | | | | | | Patched mesa will now be configured based on what virtual/gpudriver preferred provider is selected. The gpu drivers will now runtime recommend the associated um components. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine/k3r5.inc: update bootflow linksDenys Dmytriyenko2023-02-161-2/+3
| | | | | | | | | Original READMEs with bootflows were reworked and moved to a dedicated doc/ folder in more recent U-boot versions. Update links in the k3r5 config file accordingly to provide some basic explanation of K3 bootflows. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* uio-module-drv: Remove deprecated uio-module-drvAndrew Davis2023-02-1610-1192/+0
| | | | | | | | | | UIO drivers are generally frowned upon in the community, and for PRU we now have much better alternatives in RProc, RPmsg, and PRU-Consumer. Let's not send the wrong message by continuing to support this crufty interface. Remove the kernel module, DTBs, and test recipe. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-bb.org: work around for too few arguments to function ↵Ryan Eatmon2023-02-071-1/+2
| | | | | | | | | | | | | | | | | | | | | init_disassemble_info() error binutils 2.39 changed the signature of init_disassemble_info(), which now causes perf and bpftool to fail to compile. Relevant binutils commit: [1] There is a proper fix in development upstream[2]. This is a work-around for older kernels. Inspired by a patch by Anton Antonov to fix this issue on meta-arm kernels. [3] [1] https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=60a3da00bd5407f07d64dff82a4dae98230dfaac [2] https://patchwork.kernel.org/project/netdevbpf/cover/20220801013834.156015-1-andres@anarazel.de/ [3] https://patchwork.yoctoproject.org/project/arm/patch/20220824025819.4888-1-jon.mason@arm.com/#5104 Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: add BeagleBone AI-64 supportDenys Dmytriyenko2023-01-315-0/+153
| | | | | | | | | | | | | BeagleBone AI-64 (https://beagleboard.org/ai-64) uses Texas Instruments Jacinto TDA4VM/J721e SoC. Officially BeagleBone AI-64 supports Debian Linux and builds its BSP on top of meta-ti and TI SDK, but adds custom DTBs and DTBO overlays, plus integrates other drivers and features. Let's add corresponding recipes for beagleboard.org kernel and u-boot along with the BeagleBone AI-64 machine config. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sgx-ddk-um: use udev for userspace initializationMatthias Schiffer2023-01-312-1/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The ti-sgx-ddk driver requires an additional userspace initialization step after the kernel module has probed the device. Without this initialization, no EGL context can be created and Weston etc. will fail to start. The driver package contains an init script, but this does not work on pure systemd-based systems without sysvinit compat support (as provided by the systemd-compat-units package). Introduce an enabled-by-default PACKAGECONFIG that installs a udev rule instead to run the init command automatically when the driver is loaded, solving the issue without depending on a specific init system. On builds without udev, this PACKAGECONFIG can be disabled, reverting to the old init script-based solution. udev reports several events when the pvrsrvkm module is loaded: - add event for the kernel module - add events for two DRM devices - bind event for the GPU platform device The DRM devices aren't nice to match on, and the kernel module add is too early to run `pvrsrvctl --start`, so we trigger on the platform device bind. Tested with Weston 9.0.0 on the AM65x-based TQ-Systems MBa65xx. Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* treewide: replace leftover git://git.ti.comMatthias Schiffer2023-01-312-2/+2
| | | | | | | | These URIs have been updated in dunfell, but two instances were forgotten in kirkstone/master. Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: sets TI_K3_SECDEV_INSTALL_DIR default valueJose Quaresma2023-01-311-0/+2
| | | | | | | | | | The TI_K3_SECDEV_INSTALL_DIR is defined on the meta-ti-extras layer so when the layer is not used the variable is undefined. For such cases we can use default value that is the same defined on the recipes-ti/includes/ti-paths.inc Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-k3-secdev: sets TI_K3_SECDEV_INSTALL_DIR_RECIPE default valueJose Quaresma2023-01-311-0/+2
| | | | | | | | | | | The TI_K3_SECDEV_INSTALL_DIR_RECIPE is defined on the meta-ti-extras layer so when the layer is not used the variable is undefined. For such cases we can use default value that is the same defined on the recipes-ti/includes/ti-paths.inc Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Acked-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-k3-secdev: move from meta-ti-extras to meta-ti-bspJose Quaresma2023-01-311-1/+1
| | | | | | | | | | | | | | | | | | | | | | The meta-ti-bsp layer is still broken for K3 HS platforms. The patch [1] makes the check-layer happy again as it does not fail any more during bitbake parsing but it will be difficult for the end user to discover this dependency on meta-ti-extras. On the other side, meta-ti-extras depends on meta-ti-bsp so this is a circular dependency. Currently the layer is broken for am62xx-evm/am64xx-evm machines: | ERROR: Nothing PROVIDES 'ti-k3-secdev-native' (but mc:k3r5:/srv/oe/build/conf/../../layers/meta-ti/meta-ti-bsp/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb DEPENDS on or otherwise requires it). Close matches: | libtspi-dev-native | makedevs-native [1] - 8e43835c ti-sci-fw: make dependency on meta-ti-extras soft Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Acked-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Rework do_image_wic dependenciesAndrew Davis2023-01-2415-52/+17
| | | | | | | | | | | | | | | | | | The WIC image for K3 depends on the TI-SCI firmware, on AM65x and J721e also the bootloader. Make this clear by only depending on firmware in the base k3.inc file, then adding the bootloader dependency in AM65x and J721e specific includes. Remove unneeded overrides from the evm level files. Remove do_image_tar dependencies as the tar files do not include the bootloader nor TI-SCI firmware, only the boot partition of the WIC file needs these. 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 TFA_BOARD and OPTEEMACHINE to the SoC levelAndrew Davis2023-01-249-12/+17
| | | | | | | | | These defines are specific to a SoC, not a SoC family (K3) nor any specific board. Move these to the SoC level for all boards to be consistent with boards already doing this correctly. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Remove OPTEEOUTPUTMACHINE definitionAndrew Davis2023-01-2410-10/+0
| | | | | | | | This was used in the base Linaro optee-os_git.bb recipe, it is no longer used, remove it from our boards. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Remove j7 grouping and j7.incAndrew Davis2023-01-245-9/+16
| | | | | | | | | | | J7 is an unneeded level of grouping that is now causing issues and leading to mistakes when adding new J7 based platforms. Each J7x family device should use the SoC name specifically to prevent accidentally adding or removing features that are not meant for the new SoC. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Use new J7 SoC names over specific board namesAndrew Davis2023-01-248-35/+34
| | | | | | | | | | | | | | | | Now that we have SoC names, we can avoid adding features based on the board name. We expect folks to create their own boards based on these SoCs, and so using the TI made EVM board name everywhere adds extra churn when adding a new board. Plus it is more correct for most of these features as they depend on the SoC, not on the EVM board. One other thing we do here is to not use the generic "j7" name, the current and future J7 devices are far to feature diverse to group at this level. Grouping like that will lead to the wrong things getting enabled as new J7 SoCs are added. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j784s4: Move common defines into j784s4.incAndrew Davis2023-01-242-3/+11
| | | | | | | | | Like we do with J721e, J7200, and J721s2, use a SoC header include file to define common properties. This eases adding new boards based on these SoC. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Remove multi-certificate image commentAndrew Davis2023-01-241-2/+0
| | | | | | | Multi-cert is already now the default, no need to add a comment on that. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee-os: sync up with upstream meta-arm updateDenys Dmytriyenko2023-01-241-9/+0
| | | | | | | | Upstream meta-arm has updated optee-os to 3.19 and our local changes conflict with that. Update bbappend to match upstream. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: Move legacy HS signing classes into this layerAndrew Davis2023-01-246-0/+932
| | | | | | | | | These were in the meta-arago layer, but any distro should be able to run on HS devices. So move the classes and setup to the BSP layer. Signed-off-by: Andrew Davis <afd@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sgx-ddk-um: Update SRCREV for Kirkstone supportAndrew Davis2023-01-241-4/+5
| | | | | Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: Add am57xx.inc allowing use of SoC name over full EVM nameAndrew Davis2023-01-249-18/+17
| | | | | | | | | | In many spots we have to use the full EVM name for each EVM using the AM57x SoC leading to missed features on some EVMs. Add the am57xx name so we can generically add for AM57x. Signed-off-by: Andrew Davis <afd@ti.com> Reviewed-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 19:11:58 +0000