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>
Add support for ti-extras for am62xx-lp to control the kernel and u-boot
repos, branches, and srcrevs via the TI_EXTRAS variable in the local.conf
file.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Now that 2024.01 is official, the logo that am62xx-evm installs is
available in all versions of the repo that we point to. Move all of
that code out of the .bb files and into the u-boot-ti.inc file.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump SRCREV to include the following changes in UM and KM:
- Rebuild all releases with external memory wrap disabled due to
some incompatibility with certain Qt use cases.
- Add a watchdog change that prevents an occasional false
timeout when servicing long DM processes.
- Rely on snooping to perform certain cache operations and
results in decreased overhead for device -> cpu
communications.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
j722s is same GPU as am62p, need to add this into machine definition so
that Rogue driver gets included in the image.
Signed-off-by: Darren Etheridge <detheridge@ti.com>
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Fetch from the latest commit which has J722S support now.
Signed-off-by: Apurva Nandan <a-nandan@ti.com>
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Remove config files from /usr/share/jailhouse as they are not required.
Package only the cell files for respective devices and not all k3 files.
Update FILES:PN to use wildcard.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
RPM does not accept '-' as a character in the PR/version and fails with:
| error: line 4: Illegal char '-' (0x2d) in: Release: sgxrgx-54fd9d7dea098b6f11c2a244b0c6763dc8c5690c.1
The correct approach is to reference SRCPV and not SRCREV and also add it
to PV and not PR. But PV is used in the branch to fetch the sources and
cannot be modified, so use SRCPV in PR w/o any illegal characters.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
With the current implemetation is not possible to remove the '-k3r5'
customization using overrides like below and the '-k3r5' always stay there.
| TMPDIR:remove:k3r5 = "-k3r5"
| or
| TMPDIR:k3r5 = "${TOPDIR}/tmp"
This patch allows to build the core-image-minimal in oe-core master/nanbield
without any issue on a common TMPDIR folder just using the following:
| TI_COMMON_DEPLOY = "${DEPLOY_DIR}"
| TI_TMPDIR_APPEND = ""
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the BB.org kernel to the latest. Also update BeaglePlay device
tree list, as there were some renames and new additions.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
Update SRCREV for ti-jailhouse. All the patches which was being applied via yocto
have been moved to ti-jailhouse repo now. So remove the patches from SRC_URI and
files.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
A bug was introduced while trying to unify the Mesa version that is used
on SGX GPU's and Rogue GPU's. It manifests itself as an immediate segfault
whenever you try and run something like glmark2-es2-wayland or
weston-simple-egl on certain Rogue based platforms (specifically am62x).
Use different srcrev for Rogue GPU and SGX GPU platforms. The SGX GPU platforms
will use the latest commit. Rogue GPU platforms will use the last good working
commit before SGX related changes were introduced.
This change will be reverted once the issue is rootcaused and a common solution
is found for both Rogue and SGX based GPU platforms.
Signed-off-by: Darren Etheridge <detheridge@ti.com>
Signed-off-by: Anand Balagopalakrishnan <anandb@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Upgrade to v6.3.0 version.
This release adds resources for using AM243x & AM64x PRU cores with cores
running FreeRTOS:
* The RTOS Getting Started Labs
* Examples for using PRU GPIO and the broadside interface
* SORTE_G example (a custom networking interface)
Bug fixes:
* AM64x & AM65x header files, fix the names of extended sections to be in the
format of
ConstantsTableName_0x100
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
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>
This was a temporary class to help with the v5.10 to v6.1 kernel
migration, now that we have completed that, remove this class.
Suggested-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As all our supported kernels are above 5.10 and can now build this
module, remove this disable.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We support Linux v6.1 as our official version for Kirkstone. The older
kernel version was kept around during the transition to the newer version,
but we are past that now. Remove this old version.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The SRCREV is auto updated, but the PV still uses the old tag version,
update this to v0.3.
While here, we also now have a proper LICENSE file, use that.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
These are all useful for firmware recipes but some recipes did not have
them. For firmware including ti-linux-fw.inc let's add these all to
one spot and remove them from any recipe that did already have these.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
The common include ti-linux-fw.inc already includes setting this, no need
to set it in each recipe, remove that.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There is no compilation in this simple firmware recipe, no need for
these lines, remove them.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
These are common for all recipes that include ti-linux-fw.inc, add
it to this include file and remove from each recipe.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add support for ti-extras features for rt as it was added for non
rt kernel and u-boot earlier. It will also be accessible via the
TI_EXTRAS variable in the local.conf file.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Don't try to locate TI-TFL license within meta-ti-bsp relative to OE-Core
using COREBASE, as the directory structure of the layers is not guaranteed.
Instead, point to it relative to the recipe itself.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Minor rework of the TI include files used to override both SRCREV and
other settings in the optee recipes for TI SOC parts. The intent is to
make it more clear when we are changing SRCREVs versus changing other
items, and allow for sharing the SRCREV changes for optee-os-tadevkit
which should track the optee-os SRCREV.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the SRCREV to latest commit for both u-boot and linux
extras. Also update SRCREV for jailhouse branch for both psdk
linux and u-boot.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
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>
Move to the 23.2 release branch and bump SRCREV accordingly. This branch
has the proper implementation of the cache coherency fix along with some
other checks that address some system stability issues on Jacinto
devices.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump SRCREV to include some patches to better isolate SGX and PVR
components.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
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>
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>
Update both 32-bit and 64-bit configs to use the latest 6.1 Linux kernel
from beagleboard.org repository, which is based on ti-linux-kernel repo
used in linux-ti-staging, but with extra Beagle-specific features on top.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
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>
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>
Bump the SRCREV to include the required changes to build for SGX now.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump ti-sgx-ddk-um and ti-sgx-ddk-km to the new branch for Kirkstone and
mesa independent builds. This also sets up SGX to use the latest mesa
revision rogue uses.
Changelog:
- IMG Support has officially ended. This repo will not be getting
regular updates after this unless things are really broken.
- The Mesa patches which were previously being relicensed internally
were opened and combined with the unofficial rogue efforts on
freedesktop.
- Toolchains were upgraded and multiple warnings and issues were
addressed. Hardware recoveries work now, but there are still some
longstanding issues with SGX that remain to be addressed if further
resources are set aside for that.
- We moved to an lws-generic build target to avoid rebuilding external
components. As such, these external components must be patched as
needed. Libdrm is an example of this and the required patches can be
found in meta-ti.
Known bugs:
- Buffer allocations under Weston may misbehave
- GLSL macro redefinitions will cause errors regardless of whether or
not they are identical
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Makes ti-ipc firmware as default for main-r5f0_0 firmware softlink
The ti-eth-fw binaries are tested at the SDK level and should be
made default only at that level
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The main-r5f0_0 softlinks should be pointing to the ethfw binaries
instead of the mcu-r5f0_0
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This reverts commit cd13cafd65.
Some devices need ti-fs-stub-* firmware for the uboot aarch64 build
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Revert ebcf15bf0f :
"recipes-bsp:ti-sci-fw: Add k3r5 as COMPATIBLE_MACHINE"
Extend recipe to k3 machines too, to provide ti-fs-stub-* firmware
for u-boot aarch64 build.
Update do_deploy() to allow multiconfig builds for k3 machines
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Fixes the QA warnings about package contains reference to TMPDIR.
Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Currently the do_compile step fails if we try to implement UBOOT_CONFIG
in an attempt to build U-Boot with multiple R5 defconfigs.
This commit adds a condition to handle linking the UBOOT_BINARY if
UBOOT_CONFIG is used in place of UBOOT_MACHINE.
Signed-off-by: Garrett Giordano <ggiordano@phytec.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The previous patch is incorrectly accepted and released. This patch
applies the logic that was discussed on the mailing list.
- Create a new variable grouping for SPL_HS_MLO
- Update the install/deploy code to reference the new variables.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The common u-boot-ti.inc file still uses the old license checksum
from 2021 U-boot. There were formatting changes in the license text
between 2021 and 2023 and version-specific recipes had the license
checksum updated to the new value. Since there are no 2021 recipes
remaining, the new license checksum can be set in the common .inc
file generically.
Note: U-boot license hasn't changed and the same checksum is simply
being moved from the recipes to the common .inc file.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Preserve the directory structure of the deployed dm firmware so that one
can directly specify the deploy directory for binman based u-boot build.
Additionally, this makes it easier to preserve the same structure inside
the prebuilt-images directory of the tisdk-core-bundle for the same reason.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Deploy the sysfw binaries to the DEPLOYDIR, to be picked up by the
tisdk-core-bundle... for the prebuilt binaries directory
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The SPL binary built by u-boot for SD/MMC/eMMC media on HS platforms is
u-boot-spl_HS_MLO. Thanks to this fix, the binary is properly installed
and deployed.
Signed-off-by: Julien Panis <jpanis@baylibre.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This recipe only provides the sysfw binaries compiled for the r5
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
ti-sci-fw should be needed by the binman u-boot build only for the k3r5
machines and not for the k3 machines
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
OP-TEE OS provides a handful of TAs itself. While these are often meant
to be built-in, when they are not we should deploy them as part of the
OP-TEE OS package so they can be loaded at runtime.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Only move directories which haven't already been moved.
This prevents a build error should a subsequent bitbake execution
rerun do_install where the sources to 'mv' no longer exist.
| mv: cannot stat 'ti-img-rogue-umlibs/23.1.6404501/git/targetfs/am62_linux/lws-generic/release/lib/firmware': No such file or directory
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
multi_v7_defconfig that is used for legacy platforms enables
SMP by default.
Platforms like am335x and am473x are single core platforms that
doesnt need this option to be enabled.
This config cannot go in multi_v7_defconfig as well,
since there will be systems like am57x/dra7x or other community platforms
which can have multiple arm cores.
Adding the provision to disable SMP configuration for applicable platforms like
am335x and am437x.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updates SRCREV, PV, and BRANCH for armv7a targets and fixes
failure to mount /boot when using poky with systemd. The
kernel selected supports VFAT without initramfs as noted
here - https://lists.yoctoproject.org/g/meta-ti/message/16913
Removes defconfig patch setting LZMA, as the new kernel
already defaults to LZ4.
Tested by running `bitbake core-image-base` with this patchset,
and then booting a pair of Beaglebone Black devices from the
resulting image. Prior to the change, systemd boots to a
maintenance mode having failed to mount /boot. After the change,
the system boots normally and /boot is mounted.
Suggested-by: Robert Nelson <robertcnelson@gmail.com>
Signed-off-by: Anthony J. Martinez <anthony@ajmartinez.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Jacinto platforms use first R5 MCU core for DM firmware. When DM firmware was
split out into own recipe[1], ALTERNATIVE_TARGET entries got removed from
ti-rtos-firmware recipe, but corresponding ALTERNATIVE_LINK_NAME entries
remained, causing warnings. Clean up those now.
[1] https://git.yoctoproject.org/meta-ti/commit/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb?id=b21d29d94694ac49b97a1f4ba428c7d8cd6fb64a
Fixes these warnings:
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7-mcu-r5f0_0-fw or /usr/lib/firmware/j7-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7-mcu-r5f0_0-fw: /usr/lib/firmware/j7-mcu-r5f0_0-fw.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7-mcu-r5f0_0-fw == /usr/lib/firmware/j7-mcu-r5f0_0-fw
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7200-mcu-r5f0_0-fw or /usr/lib/firmware/j7200-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7200-mcu-r5f0_0-fw: /usr/lib/firmware/j7200-mcu-r5f0_0-fw.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7200-mcu-r5f0_0-fw == /usr/lib/firmware/j7200-mcu-r5f0_0-fw
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j721s2-mcu-r5f0_0-fw or /usr/lib/firmware/j721s2-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j721s2-mcu-r5f0_0-fw: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw == /usr/lib/firmware/j721s2-mcu-r5f0_0-fw
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j784s4-mcu-r5f0_0-fw or /usr/lib/firmware/j784s4-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j784s4-mcu-r5f0_0-fw: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw == /usr/lib/firmware/j784s4-mcu-r5f0_0-fw
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
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>
- 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>
- U-boot recipe in OE-Core supports out-of-tree config fragments that are passed via
SRC_URI and automatically merges all *.cfg files as fragments. This makes specifying
config fragments in the machine configuration a bit difficult. Hence, add a logic which
will ensure we handle u-boot config fragments using a new variable UBOOT_CONFIG_FRAGMENTS.
- The u-boot-mergeconfig.inc will allow us to build u-boot with list of config fragments
specified in UBOOT_CONFIG_FRAGMENTS along with the base defconfig mentioned in UBOOT_MACHINE.
- Include u-boot-mergeconfig.inc in u-boot-ti.inc
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
The SRCREV change corresponds to a commit that changes from make to
cmake for building k3conf, so we need to update the recipe as well.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
Update the QA checks done on the build artifacts to include [buildpaths] since
the PRU linker includes these paths in its output. This avoids build warnings
or errors of the type:
pru-icss-6.2.0-r1 do_package_qa: QA Issue: File /lib/firmware/pru/PRU_Halt.out in package pru-icss-halt contains reference to TMPDIR [buildpaths]
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
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>
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>
With the change to the vendored arch/arm/boot/dts directory, we need to
add support to the KERNEL_DEVICETREE_DTBMERGE to make it a search
pattern instead of a fixed list.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add in missing *-sec links pointing to signed files especially for
j784s4. Reformat file a little to make the groupings easier to
manage in the future when looking to see if -sec links are missing.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
commit 5f9be22839 ("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>
Bump the SRCREV for the umlibs and driver package to include some fixes
for Jacinto devices. These patches do the following:
- Fix virtual memory addressing
- Resolve an issue with APM and debug requests
- Attempt to resolve most of the cache coherency related issues on
Jacinto devices
- Introduce some extra cache maintenance operations in the kernel
module
It also introduces the following known issues:
- Visual artifacting on the second-to-last EGL/GLES context on BXS
based devices (J721S2/J784S4)
We're still working on that last one, but the stability improvements
make this worth while for now.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
Upgrade to v6.2.0 version.
This release supports Linux kernel 6.1.
The RPMsg library in previous versions of the PSSP will not work with
the PRU RPMsg drivers in Linux kernel 6.1.
Other changes in this version:
* Bug fixes:
- Getting Started Labs, fix "zero" command clearing too many bytes
- Include files, add a missing parentheses to pru_cfg, pru_ctrl, pru_ecap
* Update ReadMe files to point to the latest URLs
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update ti-rpmsg-char library to fix wrong rpmsg-ctrl
device ids observed when multiple remote procs are present
with multiple channels opened.
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The following patch was dropped from the SRC_URI one of my previous
graphics overhaul patches:
0001-compiler-support-OpenEmbedded-nodistro-internal-aarc.patch
Actually remove it from the source tree now that upstream is carrying
the equivalent to help enable other tools.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Upstream changed to not be so picky about compilers. Bump SRCREV so the
odd things using our recipes are happy again.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Edit the file paths so they point at files in the source directory
explicitly. For some reason shell glob were previously only respected by
some machines.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* rpmsg_client_sample is a test module and should not be autoloaded
* Both k3_r5 and k3_dsp remoteproc modules depend on virtio_rpmsg_bus
Cc: Denys Dmytriyenko <denys@ti.com>
Cc: Ryan Eatmon <reatmon@ti.com>
Cc: Praneeth Bajjuri <praneeth@ti.com>
Cc: Apurva Nandan <a-nandan@ti.com>
Cc: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Udit Kumar <u-kumar1@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Use RRECOMMENDS for components. Apparently I made an resolvable
dependency cycle that Yocto silently clipped. My best guess at the
culprit was: mesa-megadriver (RR) -> rogue-km (RR) -> rogue-um (RD) ->
libgles1-rogue (RD) -> mesa-megadriver
That killed the ti-img-rogue-umlibs recipe during do_rootfs. The rogue
GLES libs do depend on mesa-megadriver at runtime but I guess the UM
components should only really recommend the rogue GLES components be
present at runtime to make the cycle resolvable by opkg.
Fixes:
1705f6d3 (ti-img-rogue-umlibs: make all components optional, 2023-06-21)
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Now that driver support is added to support switch mode
for AM64, update recipes to package the switch firmware.
Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We need to package up new HSR firmware for am65x-sr2. Add dependencies
for them on the correct platforms.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bumping into the limitations of the binary_package class. This change
allows all rogue components to be optionally packaged without blowing
out the dependency chain.
Add a python function to fetch file paths from the FILE vars for each
component so we don't end up double tracking files. Add variables to
track component packages if things split up more later. Add a package
config string to set runtime dependencies and recommendations. Change
all logic to revolve around the PACKAGECONFIG instead of distro
features.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
When the ti-eth-fw recipe was split out from the ti-rtos-firmware recipe
we forgot to add it as a dependency.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
Early splash screen support for AM62x has been enabled in u-boot
and it requires bitmap tarball to be present in boot partition
as per the default environment settings done in u-boot [1].
Copy the ti logo bitmap tarball to boot partition of wic image in order
to enable out of box early display on AM62x.
[1] https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env
Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This firmware is shipped with the rest of ti-sysfw blobs, it shares
the same versions too and so should be simply bundled with the same.
This stub is also built into U-Boot and not loaded during kernel
runtime anymore, so remove the RDEPENDS in kernel.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
Well, flew a bit too close to the sun on that last patch. Apparently
there are a few hidden runtime dependencies on the API devlinks that
make things like EGL upset when they aren't present.
We may circle back to this at some point but for now we're fine shipping
the devlinks in the base API packages as these links don't step on any
other package.
Fixes: 1899f5ea (ti-img-rogue-umlibs: bump version and explicitly
package, 2023-06-01)
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Apply the ti_rt.config fragment to all the linux-ti-staging-rt-6.1
defconfigs so we can properly build the RT kernel for our devices.
Signed-off-by: Bryan Brattlof <bb@ti.com>
Acked-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
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>
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>
Update the ti-rpmsg-char library to 0.6.1 version to fix rpmsg_ctlr
id on v6.1 kernel when multiple channels are created.
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
U-Boot with binman will do the signing as these images are packaged.
Do not rename the DM image as the signed image.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
U-Boot with binman will do the signing as these images are packaged.
Remove signing steps here.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
U-Boot with binman will do the signing as these images are packaged.
Remove signing steps here.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
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>
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>
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>
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>
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>
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>
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>
This converts ti-sci-fw into a standard firmware provider package. We do
not need to do anything additional here with that firmware as U-Boot now
does that for us with binman.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This will no longer build after we switch away from k3-image-gen. Remove
this version and make 2023.04 the default.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This will no longer build after we switch away from k3-image-gen. Remove
this version until it can be rebased on the latest U-Boot with binman
support. For now switch current users of this over to u-boot-ti v2021.01.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
K3-image-gen is going away and we don't do SRCIPK packages like this
anymore anyway. Remove this recipe.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the version and explicitly package all Khronos APIs separately.
This should be nice for those folks that want a headless opencl system
for tinkering and such.
This version includes experimental GEM support (for applications like
Chromium that like to poke at the render node) and a new Vulkan ICD
loader interface for better support with the Vulkan ICD loaders present
in Yocto.
This lifts a method from mesa used to force a common naming convention
for Vulkan, OpenCL, and OpenGLES libs to make things a little easier to
follow. Without it the target package names get scrambled based on the
shared object name.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Move recipes to new subdir since we offer more than just libgles now.
Reusing the naming convention of the subdirectory used for the km
components for now.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This reverts commit a4f0f492f1.
The file was updated in upstream oe-core for kirkstone. This commit is
no longer needed.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This reverts commit bdc8e7c9b5.
The file was updated in upstream oe-core for kirkstone. This commit is
no longer needed.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There is only one user of these include files, expand the files inside
the one user and remove the includes.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This file should be whittled away over time, remove currently unused
paths to help us take inventory of what remains.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Like with master, move the actual TI-specific changes into corresponding
include files that are only activated for ti-soc derived platforms.
Since include files are already guarded and only activated for ti-soc
platforms, no need to use such override again.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Cleanup the J* APM patch a little. Apparently I could have stood to read
the docs a little more. Found some better runtime pm functions and also
discovered something new about the power island definition.
Notes from upstream:
- Add the CCB coherency HACK from DDK 1.15 to improve stability
on J* devices
- Fix power island support on J* devices
- Use better APM calls so user modification to power domains
don't cause the device to enter a bad state
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the ti-rpmsg-char library to 0.6.0 version that enables the
support for 6.1 kernel.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Set the variables needed to put the DTBs into the same vendored
directory structure as they are in the kernel.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Change over to using the kernel_devicetree_vendor_dtb.bbclass to have
the DTBs installed into the same vendored subdirectory that is in the
kernel. Setting the variables comes in a follow on patch.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There is a series of patches [1] [2] [3] that were submitted to oe-core
master that have gone through some iterations. It has partially stalled
in the upstreaming process but we need the effective changes to continue
our LTS plans for u-boot 2023.
This backports the effective changes of that patch against the kirkstone
version of the two classes, but renames them to make it obvious that we
are overriding them. This should be a temporary change as we expect the
changes to be backported to oe-core kirkstone once the stall is gone.
This patch will be removed once it makes it into oe-core kirkstone.
[1] https://lists.openembedded.org/g/openembedded-core/message/180753
[2] https://lists.openembedded.org/g/openembedded-core/message/181190
[2] https://lists.openembedded.org/g/openembedded-core/message/181191
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Rename the .wks to .wks.in so the EFI_PROVIDER variable is expanded
properly. We only ever set a soft recommendation for GRUB. If anyone
attempted to change that previously it was ignored (for more than just
the reason here, but that's out of my control).
Add a timeout for the bootloader menu. Currently setting it to 3
seconds.
Remove the read only flag on the rootfs. Not sure why that was there.
Signed-off-by: Randolph Sapp <rs@ti.com>
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.
