Bump this recipe to add a change to help with GCC 14 compatibility in
the check-cc script used to check compiler flags before use.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump this recipe to add a change to help with GCC 14 compatibility in
the check-cc script used to check compiler flags before use.
Reset this back to the proper branches for kernel 6.1 since this recipe
is only being used in 6.6 bsp providers.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Download and install the cc33xx firmware and binaries
to be used with the cc33xx drivers.
FW Version: 1.7.0.120
Signed-off-by: Sabeeh Khan <sabeeh-khan@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
cc33calibrator is a tool provided by TI to manually control the
radio frontend of the cc33xx device. This tool can also be used
for production line testing of the radio.
Documentation for this tool is provided within the following link:
https://www.ti.com/tool/CC33XX-SOFTWARE
Signed-off-by: Sabeeh Khan <sabeeh-khan@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
cc33conf is a tool provided by TI to configure
cc33xx WLAN devices. It can be used to change
the RF parameters and other features of the target.
Documentation for this tool is provided within the following link:
https://www.ti.com/tool/CC33XX-SOFTWARE
Signed-off-by: Sabeeh Khan <sabeeh-khan@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Share the most commonality between the recipes, except:
* SRC_URI torvalds vs. linux-next
* SRCREV and PV
* Device Tree list vs. DT prefix
* SUMMARY
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The use of external metadata file to control RTOS binary firmware
integration has been deprecated some time ago. Remove it now.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adjust IMAGE_BOOT_FILES list as next BSP does not support all combinations
of SR1.0, HS-FS and HS-SE variants.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
For our upstream testing flow we have the need to have a "next" BSP for
configuring various settings based on building the latest kernel/uboot.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adjust IMAGE_BOOT_FILES list as mainline BSP does not support all combinations
of SR1.0, SR2.0, HS-FS and HS-SE variants.
Suggested-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adjust IMAGE_BOOT_FILES list as BB.org BSP does not support all combinations
of SR1.1, SR2.0, HS-FS and HS-SE variants, same as J721e EVM in mainline.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update am62xxsip-evm machine configuration to support
TI kernel 6.1 & ti-u-boot-2023.04
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
MACHINE_KERNEL_PR is a remnant of the early OE days and hasn't been
needed for quite some time. Let's finally remove it completely.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
BeaglePlay gains official support from latest TI lts-6.6 baseline, so set
it as the default. Other Beagle platforms will still use BB.org as default.
And these defaults can still be changed with TI_PREFERRED_BSP setting in a
distro config or by end user in the local.conf
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update all Beagle platform configurations to support multiple BSPs.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adjust IMAGE_BOOT_FILES list as some BSPs do not support all combinations
of SR1.1, SR2.0, HS-FS and HS-SE variants.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This adds a facility to define multiple supported BSPs with their own
preferences for individual components, as well as lets machine configs
specify conditional configurations for different BSPs.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the SRCREV to pick up some new binaries for AM62P. The allocation
patch for Chromium was not included for this device previously.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
In order to be able to switch between different kernel providers, as well
as different versions of kernel LTS (e.g. 6.1 vs. 6.6), let's re-organize
Device Tree lists as follows:
* Move all Beagle-specific DTBs and overlays into corresponding linux-bb.org
recipe for now, to be used when building beagleboard.org baseline
* Update KERNEL_DEVICETREE in the machine configs to only list what already
exists in the upstream/mainline kernel
* Update KERNEL_DEVICETREE_PREFIX to match the list when building TI baseline
With this change it is now very easy to switch the kernel between providers
supported by meta-ti - linux-ti-mainline, linux-ti-staging and linux-bb.org
Please note that 6.6 LTS has moved to "vendored" device tree layout even for
32-bit platforms, while BB.org still uses 6.1 LTS and flat DT layout.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Lift the common parts of the top level gitignore from oe-core and
meta-openembedded. This masks out temporary python files, intermediate
artifacts, and unclean patch leftovers (.orig, .rej, etc).
We're choosing to leave patches at the root of the project out of this
as maintainer preference.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As of commit [1] there will be a separate defconfig to build u-boot
for j721s2-evm and am68-sk.
Hence, introduce new yocto machine configs for am68-sk. This is done
through a new am68.inc file as the am68-sk platform does not support GP.
So j721s2-evm.inc is copied to am68.inc and updated accordingly.
[1]: https://source.denx.de/u-boot/u-boot/-/commit/a96be9b8c05ea835d27f7c9bae03279b8bd5dcf2
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the SRCREV to pick up rebuilt binaries. Upstream release notes:
Regenerate all binaries with a fix for exportable buffer allocations
that should improve Chromium compatibility.
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>
Update all of the optee components to the upstream 4.2.0 version.
While at it, remove the patches and fixups which are not needed anymore.
Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Now that are past the inital stages of our LTS migration, we can remove
the DEFAULT_PREFERENCE settings that prevented these recipes from being
the default.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
While we are working to finish our kernel migration 6.6, we are falling
aback to software rendering for platforms that do not currently have a
solution for GPU drivers (namely the boards that use SGX).
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
New features added require another increase to max_leb_cnt.
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add a recipe for mesa-pvr to use a newer branch based on mesa 23.2.1.
This branch does not currently contain SGX patches so it is also being
masked by the ltsprep branding to prevent regressing those devices
currently.
Please note that may run into sstate errors when switching to or away
from the ltsprep tag. Please issue a clean to mesa and
ti-img-rogue-umlibs if you get warnings from either package's
do_create_runtime_spdx step.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Locally overlay verbatim copies of mesa 22.3.5 patches from
oe-core/master, so we get whatever QoL patches from core relevant to the
current release.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Recipes for DDK 24.1, but lock them behind ltsprep tags because they
require device tree changes that do not work on the current default
kernel for this layer.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Reusing the j784s4.inc file presents problems as the am69-sk platform
does not support GP. So copy the j784s4.inc to am69.inc and update
accordingly.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Currently, the 6.1 kernel is the default. Removing the k3-am69-sk dtb
file only applies to the 6.6 kernel. Restoring this entry so that
current builds work until such time as the 6.1 kernel is removed from
the recipes.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Upstream driver expects Wave5 firmware to be named "wave521c_k3_codec_fw.bin".
Driver probe fails because this compatible isn't being found.
Signed-off-by: Brandon Brnich <b-brnich@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
LCPD Automation Script
Randolph Sapp
Sabeeh Khan
Denys Dmytriyenko
Ryan Eatmon
Chirag Shilwant
Aniket Limaye
Kamlesh Gurudasani
Beleswar Padhi
Brandon Brnich