All other firmware recipes are in recipes-bsp. There is nothing much
special about this set of firmware so move it to match.
This firmware is the pre-compiled "echo test" example for various
remote cores. The directory name is not very clear on that, so fix
that up too.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* The GP variant of AM62A SoC was only used internally
for initial device bring-up and is not publicly available.
Hence, drop it from IMAGE_BOOT_FILES to ensure
tiboot3-am62ax-gp-evm.bin is not packaged inside vfat boot
partition of wic image
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
New features added under meta-tisdk [0] require another
increase to max_leb_cnt.
[0]: 3985a7caea
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* U-Boot reads the bootsplash image file from the vfat boot partition
& displays it during boot-up showcasing early splash screen support.
* There's no significance of having an additional do_install
as the logo file need not be added in the rootfs/image.
* Fixes 277f04df4c & 1fed958bfe
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
FIT_CONF_DEFAULT_DTB config specifies the default dtb file for the
FITimage when multiple ones are provided[1].
Legacyhs fitimage does not currently support this feature set which is
required for repurposing the same class for falcon boot.
This patch adds support for FIT_CONF_DEFAULT_DTB without affecting
existing platforms that rely on legacyhs fitImage.
[1]:
https://docs.yoctoproject.org/ref-manual/variables.html#term-FIT_CONF_DEFAULT_DTB
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add a recipe to deploy the HSM demo firmware to the DEPLOYDIR, to be
picked up by the tisdk-core-bundle for the prebuilt binaries directory.
This firmware is then further picked by U-Boot and packaged inside
tispl.bin FIT image for loading the HSM M4 core in applicable SoCs.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* New features added under meta-tisdk [0] require another
increase to max_leb_cnt.
* This patch fixes following errors observed with 11.00.09.04
tag on meta-tisdk,
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This patch adds prefix string for eqep overlay to
KERNEL_DEVICETREE_PREFIX.
Signed-off-by: Judith Mendez <jm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the srcrev to include a fix for events where the driver is
requested to show advanced information about file descriptors that are
associated with the device but are not currently associated with a
rendering task.
This should address the kernel fault in pvr_show_fdinfo associated with
fdinfo/lsof.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Fix the package config params to make it obvious what combinations are
allowed. Also, rework the way we are inheriting init related classes so
that we don't accidentally do any additional postinstall steps. While
we're at it, don't execute anything for the compile or configure stage.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
FIT_CONF_DEFAULT_DTB config specifies the default dtb file for the FIT
image when multiple ones are provided[1].
Since the variable is not set in current machine configs, the default is
set to the first dtb read during FIT image creation which doesn't give
us direct control over the default configuration.
Therefore this patch adds default dtbs for am62 evms.
[1]:
https://docs.yoctoproject.org/ref-manual/variables.html#term-FIT_CONF_DEFAULT_DTB
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
To facilitate better testing we need to control all aspects of the
SRC_URI. Create TI_LINUX_FW_GIT_URI, TI_LINUX_FW_GIT_PROTOCOL, and
TI_LINUX_FW_GIT_BRANCH and build SRC_URI using them.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The user mode libraries needed recompiling with the scarthgap revision of gcc to
remove all the warnings about 32bit API usage during the linking stage, new
SRCREV includes this changes. Versions of the libraries remain the same.
Signed-off-by: Antonios Christidis <a-christidis@ti>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
MACHINE_FEATURE gc320, already gets set on omap-a15.inc. But ti-bsp.inc file,
removes the feature. So, remove that portion of functionality from ti-bsp, in
order to allow the building of gc320 in kernel 6.12.
Signed-off-by: Antonios Christidis <a-christidis@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Changes made on the gc320 kernel mode driver in order to work with kernel
6.12. There is no other change in functionality with this update, and the
driver version remains the same.
Signed-off-by: Antonios Christidis <a-christidis@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump SRCREV to include a patch that changes the way
compiler_preferred_target is selected for a given toolchain. This now
checks specified SYS_CFLAGS to see if hardfloat is set explicitly and
will override the default target selection if necessary.
Signed-off-by: Randolph Sapp <rs@ti.com>
Tested-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The meta-arm layer, which is the provider of the base recipe for
optee-os, added [1] a separate optee-os-ta package for the embedded TAs
that are compiled as part of the OPTEE OS build process. However, the
TI overrides for optee-os include the embedded TAs inside the base
package, leaving the optee-os-ta package empty (and thus not
installable).
Align to the meta-arm behaviour and simply add a runtime dependency on
optee-os-ta for optee-os. While keeping backward compatibility, this
allows to install only the embedded TAs - reducing the required disk
space - on platforms on which the OPTEE OS is loaded from an external
boot image rather than being fetched from the root filesystem, like the
K3 SoCs.
[1] https://patchwork.yoctoproject.org/project/arm/patch/20230630112340.3314395-1-r.czerwinski@pengutronix.de/
Signed-off-by: Francesco Valla <francesco@valla.it>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Correct SRCREV for jailhouse which currently points to an unpublished
commit hash.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Out-of-tree module failing to build against linux-next as a result of
changes to platform driver remove function.
Signed-off-by: Brandon Brnich <b-brnich@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Fix OS APM interactions when uninitialized. Because this driver uses
lazy initialization, if the GPU is never given a task it will not be
initialized. Even if the device is not fully initialized it is still
registered with the DRM subsystem and capable of receiving OS APM
signals.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Well, this is the evil vendor driver. Time to start acting like it.
Blacklist the upstream powervr module if this driver is present.
This patch also does away with the bin_package components. It was cool
and found some interesting bugs, but we might as well start leveraging
that Makefile more now that we're starting to get some more common
files between devices.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Module recipe is missing SUMMARY and a proper SRC_URI leading to
warnings during the build process.
Fixes: 296344c8 ("ti-bsp: ti-img-encode-decode: Add Recipe for Building VXE-VXD Out-of-Tree Module")
Reported-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Brandon Brnich <b-brnich@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The new out of tree module ti-vxe-vxd-driver is only for the 6.12 kernel
and later. Since we support multiple BSPs we need to correctly wrap
this addition behind some additional logic that can make sure to not
include it for the 6.1 and 6.6 kernel builds where the module is still
in the tree.
Additionally, fix up the beaglebone-ai64 since it includes the j721e.inc
file and will need to clear this variable for its BSPs as well.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Rather than using COMPATIBLE_HOST move to using COMPATIBLE_MACHINE to
limit the recipe to being TI specific. Also, this package is "k3"
specific so further limit it down to just those matching machines and
not all TI SOCs.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The previous commit incorrectly added the k3-j721s2-evm-ub954.dtbo to
the KERNEL_DEVICETREE and it was missed during a quick review.
The correct way to add dtbs is to add a prefix string to the
KERNEL_DEVICETREE_PREFIX variable so that all files that match the
string will be picked up. This allows for multiple kernels to be
swapped out that may have different DTBs in their respective trees and
not break a build.
The upstream testing on the kernel will automatically update the
KERNEL_DEVICETREE variable when the final kernel version is available.
That way the KERNEL_DEVICETREE always points to what is available in the
mainline.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The previous commit incorrectly added the k3-j721e-evm-ub954.dtbo to
the KERNEL_DEVICETREE and it was missed during a quick review.
The correct way to add dtbs is to add a prefix string to the
KERNEL_DEVICETREE_PREFIX variable so that all files that match the
string will be picked up. This allows for multiple kernels to be
swapped out that may have different DTBs in their respective trees and
not break a build.
The upstream testing on the kernel will automatically update the
KERNEL_DEVICETREE variable when the final kernel version is available.
That way the KERNEL_DEVICETREE always points to what is available in the
mainline.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
IMG codec drivers reside only on the J721e SoC. Ensure that the drivers
are being built when building SDK.
Signed-off-by: Brandon Brnich <b-brnich@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
During 10.0 LTS bringup, the decision was made that it would be the last LTS
that carried the IMG VXE and VXD driver in tree. Driver is now hosted on
git.ti.com. This recipe is responsible for pulling in the driver,
building it, and packaging it within the J721e SDK.
Signed-off-by: Brandon Brnich <b-brnich@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
All K3 SoCs utilize the binman packaging tools in U-Boot to package
and sign the different boot firmware components needed to boot the
various security variants of K3 platform. Disable UBOOT_SIGN_ENABLE
to simplify the build
Signed-off-by: Bryan Brattlof <bb@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
DS90UB954-Q1EVM can be used to connect FPDLink-III based sensors to
TI EVMs. So pick the DS90UB954-Q1EVM overlay.
Signed-off-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
DS90UB954-Q1EVM can be used to connect FPDLink-III based sensors to
TI EVMs. So pick the DS90UB954-Q1EVM overlay.
Signed-off-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
OPTEE support for the am62lxx is still in progress.
Therefore, temporarily set TFA_SPD to empty to avoid
using any SPD (Secure Payload Dispatcher) services.
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The original .bbappend started with just a few customizations behind
a :k3 SoC override, but eventually grew in size. It got converted into
a .inc file, which is behind the same SoC override and hence it gets
included by .bbappend only for K3 platforms:
https://git.yoctoproject.org/meta-ti/commit/?id=389f9a8b726868768a8bed6cbe0b2a1f18c05410
It doesn't make sense to use the same :k3 override inside this .inc
file for every variable. Moreover, it makes it harder to change
those variables downstream for any derivative platform or even for
upstream testing.
This change drops redundant :k3 SoC overrides, w/o changing existing
behavior. It allows easier modifications of such customizations from
downstream layers or a local.conf, e.g. SRC_URI_TRUSTED_FIRMWARE_A
Note that SRC_URI is set exactly the same as in upstream base .inc
file, but version-specific recipes in meta-arm tend to add extra
patches directly to SRC_URI, which is undesirable here. Thus, reset
SRC_URI back to its default.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add am62lxx as compatible machine for ti-extras recipes and jailhouse
recipes. This is to to control the kernel and u-boot repos, branches.
So the am62lxx jailhouse build can be done by adding TI_EXTRAS=tie-jailhouse
in local.conf.
Update SRCREV and branch in ti-extras recipes for LTS migration.
Also update jailhouse recipe to build and package jailhouse, cell files,
device tree for inmate etc on am62lx image.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the bb_org-6.6 bsp provider to pick the correct version of
mesa-pvr. This probably should have be a part of the previous patch
switching ti bsp logic as well.
Fixes: 0be0a5f6 (ti-bsp: select the graphics 24.2 packages, 2025-01-22)
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the source revision to allow this module to work on kernel 6.12.
Originally this was going to be a separate branch, but considering the
bsp selector logic, this makes just as much sense.
Also enable the sgx driver in the ti_6.12 bsp selector.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Relocate the patches for 22.3.5 to the mesa-pvr-22.3.5 subdirectory so
it's more clear what version of mesa they apply to.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
No reason to do this pre install now that my python function can
evaluate file paths. Also, this may have been causing issues with state
when attempting to switch between opencl enabled/disabled builds.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since this is new logic is in place, switch the k6.6 and k6.12 configs
to use these new libraries. Do not enable GFX on 6.12 just yet. Still
need some kernel patches on the SGX side.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The gfx library provided by rogue can support this never version of mesa
out of the box. Pull it in now that we have ported the SGX side of
things.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the package version for DDK 24.2, this includes a few fixups from
IMG and support for a newer version of mesa.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Currently, the overlay mentioned in KERNEL_DEVICETREE_PREFIX in case
of j722s is "k3-j7200-evm-mcspi-loopback" which is incorrect. Change
the overlay to "k3-am625-sk-mcspi-loopback.dtso" in order to carry
out SPI loopback tests successfully.
Fixes: 13b691a9bc ("conf: machine: j722s: Add overlay to
KERNEL_DEVICETREE_PREFIX")
Signed-off-by: Anurag Dutta <a-dutta@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We have a need for some platforms to add kernel options to the bootloader
during wic creation time. Create a new variable and add that to the
sdimage-2part-efi.wks.in file so that a machine can override it if
needed.
Add an override for am64 to point the kernel at console=ttyS2.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add logic to generate UBI filesystem images which can be used to directly
flash into the NAND’s file-system partition.
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump up SRCREV of optee-os to ef1ebdc23034a804a72da2207f1a825ce96a1464
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add the overlay "k3-j7200-evm-mcspi-loopback.dtso" to the j722s
configuration so that SPI loopback tests can be carried out
successfully.
Signed-off-by: Anurag Dutta <a-dutta@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
ti-linux-kernel tree has several prune config fragments for ARM/ARM64/RT
configurations. Enable the prune config fragments here.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Acked-by: Andrew Davis <afd@ti.com>
All current K3 devices use either A53 or A72. Use the compile tune
configuration specific for these to allow the compiler to make
better optimizations.
Default tune here is weakly set to a lowest common denominator of
aarch64, as before, which is a recommended behavior for a BSP layer.
This allows for greater binary reuse (packages, sstate, etc.) across
different platforms of the same architecture in multi-BSP environments.
At the same time, since all the correct tunes are now configured for
K3 devices, one can elevate compiler optimization levels either from
local.conf or own Distro configuration on a per-SoC or per-device
basis, like so:
DEFAULTTUNE:k3 = "armv8a-crc"
DEFAULTTUNE:j721e = "cortexa72-cortexa53"
DEFAULTTUNE:beagleplay = "cortexa72-cortexa53"
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Rather than override the value for SPL_BINARY for all bsps, simply just
set the value to the correct value. This should be ok since all
beaglebone-ai64 variations should use tispl.bin_unsigned.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The defaults for UBOOT_MACHINE and SPL_BINARY are now aligned with the
mainline values and new ti-6_1 values for the previous defaults were
created to capture those. Also updated the meta-beagle beagleplay since
it inherits the beagleplay-ti settings.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The ti-cgt-arm compiler is a custom TI compiler. It does not
currently support reproducible builds and is provided via a
binary blob download that we cannot patch in the recipe to
address the issue.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update SRCREV to pick up patch that fixes some compile errors:
../git/memplugin_linux.c: In function 'memplugin_alloc':
../git/memplugin_linux.c:69:9: error: implicit declaration of function 'dsp_dce_buf_lock' [-Wimplicit-function-declaration]
69 | dsp_dce_buf_lock(1, &(h->dma_buf_fd));
| ^~~~~~~~~~~~~~~~
../git/memplugin_linux.c:71:9: error: implicit declaration of function 'dce_buf_lock' [-Wimplicit-function-declaration]
71 | dce_buf_lock(1, &(h->dma_buf_fd));
| ^~~~~~~~~~~~
../git/memplugin_linux.c: In function 'memplugin_free':
../git/memplugin_linux.c:91:17: error: implicit declaration of function 'dsp_dce_buf_unlock' [-Wimplicit-function-declaration]
91 | dsp_dce_buf_unlock(1, &(h->dma_buf_fd));
| ^~~~~~~~~~~~~~~~~~
../git/memplugin_linux.c:93:17: error: implicit declaration of function 'dce_buf_unlock' [-Wimplicit-function-declaration]
93 | dce_buf_unlock(1, &(h->dma_buf_fd));
| ^~~~~~~~~~~~~~
../git/memplugin_linux.c:95:13: error: implicit declaration of function 'close'; did you mean 'pclose'? [-Wimplicit-function-declaration]
95 | close(h->dma_buf_fd);
| ^~~~~
| pclose
and
../git/libdce_linux.c: In function 'dce_deinit':
../git/libdce_linux.c:90:9: error: implicit declaration of function 'close'; did you mean 'pclose'? [-Wimplicit-function-declaration]
90 | close(OmapDrm_FD);
| ^~~~~
| pclose
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There were some errors related to ipk postinst. The issues were fixed
by going to the update-alternatives class instead of trying to create
the steps directly in the recipe.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The script that sends the automated patch does not currently handle
updating the KERNEL_REPRODUCIBILITY_PATCHES variable with the changes in
the patches.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Like we do with GPU support, GC320 support is conditional on the
kernel we are building and so should be disabled here for kernels
on which it is not functional yet.
We can then remove these disabling lines as the driver is updated
for each supported kernel, instead of blanket disabling in the
distro layer as done currently.
Signed-off-by: Andrew Davis <afd@ti.com>
This might have been useful for building development packages with
the pre-built binaries for deployment elsewhere, but there are
better ways to do this and these are no longer consumed. Remove
this packaging step.
Signed-off-by: Andrew Davis <afd@ti.com>
This might have been useful for building development packages with
the pre-built binaries for deployment elsewhere, but there are
better ways to do this and these are no longer consumed. Remove
this packaging step.
Signed-off-by: Andrew Davis <afd@ti.com>
This was used when the kernel had a different configuration for
the testing kernel. This has not been the case since v5.10 so
drop the systest kernel package as it will be the same as the
normal kernel package now.
Signed-off-by: Andrew Davis <afd@ti.com>
We are moving to 6.12 to be our new LTS, so we are switching the default
BSP to that. You can still access the 6.6 kernel if you need to by using
the BSP system and setting TI_PREFERRED_BSP = "ti-6_6" in your
local.conf.
Current known issues:
- Hardware graphics is disabled until we get a patch that updates the
patches to work with the 6.12 kernel. Falling back to software
rendering.
- am62xxsip-evm and j742s2-evm are not supported in the 2025.01 u-boot
yet. They will fail to build until the u-boot recipe is updated to
point to a commit that fixes their support.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There was a fix for "buildpaths" QA error in master that got backported
to scarthgap, but out of 2 references to the new UNPACKDIR, one got
corrected, but the other one was left behind. Since scarthgap has no
notion of UNPACKDIR, replace it with corresponding WORKDIR.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Rogue graphics driver 24.1 currently fails to build against the kernel
that enables FORTIFY_SOURCE, such as bb.org. Disable this config for now,
until the driver is fixed.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Most Beagle platforms are switching to 6.6 based Linux kernel and U-boot
2024.10. Add corresponding recipes and extend beagle-bsp with required
settings.
BeagleY-AI for now remains on 6.1 BSP with U-boot 2023.04.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Rename "bb_org" BSP recipes to include version in the recipe names.
This way we can support multiple versions.
Also remove 2 unused kernel patches that were needed for 5.10
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Move "bb_org" kernel and U-boot providers that use corresponding official
BeagleBoard.org trees into own meta-beagle layer.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Extract "bb_org" BSP specific settings from beagleplay-ti in meta-ti-bsp and
move them to own beagleplay machine config in meta-beagle.
The differences between 2 configs are minimal, hence beagleplay in meta-beagle
inherits beagleplay-ti from meta-ti-bsp as a base and only adjusts what's
needed.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
OE-Core master has switched from lz4c to lz4 host tool, but a corresponding
change only appears in kernel 6.13. Since bb.org kernels 6.1 and 6.6 enable
LZ4 compression by default, also add a legacy lz4c tool in the list.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
The new meta-beagle will host all supported Beagle platforms that
use TI SoCs and hence need to depend on meta-ti-bsp. The default
BSP for the platforms in this layer will use BeagleBoard.org
official trees for the Linux kernel and U-boot.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
BeaglePlay is officially supported by TI "ti-6_6" BSP and is part
of the TI-SDK releases. Switching BSP to BeagleBoard.org "bb_org"
settings for the same machine is possible within the same layer.
But having different machine configs for the same machine name in
multiple layers can be confusing and prone to errors. Hence rename
the config to indicate BeaglePlay with official TI support in order
to re-use the canonical name in a separate layer.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Early Boot of remote processors is supported at the SPL stage of the
bootloader. Currently, SPL looks for the remoteproc firmwares in the
boot partition.
Therefore, add the rproc firmware to the boot partition of wic images.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Early boot of remote processors from SPL stage of bootloader requires
the remoteproc firmware to be present in the boot partition. Deploy this
rproc IPC firmware so that it can be copied to the boot partitions of
the wic images.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
This package provides Linux-side components for TI IPC and depends on
virtual/kernel Linux kernel for the build, so it is not compatible with
non-Linux builds, such as k3r5 baremetal multiconfig. Hence adjust
COMPATIBLE_HOST accordingly.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Add a SECURITY file with hints for security researchers and other
parties who might report potential security vulnerabilities.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Acked-by: Denys Dmytriyenko <denys@konsulko.com>
This IPC example is no longer supported nor recommended for new designs.
The documentation is no not available either (was on Processors Wiki).
Remove this example.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump versions of mesa-pvr and ti-sgx-ddk-km to support SGX with kernel
6.6 and the same version of mesa rogue is using.
Enable SGX by default in the 6.6 BSP provider section logic.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update to commit 58b25570c9ef91753b14c2103f45f4be9dddb696, which adds
the DM_MANAGED suspend feature.
58b25570c9
Also change the docs/license.rst checksum. The license file was
modified to include a reference to the pydevicetree project which uses
the Apache License 2.0.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The mesa.inc that we inherit from oe-core now has the required
parameters. This conditional append is no longer required.
This reverts commit dbc6afc46e.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
PREFERRED_VERSION matches against the PV in the recipe, not against the
file name. With the upcoming 6.12, the 6.1 kernel version string was a
little too loose. The "6.1%" could glob onto the 6.12 recipe. Take
this time to also clean up a couple of the other versions and narrow
them down.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add bsp-ti-6_12 overrides in A53 & R5 machine configuration
to ensure it picks the appropriate u-boot configs for beagleplay
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We are planning on adding upstream u-boot testing against stable tagged
versions of u-boot and need a little more control over telling bitbake to
not point at a branch but point to a tag.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update to the latest u-boot release v2024.10.
Additionally, take this time to clean up the mainline recipe and
streamline it a bit.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Our upstream testing needs to point to both master and master-next and
we need two different recipes to track that. This recipe mirrors the
linux-ti-next recipe and points to the master-next branch for the latest
bleeding edge changes.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
It was suggested to move the reproducibility patches out of
ti-kernel.inc and into the respective recipes.
Taking this time to also rework all of the pieces that go into the SRC_URI
and create a standardization for how all of the kernel recipes are done.
Create KERNEL_GIT_URI, KERNEL_GIT_PROTOCOL, KERNEL_GIT_BRANCH,
KERNEL_DEFCONFIG, and KERNEL_REPRODUCIBILITY_PATCHES. The default for
the above new variables is to the git.ti.com repository and how we manage
the kernel settings. The other kernel recipes that do something other than
how TI does it can simply override the variables.
This change will make it easier to perform the upstream testing that we
do on a nightly basis. Additionally, it will simplify the auto generation
of the patches to move the mainline (stable kernel) recipes since the
required patches will be all done in the same recipe.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
