From: Denys Dmytriyenko <denis@denix.org>
To: reatmon@ti.com
Cc: Andrew Davis <afd@ti.com>, Denys Dmytriyenko <denys@konsulko.com>,
meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti][master/kirkstone][PATCH 6/8] ti-rtos-firmware: Use a table instead of a list of copy commands
Date: Fri, 10 Feb 2023 16:23:22 -0500 [thread overview]
Message-ID: <20230210212322.GE22689@denix.org> (raw)
In-Reply-To: <4b7c58a4-6d44-5df9-1567-7f2e1061643c@ti.com>
On Thu, Feb 09, 2023 at 07:29:46AM -0600, Ryan Eatmon via lists.yoctoproject.org wrote:
>
>
> On 2/7/2023 17:42, Andrew Davis wrote:
> >Using a table makes it easier to see what firmware is included with
> >each machine build. It also helps prevent errors here.
>
> I like the table. It makes it clearer to see what is available on
> which platform. Nice change.
Yeah, nicely done!
With the change I just realized that J721e is the only K3 SoC/platform with
C66 (and C7 at the same time) cores, interesting... :)
> >Since the same functions run across machines we now sign all the firmware
> >without needing to add a new signing function for each new machine.
> >
> >Another fix is that we install the DM firmware to the deploy directory
> >for all machines that use need it. This was added for J7x machines
> >but missed for AM62x.
next prev parent reply other threads:[~2023-02-10 21:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 23:42 [meta-ti][master/kirkstone][PATCH 1/8] ti-rtos-firmware: Use ti-k3-secdev if TI_SECURE_DEV_PKG_K3 not defined Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 2/8] ti-rtos-firmware: Remove unneeded per-machine TARGET defines Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 3/8] ti-rtos-firmware: Fix name for AM64x and AM62x firmware Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 4/8] ti-rtos-firmware: Do not break the source directory by renaming files Andrew Davis
2023-02-10 21:07 ` Denys Dmytriyenko
2023-02-10 21:14 ` Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 5/8] ti-rtos-firmware: Use defines to set firmware names Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 6/8] ti-rtos-firmware: Use a table instead of a list of copy commands Andrew Davis
2023-02-09 13:29 ` Ryan Eatmon
2023-02-09 18:11 ` Andrew Davis
2023-02-10 1:46 ` Ryan Eatmon
2023-02-10 21:23 ` Denys Dmytriyenko [this message]
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 7/8] ti-rtos-firmware: Fix use of base_libdir with nonarch_base_libdir Andrew Davis
2023-02-07 23:42 ` [meta-ti][master/kirkstone][PATCH 8/8] ti-rtos-firmware: Deploy secure firmware unconditionally Andrew Davis
2023-02-10 21:02 ` [meta-ti][master/kirkstone][PATCH 1/8] ti-rtos-firmware: Use ti-k3-secdev if TI_SECURE_DEV_PKG_K3 not defined Denys Dmytriyenko
2023-02-10 21:13 ` Andrew Davis
2023-02-10 21:50 ` Denys Dmytriyenko
2023-02-14 9:45 ` Jose Quaresma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230210212322.GE22689@denix.org \
--to=denis@denix.org \
--cc=afd@ti.com \
--cc=denys@konsulko.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=reatmon@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.