On 6/19/2024 10:22 PM, Sabeeh Khan via lists.yoctoproject.org wrote:
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
---
.../recipes-bsp/cc33xx-fw/cc33xx-fw_git.bb| 26 +++
1
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
---
meta-ti-bsp/conf/machine/include/j722s.inc | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
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
---
meta-ti-bsp/conf/machine/include/ti-bsp.inc | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff
On 6/17/2024 11:11 AM, Denys Dmytriyenko wrote:
On Mon, Jun 17, 2024 at 07:25:32PM +0530, Chirag Shilwant via
lists.yoctoproject.org wrote:
Update am62xxsip-evm machine configuration to support
TI kernel 6.1 & ti-u-boot-2023.04
Signed-off-by: Chirag Shilwant
---
v2: In commit message,
On 6/17/2024 3:33 AM, Chirag Shilwant wrote:
Update am62xxsip-evm machine configuration to support
TI kernel 6.1 & ti-u-boot-2024.04
uboot is 2023.04... -^
Signed-off-by: Chirag Shilwant
---
meta-ti-bsp/conf/machine/am62xxsip-evm-k3r5.conf | 4
The offending patch has been reverted and pushed to master. You should
be able re-enable the nightly testing from the perspective of this issue.
On 6/14/2024 11:17 AM, Denys Dmytriyenko wrote:
Thanks Alexandre
And sorry this has taken longer than expected to get it fixed.
As I explained
On 6/14/2024 1:55 PM, Denys Dmytriyenko wrote:
On Fri, Jun 14, 2024 at 12:34:23PM -0400, Denys Dmytriyenko wrote:
On Thu, Jun 13, 2024 at 04:18:16PM -0500, Ryan Eatmon wrote:
On 6/13/2024 12:22 PM, Denys Dmytriyenko wrote:
From: Denys Dmytriyenko
This adds a facility to define multiple
On 6/13/2024 12:22 PM, Denys Dmytriyenko wrote:
From: Denys Dmytriyenko
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
On 6/13/2024 2:47 PM, Denys Dmytriyenko wrote:
On Thu, Jun 13, 2024 at 02:29:34PM -0500, Ryan Eatmon wrote:
On 6/13/2024 12:22 PM, Denys Dmytriyenko wrote:
From: Denys Dmytriyenko
This adds a facility to define multiple supported BSPs with their own
preferences for individual components,
On 6/13/2024 12:22 PM, Denys Dmytriyenko wrote:
From: Denys Dmytriyenko
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
On 6/6/2024 3:16 PM, Denys Dmytriyenko wrote:
Oops, this is meant for master/scarthgap - forgot the branch tag, but sent the
updated version.
I was just going to ask...
On Thu, Jun 06, 2024 at 03:47:56PM -0400, Denys Dmytriyenko wrote:
From: Denys Dmytriyenko
In order to be able to
On 6/5/2024 11:07 AM, Randolph Sapp wrote:
On Tue Jun 4, 2024 at 5:15 PM CDT, Ryan Eatmon wrote:
On 6/4/2024 2:12 PM, Denys Dmytriyenko wrote:
On Mon, Jun 03, 2024 at 02:55:15PM -0500, r...@ti.com wrote:
From: Randolph Sapp
Lift the common parts of the top level gitignore from oe-core
A newly enabled check in master is causing errors with this package:
ERROR: QA Issue: Architecture did not match (ARM, expected x86-64)
Adding arch to the INSANE_SKIP variable disables that check for this
recipe.
Suggested-by: Denys Dmytriyenko
Signed-off-by: Ryan Eatmon
---
On 6/4/2024 2:12 PM, Denys Dmytriyenko wrote:
On Mon, Jun 03, 2024 at 02:55:15PM -0500, r...@ti.com wrote:
From: Randolph Sapp
Lift the common parts of the top level gitignore from oe-core and
meta-openembedded. This masks out temporary python files, intermediate
artifacts, and patches at
For recipes that have file:// in SRC_URI, the files are placed into
WORKDIR. Moving forward [1], that directory will be UNPACKDIR and
eventually move to somewhere other than WORKDIR. So update all
references to WORKDIR that are looking for these file to use UNPACKDIR
instead.
[1]
One of the changes in gcc v14 is making implicit-function-declaration an
error. For some older software packages the easiest fix is to add
-fpermissive to the compile line.
Signed-off-by: Ryan Eatmon
---
meta-ti-extras/recipes-devtools/gdbc6x/gdbc6x_git.bb | 2 +-
1 file changed, 1
Ignore this. I didn't realize this patch was still in the directory
when I sent all the patches in...
On 5/31/2024 2:45 PM, Ryan Eatmon via lists.yoctoproject.org wrote:
While we are working to finish our kernel migration 6.6, we are falling
aback to software rendering for platforms that do
Ignore this. I didn't realize this patch was still in the directory
when I sent all the patches in...
On 5/31/2024 2:45 PM, Ryan Eatmon via lists.yoctoproject.org wrote:
Now that are past the inital stages of our LTS migration, we can remove
the DEFAULT_PREFERENCE settings that prevented
For recipes that have file:// in SRC_URI, the files are placed into
WORKDIR. Moving forward [1], that directory will be UNPACKDIR and
eventually move to somewhere other than WORKDIR. So update all
references to WORKDIR that are looking for these file to use UNPACKDIR
instead.
[1]
These are the patches needed to support the change to UNPACKDIR. I am
not going to list what changed from v2 to v3 because it was pretty much
a full throw out and redo once things solidified, but I still wanted to
call this v3 since it is my third attempt.
Ryan Eatmon (2):
recipes: Update to
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
---
meta-ti-bsp/conf/machine/include/am65xx.inc | 2 +-
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
---
.../powervr-drivers/ti-img-rogue-driver_24.1.6554834.bb | 2 --
Follow along with the corresponding patch in upstream. [1]
[1]
https://git.openembedded.org/openembedded-core/commit/?h=master-next=d9328e3b0b062f0621de3d114584b44f384a1c02
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/recipes-bsp/vis-fw/vis_01.50.07.15.bb | 3 ++-
1 file changed, 2
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
---
.../powervr-drivers/ti-img-rogue-driver_24.1.6554834.bb | 2 --
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
---
meta-ti-bsp/conf/machine/include/am65xx.inc | 2 +-
On 5/22/2024 8:36 AM, Chirag Shilwant wrote:
+ Bryan for providing more details on the u-boot defconfig name change
for am62xx-lp-evm
On 22/05/24 18:46, Ryan Eatmon wrote:
This changes make scarthgap and master incompatible with the current
default for uboot... 2024.04 is not the default
On 5/22/2024 8:00 AM, Chirag Shilwant wrote:
Modify the U-Boot defconfig names for A53 and R5
machine configurations based on ti-u-boot-2024.04 [1]
[1]:
https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2024.04=781b6a4a9ffde2428484d5c061b80e6c192b2049
Signed-off-by: Chirag
This changes make scarthgap and master incompatible with the current
default for uboot... 2024.04 is not the default yet. Why was this
change made in uboot?
We cannot accept this change until we default to 2024.04.
On 5/22/2024 8:00 AM, Chirag Shilwant wrote:
Modify the U-Boot defconfig
On 5/16/2024 9:04 PM, christophercordahi via lists.yoctoproject.org wrote:
Only 28 M of the necessary 97 M are downloaded using the command
wget
http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/3_55_02_22/exports/xdccore/xdctools_3_55_02_22_core_linux.zip
There’s a
On 5/8/2024 3:42 PM, Randolph Sapp wrote:
On Thu May 2, 2024 at 2:45 PM CDT, Denys Dmytriyenko wrote:
Can you make it a diff please? As shown previously, that helps with review and
allows spotting issues much easier.
[snip]
Yeah, sorry about the delay on this. Just got back to Dallas.
Since S = "${WORKDIR}" is the default setting for S it is not needed to
override S in this way.
Signed-off-by: Ryan Eatmon
---
v2: After reviewing what all was being changed, I decided to make
smaller changes for this patch series while the whole UNPACKDIR
change is worked out upstream.
This is a corresponding patch to match one from Richard Purdie in
oe-core. [1]
Where recipes use S = ${WORKDIR}, ensure they are referencing ${S} correctly
to access files as soon we want to stop doing this in WORKDIR at which point
they would break unless corrected.
[1]
Since S = "${WORKDIR}" is the default setting for S it is not needed to
override S in this way.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/recipes-bsp/vis-fw/vis_01.50.07.15.bb | 2 --
1 file changed, 2 deletions(-)
diff --git a/meta-ti-bsp/recipes-bsp/vis-fw/vis_01.50.07.15.bb
This is a correspnding patch to match one from Richard Purdie in
oe-core. [1]
Since we want to be able to stop unpacking to WORKDIR, correct the WORKDIR
references in recipe do_compile/do_install tasks to use UNPACKDIR in the
appropraite places instead.
[1]
meta-arm has created the scarthgap branch.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/README| 2 +-
meta-ti-extras/README | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-ti-bsp/README b/meta-ti-bsp/README
index 4c86c8fb..70c40d4e 100644
--- a/meta-ti-bsp/README
On 4/30/2024 3:47 PM, Denys Dmytriyenko wrote:
On Tue, Apr 30, 2024 at 02:58:11PM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
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.
Any
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
---
v2: Fix commit message.
meta-ti-bsp/conf/machine/am69-sk.conf | 2 +-
Reusing the j784s4.inc file presents problems as the am69-sk platform
does not support GP. So copy the j784s4.inc to am699.inc and update
accordingly.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/conf/machine/am69-sk.conf | 2 +-
meta-ti-bsp/conf/machine/include/am69.inc | 19
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
---
meta-ti-bsp/conf/machine/j784s4-evm.conf |
On 4/29/2024 8:51 AM, Limaye, Aniket wrote:
On 4/26/2024 1:06 AM, Ryan Eatmon wrote:
On 4/24/2024 10:59 PM, Limaye, Aniket wrote:
On 4/24/2024 6:53 PM, Ryan Eatmon wrote:
We have consistently named the machines with -evm and not -sk. Is
there a good reason to not name this am69-evm?
On 4/26/2024 2:01 PM, Denys Dmytriyenko wrote:
On Thu, Apr 25, 2024 at 02:36:10PM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
On 4/24/2024 10:59 PM, Limaye, Aniket wrote:
On 4/24/2024 6:53 PM, Ryan Eatmon wrote:
We have consistently named the machines with -evm and not -sk
Yes. I was just finishing up another thing and about to get back to this.
On 4/26/2024 2:02 PM, Denys Dmytriyenko wrote:
Ryan,
Will you be able to pick up v2 of this? Thanks.
On Wed, Apr 24, 2024 at 12:46:48PM -1000, Jon Cormier wrote:
Reviewed-by: Jonathan Cormier
On Wed, Apr 24,
The new kernel directory stucture for the DTBs is causing problems when
assembing the image files. It produces errors like this:
output: install: cannot stat 'deploy-ti/images/-evm/omap/.dtb': No such
file or directory
or
output: install: cannot stat
We missed that the KERNEL_DEVICETREE should have been updated for the
32bit platforms with the change in linux-ti-mainline to v6.6. The new
directory structure under arch/arm/boot/dts is in effect for that
version.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/conf/machine/am57xx-evm.conf | 14
On 4/24/2024 10:59 PM, Limaye, Aniket wrote:
On 4/24/2024 6:53 PM, Ryan Eatmon wrote:
We have consistently named the machines with -evm and not -sk. Is
there a good reason to not name this am69-evm?
Well this is just following the naming convention that got accepted in
u-boot:
We have consistently named the machines with -evm and not -sk. Is there
a good reason to not name this am69-evm?
On 4/24/2024 3:35 AM, Aniket Limaye wrote:
From: Beleswar Padhi
As of commits [1] and [2] in ti-u-boot-2024.04 and upstream respectively
there is a separate defconfig to
Update LAYERSERIES_COMPAT to remove EOL branches and add future styhead.
Signed-off-by: Ryan Eatmon
---
v2: Add missing nanbield in meta-ti-extras/conf/layer.conf
meta-ti-bsp/conf/layer.conf| 2 +-
meta-ti-extras/conf/layer.conf | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
Since we do not directly support the non-LTS branches, customers are
forced to rely on master for projects that make use of those branches.
We are not going to start creating branches for all of the non-LTS
releases, but we can do a better job of having master continue to
support the branches
Add recipe for yamllint. There is an upcoming change in u-boot where
the binman tool is now configured to call yamllint to verify the configs
during compile time.
There was a previous patch a year ago from Trevor Woerner that never
made it into oe-core. This patch is a reworking of his patch
In an attempt to try and better support non-LTS branches, we need to do
a better job at not removing temporary patches too soon from master.
This TODO file should allow us to better schedule the time when the
patches can be safely removed.
Signed-off-by: Ryan Eatmon
---
TODO | 9 +
1
On 4/17/2024 1:35 PM, Ryan Eatmon via lists.yoctoproject.org wrote:
On 4/17/2024 11:30 AM, Denys Dmytriyenko wrote:
On Wed, Apr 17, 2024 at 11:11:29AM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
Update LAYERSERIES_COMPAT to remove EOL branches and add future styhead.
Signed-off
On 4/17/2024 11:30 AM, Denys Dmytriyenko wrote:
On Wed, Apr 17, 2024 at 11:11:29AM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
Update LAYERSERIES_COMPAT to remove EOL branches and add future styhead.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/conf/layer.conf| 2 +-
meta-ti
Since we do not directly support the non-LTS branches, customers are
forced to rely on master for projects that make use of those branches.
We are not going to start creating branches for all of the non-LTS
releases, but we can do a better job of having master continue to
support the branches
In an attempt to try and better support non-LTS branches, we need to do
a better job at not removing temporary patches too soon from master.
This TODO file should allow us to better schedule the time when the
patches can be safely removed.
Signed-off-by: Ryan Eatmon
---
TODO | 9 +
1
Add recipe for yamllint. There is an upcoming change in u-boot where
the binman tool is now configured to call yamllint to verify the configs
during compile time.
There was a previous patch a year ago from Trevor Woerner that never
made it into oe-core. This patch is a reworking of his patch
Update LAYERSERIES_COMPAT to remove EOL branches and add future styhead.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/conf/layer.conf| 2 +-
meta-ti-extras/conf/layer.conf | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-ti-bsp/conf/layer.conf
Our CICD script inadvertently added the SRCPV back into the recipes.
The script has been fixed, so removing the variable once again.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.1.bb | 2 +-
meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.6.bb | 2
Our CICD script inadvertently added the SRCPV back into the recipes.
The script has been fixed, so removing the variable once again.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.1.bb | 2 +-
meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.6.bb | 2
Update LAYERSERIES_COMPAT to scarthgap and styhead.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/conf/layer.conf| 2 +-
meta-ti-extras/conf/layer.conf | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-ti-bsp/conf/layer.conf b/meta-ti-bsp/conf/layer.conf
index
On 4/8/2024 1:09 PM, Denys Dmytriyenko wrote:
Are there still any UBI-based tests running on am335x platform?
No idea. Let me check.
On Mon, Apr 08, 2024 at 09:43:01PM +0530, Chirag Shilwant wrote:
New features added require another increase to max_leb_cnt.
Signed-off-by: Chirag
On 4/4/2024 1:42 PM, Bajjuri, Praneeth wrote:
On 4/4/2024 8:37 AM, Ryan Eatmon wrote:
Set the KERNEL_DEVICETREE_PREFIX so that, when using the various TI
kernel recipes, the "correct" DTB files are pulled in depending on what
is available in that kernel source.
Signed-off-by: Ryan Eatmon
Set the KERNEL_DEVICETREE_PREFIX so that, when using the various TI
kernel recipes, the "correct" DTB files are pulled in depending on what
is available in that kernel source.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/conf/machine/beaglebone-ai64.conf | 4
Update the READMEs with the current available scarthgap branches.
Signed-off-by: Ryan Eatmon
---
v2: Rollback the layers to master that do not have scarthgap branches
yet.
meta-ti-bsp/README| 2 +-
meta-ti-extras/README | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git
On 3/25/2024 7:17 AM, mly...@hi-techniques.com wrote:
There was an announcement in the #Yocto group about the Dunfell branch going to EOL. I
was wondering, will TI still be pushing changes to that branch after it goes EOL or will
changes only be pushed to different (newer) branch(s)? I'm
I'm sorry. We only support the LTS branches plus master. We do not
have the resources to maintain every branch.
You are free to pick up the recipe in a local layer for your project
that is stll on nanbield.
On 3/22/2024 4:47 AM, Samuli Piippo wrote:
Now that the recipe is gone, the
On 3/20/2024 11:29 PM, Chirag Shilwant wrote:
On 21/03/24 01:35, Ryan Eatmon via lists.yoctoproject.org wrote:
All READMEs were still mentioning master, update that. Signed-off-by:
Ryan Eatmon --- meta-ti-bsp/README | 4 ++--
meta-ti-extras/README | 6 +++--- 2 files changed, 5 insertions
All READMEs were still mentioning master, update that.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/README| 4 ++--
meta-ti-extras/README | 6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/meta-ti-bsp/README b/meta-ti-bsp/README
index c5780531..70c40d4e 100644
---
Update the compatibility to just scarthgap.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/conf/layer.conf| 2 +-
meta-ti-extras/conf/layer.conf | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-ti-bsp/conf/layer.conf b/meta-ti-bsp/conf/layer.conf
index
On 3/14/24 13:30, Denys Dmytriyenko wrote:
On Wed, Mar 13, 2024 at 10:13:47AM +0530, Kumar, Udit wrote:
On 3/13/2024 3:20 AM, Denys Dmytriyenko wrote:
On Tue, Mar 12, 2024 at 10:41:32PM +0530, Udit Kumar via lists.yoctoproject.org
wrote:
Signed-off-by: Udit Kumar
---
Changelog:
Changes in
On 3/13/2024 11:53 AM, Denys Dmytriyenko wrote:
On Wed, Mar 13, 2024 at 11:21:49AM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
We have a request to be able to override the beagle kernel set in
PREFERRED_PROVIDER_virtual/kernel, but it is being absolutely set and
not loosely set
We have a request to be able to override the beagle kernel set in
PREFERRED_PROVIDER_virtual/kernel, but it is being absolutely set and
not loosely set with ?=. Take this time to create a central include for
all beagle boards like we have for the k3.inc.
Signed-off-by: Ryan Eatmon
---
We typically put the file grouping of the change in the commit message.
For example:
conf: machine: am57xx: export ov10635 camera device tree overlay
On 3/11/2024 6:14 AM, Udit Kumar via lists.yoctoproject.org wrote:
Adding ov10635 camera overlay in default build
Signed-off-by: Udit
On 3/6/2024 5:34 PM, Randolph Sapp via lists.yoctoproject.org wrote:
On Wed Mar 6, 2024 at 4:50 PM CST, Randolph Sapp via lists.yoctoproject.org
wrote:
From: Randolph Sapp
Bump the package version to align with the changed AM62 GPU device tree
compatible string. This will make it easer to
Copy the same KERNEL_LOCALVERSION change to the upcoming 6.6 kernel.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.6.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.6.bb
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
---
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 9 ++---
1
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
From: Denys Dmytriyenko
A change in master from last year [1] dropped setting SRCPV. Since it is now
empty,
we do not need to use when setting PV.
[1]
https://git.openembedded.org/openembedded-core/commit/?id=a8e7b0f932b9ea69b3a218fca18041676c65aba0
Signed-off-by: Ryan Eatmon
On 2/20/2024 8:31 AM, Andrew Davis wrote:
On 2/16/24 2:23 PM, Denys Dmytriyenko wrote:
Unfortunately, NAK.
This is considered an antisocial behavior for a BSP in the Yocto Project
world. And the performance benefit is questionable with 1%-2%, if at all.
This stated when a potential
This reverts commit 04c2204c11cb3ee5eee84f2d213037b763954786.
oe-core master branch picked up this patch [1], so we no longer need it
in meta-ti.
[1]
https://git.openembedded.org/openembedded-core/commit/?id=128cfc5222752a6337a9cbb9bc9023c13ee19f2f
Signed-off-by: Ryan Eatmon
---
On 1/24/2024 12:23 PM, Ryan Eatmon via lists.yoctoproject.org wrote:
On 1/24/2024 8:46 AM, Devarsh Thakkar wrote:
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.
I'm going to send
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
---
.../recipes-bsp/u-boot/u-boot-ti-mainline_git.bb | 4 ++--
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
---
.../recipes-bsp/u-boot/u-boot-ti-mainline_git.bb | 4 ++--
On 1/24/2024 8:46 AM, Devarsh Thakkar wrote:
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.
I'm going to send another patch that updates the u-boot mainline recipe
to 2024.01 and move the
Add recipe for yamllint. There is an upcoming change in u-boot where
the binman tool is now configured to call yamllint to verify the configs
during compile time.
There was a previous patch a year ago from Trevor Woerner that never
made it into oe-core. This patch is a reworking of his patch
A patch has been accepted in mainline u-boot that has binman calling
yamllint to verify the configs during compile. This means that the
yamllint must be available as a tool at the time.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 2 +-
1 file changed, 1
On 1/5/2024 10:14 AM, Ryan Eatmon via lists.yoctoproject.org wrote:
Can we split this change into two? One patch that explicitly changes
the SRCREV and a second commit that adds support for j722s. I know
that's not how it was during wakeup, but that's what I would prefer for
the long
Can we split this change into two? One patch that explicitly changes
the SRCREV and a second commit that adds support for j722s. I know
that's not how it was during wakeup, but that's what I would prefer for
the long term record.
On 1/5/2024 2:28 AM, Aniket Limaye wrote:
From: Darren
Jose
Ryan Eatmon via lists.yoctoproject.org <http://lists.yoctoproject.org>
<mailto:ti@lists.yoctoproject.org>> escreveu no dia quarta,
20/12/2023 à(s) 16:14:
On 12/20/2023 10:07 AM, Andrew Davis wrote:
> The R5 SPL bootloader is the only software we build us
On 12/20/2023 10:07 AM, Andrew Davis wrote:
The R5 SPL bootloader is the only software we build using the R5 (arm32)
multiconfig environment. Using multiconfig pulls in a large number of
build dependencies (see the -native environment in baremetal tmp dir)
this increases build time and space.
We are preparing to migrate our uboot version to 2024.01. As we are still
working on the migration, mark the default preference low for this
version. We will enable building with this uboot in a meta-arago brand
in the near future. Once the migration is complete, we will remove the
2023.04
We are preparing to migrate our kernel version to 6.6. As we are still
working on the migration, mark the default preference low for this
version. We will enable building with this kernel in a meta-arago brand
in the near future. Once the migration is complete, we will remove the
6.1 kernel and
There was a bug in our CICD script. This is the only new patch. Ignore
the other tree patches in the series. They were already applied.
On 11/27/2023 3:58 PM, LCPD Automation Script wrote:
Updated the value(s) for:
ti-linux-fw:
There was a question for you. I was waiting for you to respond.
On 11/20/2023 2:17 PM, Denys Dmytriyenko wrote:
Ping.
On Sun, Nov 12, 2023 at 07:07:43PM +, Denys Dmytriyenko wrote:
From: Denys Dmytriyenko
This k3r5 multiconfig builds baremetal components (and corresponding native,
On 11/15/2023 11:39 AM, Bajjuri, Praneeth wrote:
updating denys email id
On 11/15/2023 4:58 AM, Sinthu Raja M via lists.yoctoproject.org wrote:
From: Sinthu Raja
The stdarg header file location is changed to linux/stdarg.h. Add patch
to fix the compilation issue and also add fix to import
On 11/14/2023 10:17 AM, Francesco Dolcini wrote:
Hello Randolph,
On Mon, Oct 23, 2023 at 01:15:38PM -0300, Max Krummenacher wrote:
On our weekly CI build we see glmark segfaulting on our AM625 based SoM.
Reverting commit 9b6bce2c ("mesa-pvr: bump srcrev for sgx support") on
top of meta-ti @
Andrew,
Can we add a third patch to also remove the class:
kernel-fitimage-ti-u-boot.bbclass
I beleive it is only referenced in the 5.10 recipe.
On 11/8/2023 10:58 AM, Andrew Davis wrote:
We support Linux v6.1 as our official version for Kirkstone. The older
kernel version was kept around
On 11/8/2023 10:43 AM, Judith Mendez wrote:
Hi Praneeth,
On 11/8/23 10:04 AM, Praneeth Bajjuri wrote:
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
On 11/8/2023 8:35 AM, Kamlesh Gurudasani wrote:
Enable TRNG in AM62X and AM62PX, as bugs related to TRNG has been fixed now.
TF-A fix:
https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=d7a7135d32a8c7da004c0c19b75bd4e2813f9759
OP-TEE fix:
On 11/7/2023 3:52 AM, Vibhore Vardhan wrote:
On 13:45-20231107, Kamlesh Gurudasani wrote:
Hi Kamlesh,
"Bajjuri, Praneeth" writes:
...
---
meta-ti-bsp/recipes-security/optee/optee-os-ti.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-mainline_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-mainline_git.bb
b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-mainline_git.bb
index
1 - 100 of 593 matches
Mail list logo
