From: Denys Dmytriyenko <denis@denix.org>
To: afd@ti.com
Cc: Denys Dmytriyenko <denys@konsulko.com>,
Ryan Eatmon <reatmon@ti.com>,
Darren Etheridge <detheridge@ti.com>,
meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti][master][PATCH 1/4] meta-ti: rename j7-evm to j721e-evm
Date: Fri, 25 Mar 2022 15:23:19 -0400 [thread overview]
Message-ID: <20220325192319.GF23554@denix.org> (raw)
In-Reply-To: <20220325184151.16940-1-afd@ti.com>
On Fri, Mar 25, 2022 at 01:41:48PM -0500, Andrew F. Davis via lists.yoctoproject.org wrote:
> In many places we use "j7" the family when we should be using a
> specific SoC or EVM and vice-versa. For instance when including
> graphics drivers we add for all "j7" family, but what we really
> want is only for some specific j7 SoC.
>
> First step in untangling this is to make it clear that there is
> no SoC called j7. There is a SoC called j721e with a j721e-evm.
>
> Fix up this naming here.
Heh, I was actually thinking of finally making such change myself lately! :)
My main concern was about breaking downstream users of meta-ti who builds on
top of j7-evm platform. But it is probably a good time to get it into master
now, as recent layer restructuring already required downstream changes and
adjustments.
> Signed-off-by: Andrew Davis <afd@ti.com>
I looked over the changes in both patchsets and they seem fine.
I'm going to do a quick test locally though.
> ---
> .../machine/{j7-evm-k3r5.conf => j721e-evm-k3r5.conf} | 4 ++--
> meta-ti-bsp/conf/machine/{j7-evm.conf => j721e-evm.conf} | 4 ++--
> ...s-evm-k3r5-sr1-1.conf => j721e-hs-evm-k3r5-sr1-1.conf} | 6 +++---
> .../{j7-hs-evm-k3r5.conf => j721e-hs-evm-k3r5.conf} | 4 ++--
> .../conf/machine/{j7-hs-evm.conf => j721e-hs-evm.conf} | 8 ++++----
> meta-ti-bsp/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb | 6 +++---
> .../trusted-firmware-a/trusted-firmware-a_%.bbappend | 2 +-
> meta-ti-bsp/recipes-security/optee/optee-os_%.bbappend | 2 +-
> meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 2 +-
> 9 files changed, 19 insertions(+), 19 deletions(-)
> rename meta-ti-bsp/conf/machine/{j7-evm-k3r5.conf => j721e-evm-k3r5.conf} (63%)
> rename meta-ti-bsp/conf/machine/{j7-evm.conf => j721e-evm.conf} (82%)
> rename meta-ti-bsp/conf/machine/{j7-hs-evm-k3r5-sr1-1.conf => j721e-hs-evm-k3r5-sr1-1.conf} (53%)
> rename meta-ti-bsp/conf/machine/{j7-hs-evm-k3r5.conf => j721e-hs-evm-k3r5.conf} (67%)
> rename meta-ti-bsp/conf/machine/{j7-hs-evm.conf => j721e-hs-evm.conf} (79%)
--
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
next prev parent reply other threads:[~2022-03-25 19:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 18:41 [meta-ti][master][PATCH 1/4] meta-ti: rename j7-evm to j721e-evm Andrew Davis
2022-03-25 18:41 ` [meta-ti][master][PATCH 2/4] meta-ti-bsp: add SoC families for the J7 SoCs Andrew Davis
2022-03-29 4:50 ` Denys Dmytriyenko
2022-03-29 12:39 ` Ryan Eatmon
2022-03-25 18:41 ` [meta-ti][master][PATCH 3/4] ti-img-rogue-umlibs: only the j721e SoC is currently supported Andrew Davis
2022-03-29 4:50 ` Denys Dmytriyenko
2022-03-29 12:39 ` Ryan Eatmon
2022-03-25 18:41 ` [meta-ti][master][PATCH 4/4] ti-sgx-ddk-um: only the am65xx member of the k3 family is supported Andrew Davis
2022-03-29 4:50 ` Denys Dmytriyenko
2022-03-29 12:39 ` Ryan Eatmon
2022-03-25 19:23 ` Denys Dmytriyenko [this message]
2022-03-25 19:38 ` [meta-ti][master][PATCH 1/4] meta-ti: rename j7-evm to j721e-evm Andrew Davis
2022-03-29 4:48 ` Denys Dmytriyenko
2022-03-29 4:49 ` Denys Dmytriyenko
2022-03-29 12:39 ` Ryan Eatmon
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=20220325192319.GF23554@denix.org \
--to=denis@denix.org \
--cc=afd@ti.com \
--cc=denys@konsulko.com \
--cc=detheridge@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).