Update SRCREV for Jailhouse-enabled U-Boot and Linux kernel
and ti-jailhouse for the bsp-ti-6_18
Changes include:
- u-boot/ti-extras.inc: Update to latest SRCREV
- linux/ti-extras.inc: Update to latest SRCREV
- linux/ti-extras-rt.inc: Update to latest SRCREV
- jailhouse/ti-jailhouse: Update to latest SRCREV
Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add -ffile-prefix-map flags to KCFLAGS to remove build path
references from kernel module compilation, ensuring reproducible
builds and preventing absolute path leakage in binaries.
inherit module-base kernel-module-split for building kernel modules
move V=1 into EXTRA_OEMAKE and remove overriding do_compile()
This resolves buildpaths QA warnings during packaging.
Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Inmate binaries are bare-metal applications without standard debug
symbols that can be meaningfully split. Inhibit debug package
creation to avoid unnecessary packaging overhead and potential
QA warnings.
Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update JH_RAMFS_IMAGE references to use correct .cpio
extension instead of .rootfs.cpio to match current image
naming convention
Signed-off-by: Mahammed Sadik Shaik <s-sadik@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As am57xx.inc is now the only user of omap-a15.inc, merge the content of
omap-a15.inc into am57xx.inc and remove omap-a15.inc. As we no longer have
this common include, also remove "omap-a15" and use "am57xx" in its place.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As AM57xx already defined both "dra7xx" and "am57xx" as SOC_FAMILY the
AM57xx was effectively a superset MACHINE. Although not all features of
AM57xx are needed for DRA7xx, make DRA7xx-EVM use the AM57xx definition.
This allows us to still support DRA7xx as the only differences that
impact device function are the selection of U-Boot defconfig, DTBs, and
OPTEE, all handled by the MACHINE conf file which is left unchanged.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Major Updates since 1.7.0.120:
- Added WPA1 support
- Addressed many stability issues in WiFi and BLE
- Enabled thermal protection for operation up to 105C
SHA1 checksum:
c364c4d89802bcac769ee6eebc08ae1c4ef5a205 cc33xx_2nd_loader.bin
b39bfac65e0300e81dfcfee7301e07b4289df448 cc33xx-conf.bin
821fa40f608e350baa9e4cdfea6719bf469c5220 cc33xx_fw.bin
Signed-off-by: Sabeeh Khan <sabeeh-khan@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This recipe builds and runs fine on both DRA7x and AM57x machines.
The COMPATIBLE_MACHINE is set to just DRA7x, but this was okay as AM57x
machines also set themselves as DRA7x family devices. The issue is then
we cannot then differentiate between packages that are actually DRA7x-
only and those that just use that family to mean both machine types. To
fix this when we mean both are allowed use "omap-a15" as done here.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This recipe builds and runs fine on both DRA7x and AM57x machines.
The COMPATIBLE_MACHINE is set to just DRA7x, but this was okay as AM57x
machines also set themselves as DRA7x family devices. The issue is then
we cannot then differentiate between packages that are actually DRA7x-
only and those that just use that family to mean both machine types. To
fix this when we mean both are allowed use "omap-a15" as done here.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This recipe is already only compatible with the DRA7xx machine, so
no need to set PLATFORM based on the only possibility. This then
allows us to directly set the compile flags for the same. And now
that the package does not change based on the machine, remove the
PACKAGE_ARCH line.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This recipe is already only compatible with the DRA7xx machine, so
no need to set PLATFORM based on the only possibility. This then
allows us to directly set the compile flags for the same. And now
that the package does not change based on the machine, remove the
PACKAGE_ARCH line.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This was only ever used as part of the DSP firmware for OpenCL dispatch.
That is all gone now, so remove this leftover dependency.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The messageq IPC firmware example for AM57xx SoCs is available in
ti-linux-firmware repository. Add a recipe to package the prebuilt
messageq firmware into the rootfs.
Additionally, make sure the firmware for IPU1 rproc is copied into boot
partition by updating the dependency in omap-a15 machine conf to the
above recipe. This is needed for Early Boot use cases and gets rid of
dependency on meta-ti-extras layer.
There is no need to deploy the vayu IPC firmware anymore. Remove
the deploy task from ti-ipc-rtos recipe.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add a recipe to build the Application Host (for A15 core) to demonstrate
IPC with remote processors through messageq firmware. Also package this
in the /usr/bin directory for testing IPC. This recipe only builds the
app_host, and the firmwares are available in ti-linux-firmware
repository.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
update to PSSP release v6.5.0. This release is compatible to linux
v6.12 and other fixes for RP message size.
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
When specifying multiple git repos in the SRC_URI and you want the
"secondary" repositories to appear within the directory structure of the
primary repository, then we need to make sure that the destsuffix is
correct. With the change to calculating the value of S to use
BB_GIT_DEFAULT_DESTSUFFIX, we need to make sure that the destsuffix is
based on that variable as well.
Also, update the paths for S to be within new source location.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
If a recipe is fetching an entire git repo and then just building a
single dir, then we need to update S to lock into the sub directory.
Easiest fix is to simply append the subdir to whatever the system wants
to set S to by default.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Removing all the S = ${WORKDIR}/git assignments works because BB_GIT_DEFAULT_DESTSUFFIX
is set to match S from bitbake.conf (which itself is set to match typical tarball
releases).
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There is no need to have two assignments; also setting S from
UNPACKDIR (and not vice versa) is more logical as unpack
task comes first, and tasks that come after unpack use S to access
unpack results.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update all layers with the new Yocto release, fixing the current build
error:
ERROR: Layer meta-ti-bsp is not compatible with the core layer which
only supports these series: whinlatter (layer is compatible with styhead
walnascar)
Signed-off-by: Hiago De Franco <hiago.franco@toradex.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Every recipe should have a SUMMARY and that can only be 72 characters at
most. Some of these recipes had DESCRIPTIONS and not SUMMARY, some were
missing the SUMMARY, and some had slightly too long values for the SUMMARY.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This is an old code base and hasn't been updated in a very long
time. It now fails to compile with gcc-15 (C23 standard). Force
compilation with GNU/C11 standard instead.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since OE bitbake commit 24772dd2ae6c ("parse/ConfHandler: Add warning for
deprecated whitespace usage"), the current build generates the following
warning (as example):
| WARNING: ...meta-ti/meta-ti-bsp/recipes-ti/ipc/ti-ipc_git.bb:
| meta-ti/meta-ti-bsp/recipes-ti/ipc/ti-ipc_git.bb:2
| has a lack of whitespace around the assignment:
| 'HOMEPAGE="http://processors.wiki.ti.com/index.php/Category:IPC"'
Fix all the warnings.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
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>
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>
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 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>
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>
As the patch that added these states, this is an ugly hack, the issues
involved are fixed and no longer relevant, remove this.
Signed-off-by: Andrew Davis <afd@ti.com>
We use the makefile shipped with the firmware to deploy the firmware
instead of just manually moving it in the install step. But the makefile
doesn't do the right thing, so we also modify the makefile. Skip all
this and just move the firmware ourselves.
Signed-off-by: Andrew Davis <afd@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 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>
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>
The next Yocto Project release is called walnascar and OE-Core master branch
is now marked accordingly. Add layer compatibility with walnascar.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There was a change to the return value for a function pointer in the
kernel v6.11. This patch adapts the module to the kernel change.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Last user was dspdce-fw which is removed. Remove this now unused
support library.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This was an attempt to run the DCE server firmware on the DSP instead
of on the IPU M4 cores. Not widely used and not used at all anymore,
remove the firmware for this.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Remove openmp-rtos component as deprecated and not maintained.
This used to provide OpenMP DSP runtime components for legacy devices.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
omapzoom has been down since a long time. Point the repository to the
mirror in git.ti.com
Reported-by: Daniel Schultz <d.schultz@phytec.de>
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
A compile error has apperaed when building againt the v6.10 kernel.
git/debugss_module/debugss-mod/debugss_kmodule.c:1149:34: error: array type has incomplete element type 'struct of_device_id'
1149 | static const struct of_device_id dra7xx_debugss_of_match[] = {
| ^~~~~~~~~~~~~~~~~~~~~~~
The easy fix is just to add an include for the header that defines the
missing struct.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Mahammed Sadik Shaik
Ryan Eatmon
Andrew Davis
Sabeeh Khan
Beleswar Padhi
Hari Nagalla
Hiago De Franco
Denys Dmytriyenko
Max Krummenacher
Paresh Bhagat
Aniket Limaye
Chirag Shilwant
Nishanth Menon