| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.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>
|
| |
|
|
|
|
| |
Update to the latest release version.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
| |
|
|
| |
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
| |
|
|
|
|
|
|
| |
Update library to 0.6.3 as it adds support for AM62P
SoC.
Signed-off-by: Hari Nagalla <hnagalla@ti.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>
|
| |
|
|
|
|
|
| |
There are a number of issues in gallium when moving to LLVM 17. These
patches fix those compile issues.
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>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
TI_LINUX_FW_SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.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>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.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>
|
| |
|
|
|
|
|
|
| |
Updated the value(s) for:
PV
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
|
| |
Updated the value(s) for:
PV
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.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>
|
| |
|
|
|
|
| |
New features added require another increase to max_leb_cnt.
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>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.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>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
|
| |
|
|
|
|
|
| |
Updated the value(s) for:
TI_LINUX_FW_SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.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>
|
| |
|
|
|
|
|
| |
This definition is only needed in the "-k3r5" multiconfig files.
Signed-off-by: Andrew Davis <afd@ti.com>
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>
|
| |
|
|
|
|
|
| |
We do not use UIO anymore, remove these files.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
| |
|
|
|
|
|
|
|
| |
Update to latest release tag, i.e. v2.9
https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=d3e71ead6ea5bc3555ac90a446efec84ef6c6122
Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
