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>
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>
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>
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>
We got a bit more time to do a proper migration this time. A discovery
period to see what actually works and boy, it wasn't much.
This update resolves issues with:
- Macro redefinition
- Sparse NPOT texture allocations
- vec4 reductions
- Mesa image extensions
- Buffer allocations under weston
- Devices with both a RENDER and PRIMARY display node
- Underprivileged users being unable to allocate buffers
- Removed call to drm_map_legacy
- Replace deprecated kernel calls
- Fix some cache attributes for userspace allocations
- About 40 other various errors and warnings
This core was never fully GLES2 conformant. In fact, if you try to run
cts on any of the older releases you'll find yourself in a hardware
recovery loop pretty quickly. We've gotten it to about 94.2% conformance
with these patches.
There are still dragons here, but they are at least a little more
manageable.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Update linux-bb.org to 6.1.80 for both 32 and 64 bit platforms
* Update DTB/DTBO lists to include latest renames and additions
* Re-enable vendored DTB layout by default
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Separate FAT boot partition holds SPL, SYSFW and U-boot images, while
rootfs places kernel images and DTBs into /boot directory. So it is not
desirable to mount boot FAT partition into /boot directory of the rootfs
and shadow its original content - adjust corresponding entry in wic
templates.
While at it, remove unused ondisk parameter when using use-uuid, which
takes precedence and is more flexible.
Note: boot FAT partition will be automounted at /run/media/boot-mmcblk0p1/
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Reviewed-by: Jonathan Cormier <jcormier@criticallink.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This upgrade contains the following changes:
* updated hostapd path in ap_start.sh
* ap_stop.sh removes wlan1 interface
* hostapd.conf updated to work seamlessly with hostapd 2.10
Signed-off-by: Sabeeh Khan <sabeeh-khan@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
It is useful to have U-boot initial environment deployed for future
reference or to initialize environment files as part of the build.
In multiconfig setup, such as TI K3 platforms, building U-boot
multiple times for Cortex-R5 and Cortex-A53 cores results in file
conflicts when deploying under the same name. To avoid that, those
initial-env files were removed at the end of the do_deploy task.
But it is better to only remove them for k3r5 multiconfig, since
that only builds SPL and saved env doesn't make much sense, but
preserve and deploy initial-env for the main machine multiconfig.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
am69 and am68 sk boards supports V3Link cameras interfaced via V3Link
camera fusion board. Refer to
commit b7a97b1b (conf: machine: am62axx: Pick overlays for V3Link cameras)
for details
Signed-off-by: Rahul T R <r-ravikumar@ti.com>
Acked-by: Jai Luthra <j-luthra@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
j722s-evm supports capture from fpdlink cams via fpdlink fusion1 board
or V3Link camera fusion board. So package fpdlink camera overlays
Signed-off-by: Rahul T R <r-ravikumar@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update SRCREV for jailhouse recipe which will add changes for Out of Box
demo and also a new application to test whether the linux inmate cell has
crashed or not.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Acked-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Latest ti-u-boot will be supporting HSSE1.0 and HSFS1.0 versions of the
j7200 soc through the binman dts nodes. Add support in yocto to package
the created binaries in the wic images.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Latest ti-u-boot will be supporting HSSE2.0 and HSFS1.1 versions of the
j721e soc through the binman dts nodes. Add support in yocto to package
the created binaries in the wic images.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
update from 0.6.4 to 0.6.6.
This update brings the following fixes from ti-rpmsg-char repo.
55a6f40 remove ti.ipc4.ping-pong reference
8892e57 lib: fix data type build warnings
7c2ab48 lib: fix build warnings
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Acked-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The new V3Link camera fusion board [1] comes with a CSI to FPDLink
serializer board, which allows interfacing multiple 22-pin FFC
compatible sensors with SK-AM62A.
Currently overlays for interfacing IMX219 sensor with V3Link are built
as part of the TI linux kernel, so pick these in the BSP filesystem.
[1]: https://www.arducam.com/fpd-link-3-cameras/
Signed-off-by: Jai Luthra <j-luthra@ti.com>
Acked-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Stop using UBOOT_LOCALVERSION, and copy what is done in the kernel recipe. This
allows us to set the correct SHA into the version string even if AUTOREV is used
since SRCPV is no longer set in oe-core.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The use of KERNEL_LOCALVERSION for controlling the kernel version has
changed recently. Placing the value of KERNEL_LOCALVERSION in
.scmversion was causing it to duplicate the string in the final version.
Instead, drop KERNEL_LOCALVERSION to just identify that it comes from
TI, and that it is an RT kernel. Additionally, place the commit sha for
the kernel into the .scmversion file explicitly to be both backward and
forward compatible.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This patch moves the jailhouse recipe general variables to a
ti-jailhouse.inc file along with fetch and compile task.
Jailhouse repo also contains some demo applications which can
be packaged alone in filesytem and does not require packaging
jailhouse module, firmware and tool.
So add a new recipe jailhouse-inmate which can be used to only
package those demos. The existing jailhouse recipe will contain
variables and other dependencies needed for do_install task for
jailhouse module, tools, demos etc. The do_install of jailhouse
inmate recipe will only package demo applications.
This new recipe(jailhouse-inmate) will be added to a new image
in meta-arago. The new image will be used for jailhouse second
linux instance or cell.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the SRCREV to include a fix for suspend and resume. Unfortunately
version 23.3 includes a partial rework of the power management subsystem
that breaks OS active power management. Apparently it also broke OS
suspend/resume by incorrectly setting OS state before the device state
was updated and trying to fall back on device default behavior in
certain paths.
This fixes OS suspend/resume but unfortunately full OS APM will need a
little more work.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Update linux-bb.org to 6.1.69 for both 32 and 64 bit platforms
* Update u-boot-bb.org to the latest 2023.04 based on SDK 9.1 release
* Update DTB/DTBO lists to include latest renames and additions
Note: all changes are in a single commit for bisectability
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The current master has the support for power off functionality, update
to that.
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update all OP-TEE components to 4.1 tag. OP-TEE examples are already in
4.1 tag.
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add TI logo image as bootsplash image file for AM62P and install it in
boot directory from where u-boot can read from and display during
boot-up time.
Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
Acked-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Migrate to version 23.3.6512818, this includes the stability updates
released in 23.2 as well as some additional modifications to help with
userspace application support, namely Chromium.
We're also dropping the x11 window system extensions from the Vulkan
libraries for now. Ideally, both x11 and wayland extensions will be
provided by mesa's vulkan-wsi-layer in the future, but currently x11
isn't supported and this just added extra complexity to the package in
Yocto.
Signed-off-by: Randolph Sapp <rs@ti.com>
Tested-by: Darren Etheridge <detheridge@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the SRCREV to include some useful patches that:
- Fix the ROGUE segfault issue introduced by SGX (this was what
the old conditional logic was addressing)
- Fix destruction of event queue with proxies still attached
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
