[meta-ti][dunfell][PATCH 4/4] conf: machine: j784s4-evm: Add uarts overlay for J784S4

2023-02-22 Thread Bhavya Kapoor via lists.yoctoproject.org
Add device tree overlay for extending support for mcu_uart0 as well as wkup_uart0 for boards with J784S4 SoC. This overlay will mainly be used for the purpose of testing uart instances. Signed-off-by: Bhavya Kapoor --- conf/machine/j784s4-evm.conf | 1 + 1 file changed, 1 insertion(+) diff --gi

[meta-ti][dunfell][PATCH 3/4] conf: machine: j721s2-evm: Add uarts overlay for J721S2

2023-02-22 Thread Bhavya Kapoor via lists.yoctoproject.org
Add device tree overlay for extending support for mcu_uart0 as well as wkup_uart0 for boards with J721S2 SoC. This overlay will mainly be used for the purpose of testing uart instances. Signed-off-by: Bhavya Kapoor --- conf/machine/j721s2-evm.conf | 1 + 1 file changed, 1 insertion(+) diff --gi

[meta-ti][dunfell][PATCH 1/4] conf: machine: j7200-evm: Add uarts overlay for J7200

2023-02-22 Thread Bhavya Kapoor via lists.yoctoproject.org
Add device tree overlay for extending support for mcu_uart0 as well as wkup_uart0 for boards with J7200 SoC. This overlay will mainly be used for the purpose of testing uart instances. Signed-off-by: Bhavya Kapoor --- conf/machine/j7200-evm.conf | 1 + 1 file changed, 1 insertion(+) diff --git

[meta-ti][dunfell][PATCH 2/4] conf: machine: j7-evm: Add uarts overlay for J721E

2023-02-22 Thread Bhavya Kapoor via lists.yoctoproject.org
Add device tree overlay for extending support for mcu_uart0 as well as wkup_uart0 for boards with J721E SoC. This overlay will mainly be used for the purpose of testing uart instances. Signed-off-by: Bhavya Kapoor --- conf/machine/j7-evm.conf | 1 + 1 file changed, 1 insertion(+) diff --git a/c

Re: [meta-ti] [master/kirkstone][PATCH 2/2] ti-sgx-ddk-um: use udev for userspace initialization

2023-02-22 Thread Denys Dmytriyenko
So, testing the latest patch series, I started getting breakage on all SGX platforms: WARNING: tisdk-default-image-1.0-r0 do_rootfs: ti-sgx-ddk-um.postinst returned 1, marking as unpacked only, configuration required on target. ERROR: tisdk-default-image-1.0-r0 do_rootfs: Postinstall scriptlets

Re: [meta-ti] [kirkstone] trouble loading device tree overlay (beaglebone black, uboot, linux-ti-staging)

2023-02-22 Thread Danny Hadley via lists.yoctoproject.org
Following up on this - I was able to get a mirror set up and have been successfully able to clone from that remote instead of `git.beagleboard.org` which solved my fetching problems. I'm not sure if it was necessary, but there were some hoops I had to jump through to checkout and publish the com

Re: [meta-ti][master/kirkstone][PATCH] ti-linux-fw: update to the latest

2023-02-22 Thread Denys Dmytriyenko
On Tue, Feb 21, 2023 at 04:40:48PM -0500, Denys Dmytriyenko wrote: > On Tue, Feb 21, 2023 at 03:29:43PM -0600, Andrew Davis via > lists.yoctoproject.org wrote: > > While here update FW versions and remove those no longer used. > > Thanks! I believe it should take care of those race conditions in

Re: [meta-ti][master/kirkstone][PATCH v2 15/15] ti-rtos-firmware: Deploy secure firmware unconditionally

2023-02-22 Thread Denys Dmytriyenko
On Wed, Feb 15, 2023 at 01:33:55PM -0600, Andrew Davis via lists.yoctoproject.org wrote: > Having signed firmware is needed for the HS platforms, but does not > cause any issues for non-HS. To keep things simple, let's deploy > both sets unconditionally. This prevents mistakes when adding HS > sup

Re: [meta-ti][master/kirkstone][PATCH v2 14/15] ti-rtos-firmware: Fix use of base_libdir with nonarch_base_libdir

2023-02-22 Thread Denys Dmytriyenko
On Wed, Feb 15, 2023 at 01:33:54PM -0600, Andrew Davis via lists.yoctoproject.org wrote: > Firmware belongs in the nonarch lib directory. Use the right variable. > > Signed-off-by: Andrew Davis Tested-by: Denys Dmytriyenko > --- > .../ti-rtos-bin/ti-rtos-firmware.bb | 112

Re: [meta-ti][master/kirkstone][PATCH v2 13/15] ti-rtos-firmware: Use a table instead of a list of copy commands

2023-02-22 Thread Denys Dmytriyenko
On Wed, Feb 15, 2023 at 01:33:53PM -0600, Andrew Davis via lists.yoctoproject.org wrote: > Using a table makes it easier to see what firmware is included with > each machine build. It also helps prevent errors here. > > Since the same functions run across machines we now sign all the firmware > w

Re: [meta-ti][master/kirkstone][PATCH v2 12/15] ti-rtos-firmware: Use defines to set firmware names

2023-02-22 Thread Denys Dmytriyenko
On Wed, Feb 15, 2023 at 01:33:52PM -0600, Andrew Davis via lists.yoctoproject.org wrote: > This allows us to change the name in one spot and avoid duplication. > It also helps prevent hard to see changes/typos in the firmware names. > > Signed-off-by: Andrew Davis Tested-by: Denys Dmytriyenko

Re: [meta-ti][master/kirkstone][PATCH v2 11/15] ti-rtos-firmware: Do not break the source directory by renaming files

2023-02-22 Thread Denys Dmytriyenko
On Wed, Feb 15, 2023 at 01:33:51PM -0600, Andrew Davis via lists.yoctoproject.org wrote: > If we rename files in the source directory the next time we need to rebuild > the original files will be gone and build will fail. Use symlinks instead. > > Signed-off-by: Andrew Davis Tested-by: Denys Dm

Re: [meta-ti][master/kirkstone][PATCH v2 10/15] ti-rtos-firmware: Fix name for AM64x and AM62x firmware

2023-02-22 Thread Denys Dmytriyenko
On Wed, Feb 15, 2023 at 01:33:50PM -0600, Andrew Davis via lists.yoctoproject.org wrote: > The firmware for AM64x and AM62x are renamed to match the other platforms, > but we don't actually change them to match. Remove baremetal from the > names. > > These are only referenced to by softlink, so t

Re: [meta-ti][master/kirkstone][PATCH v2 09/15] ti-rtos-firmware: Remove unneeded per-machine TARGET defines

2023-02-22 Thread Denys Dmytriyenko
On Wed, Feb 15, 2023 at 01:33:49PM -0600, Andrew Davis via lists.yoctoproject.org wrote: > Since these TARGET defines are only used on the machine for which > an ALTERNATIVE is defined and always have the same name, these > provide nothing. Drop them. > > Signed-off-by: Andrew Davis Tested-by:

Re: [meta-ti][master/kirkstone][PATCH v2 08/15] ti-k3-secdev: Remove inclusion of ti-paths.inc

2023-02-22 Thread Denys Dmytriyenko
On Wed, Feb 15, 2023 at 01:33:48PM -0600, Andrew Davis via lists.yoctoproject.org wrote: > Since this directory path will not change, let's avoid use > of ti-paths.inc which is set to be removed. > > Signed-off-by: Andrew Davis Tested-by: Denys Dmytriyenko > --- > meta-ti-bsp/recipes-ti/sec

Re: [meta-ti][master/kirkstone][PATCH v2 07/15] conf: machine: k3: Remove unneeded TI_SECURE_DEV_PKG_K3 assignments

2023-02-22 Thread Denys Dmytriyenko
On Wed, Feb 15, 2023 at 01:33:47PM -0600, Andrew Davis via lists.yoctoproject.org wrote: > For K3 machines the SECDEV selection happens in the recipes that use it. > This assignment is therefor no longer needed. Remove it. > > Suggested-by: Ryan Eatmon > Signed-off-by: Andrew Davis Tested-by:

Re: [meta-ti][master/kirkstone][PATCH v2 06/15] ti-sci-fw: Use new ti-secdev class to sign the images

2023-02-22 Thread Denys Dmytriyenko
On Wed, Feb 15, 2023 at 01:33:46PM -0600, Andrew Davis via lists.yoctoproject.org wrote: > Use the new ti-k3-secdev package to pull in the signing tools if they are > not provided by the environment. > > Signed-off-by: Andrew Davis Tested-by: Denys Dmytriyenko > --- > meta-ti-bsp/recipes-bs

Re: [meta-ti][master/kirkstone][PATCH v2 05/15] ti-rtos-firmware: Use new ti-secdev class to sign the images

2023-02-22 Thread Denys Dmytriyenko
On Wed, Feb 15, 2023 at 01:33:45PM -0600, Andrew Davis via lists.yoctoproject.org wrote: > Use ti-k3-secdev native package to provide secure-binary-image.sh script > when it is not passed on as an environment variable. This fixes an issue > with AM64xx which is always HS but should not require TI_

Re: [meta-ti][master/kirkstone][PATCH v2 04/15] u-boot-ti: Use new ti-secdev class to sign the images

2023-02-22 Thread Denys Dmytriyenko
On Wed, Feb 15, 2023 at 01:33:44PM -0600, Andrew Davis via lists.yoctoproject.org wrote: > Use the new ti-k3-secdev package to pull in the signing tools if they are > not provided by the environment. This allows us to use these tools > unconditionally. Remove the checks for the script and do the s

Re: [meta-ti][master/kirkstone][PATCH v2 03/15] optee-os: Use new ti-secdev class to sign the images

2023-02-22 Thread Denys Dmytriyenko
On Wed, Feb 15, 2023 at 01:33:43PM -0600, Andrew Davis via lists.yoctoproject.org wrote: > Use the new ti-k3-secdev package to pull in the signing tools if they are > not provided by the environment. This allows us to use these tools > unconditionally. Remove the checks for the script and do the s

Re: [meta-ti][master/kirkstone][PATCH v2 02/15] trusted-firmware-a: Use new ti-secdev class to sign the images

2023-02-22 Thread Denys Dmytriyenko
On Wed, Feb 15, 2023 at 01:33:42PM -0600, Andrew Davis via lists.yoctoproject.org wrote: > Use the new ti-k3-secdev package to pull in the signing tools if they are > not provided by the environment. This allows us to use these tools > unconditionally. Remove the checks for the script and do the s

Re: [meta-ti][master/kirkstone][PATCH v2 01/15] meta-ti-bsp: Add helper class for TI Security Development Tools

2023-02-22 Thread Denys Dmytriyenko
On Wed, Feb 15, 2023 at 01:33:41PM -0600, Andrew Davis via lists.yoctoproject.org wrote: > The setup here is common to all packages that require signing with > the TI Security Development Tools. Add a helper class to factor out > this commonality. > > Signed-off-by: Andrew Davis Tested-by: Deny

Re: [meta-ti] [kirkstone][PATCH v7 1/3] meta-ti-bsp: graphics: Resolve dependency chain

2023-02-22 Thread Jose Quaresma
Sapp, Randolph escreveu no dia terça, 21/02/2023 à(s) 18:27: > On Mon, Feb 20 2023 at 22:21:15 -05:00:00, Denys Dmytriyenko < > de...@denix.org> wrote: > > > diff --git a/meta-ti-bsp/recipes-graphics/mesa/mesa-gl_22.0.%.bbappend > > b/meta-ti-bsp/recipes-graphics/mesa/mesa-gl_22.0.%.bbappend > ne