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][dunfell][PATCH 1/3] meta-ti: Rename j7-evm to j721e-evm
Date: Thu, 1 Sep 2022 12:10:27 -0400 [thread overview]
Message-ID: <20220901161027.GK18429@denix.org> (raw)
In-Reply-To: <f5281106-4ac9-a76b-1a3c-44d87e46733b@ti.com>
On Thu, Sep 01, 2022 at 10:31:42AM -0500, Ryan Eatmon via lists.yoctoproject.org wrote:
>
>
> On 8/31/2022 12:53, Andrew Davis wrote:
> >In many places we use "j7" (the family name) when we should be using a
> >specific SoC or EVM and vice-versa. For instance when including graphics
> >drivers we add for all the "j7" family, but what we really want is only
> >for some specific j7 SoCs.
> >
> >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.
> >
> >Signed-off-by: Andrew Davis <afd@ti.com>
> >---
> > .../{j7-evm-k3r5.conf => j721e-evm-k3r5.conf} | 4 ++--
> > conf/machine/{j7-evm.conf => j721e-evm.conf} | 4 ++--
> > ...sr1-1.conf => j721e-hs-evm-k3r5-sr1-1.conf} | 6 +++---
> > ...hs-evm-k3r5.conf => j721e-hs-evm-k3r5.conf} | 4 ++--
> > .../{j7-hs-evm.conf => j721e-hs-evm.conf} | 6 +++---
> > .../cadence-mhdp-fw/cadence-mhdp-fw_git.bb | 2 +-
> > .../ti-img-rogue-driver_1.15.6133109.bb | 10 +++++-----
> > recipes-bsp/sciclient/sciclient-rtos_git.bb | 6 +++---
> > .../viddec-test-app_1.0.0.bb | 2 +-
> > .../videnc-test-app_1.0.0.bb | 2 +-
> > recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb | 18 +++++++++---------
> > .../trusted-firmware-a_%.bbappend | 2 +-
> > .../ti-img-rogue-umlibs_1.15.6133109.bb | 6 +++---
> > recipes-kernel/linux/kernel-rdepends.inc | 4 ++--
> > recipes-security/optee/optee-os_%.bbappend | 2 +-
> > recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 2 +-
> > 16 files changed, 40 insertions(+), 40 deletions(-)
> > rename conf/machine/{j7-evm-k3r5.conf => j721e-evm-k3r5.conf} (81%)
> > rename conf/machine/{j7-evm.conf => j721e-evm.conf} (87%)
> > rename conf/machine/{j7-hs-evm-k3r5-sr1-1.conf => j721e-hs-evm-k3r5-sr1-1.conf} (53%)
> > rename conf/machine/{j7-hs-evm-k3r5.conf => j721e-hs-evm-k3r5.conf} (81%)
> > rename conf/machine/{j7-hs-evm.conf => j721e-hs-evm.conf} (85%)
> >
> >diff --git a/conf/machine/j7-evm-k3r5.conf b/conf/machine/j721e-evm-k3r5.conf
> >similarity index 81%
> >rename from conf/machine/j7-evm-k3r5.conf
> >rename to conf/machine/j721e-evm-k3r5.conf
>
>
> So this changes the name of the yocto build machine label... This
> will be impactful to users used to building j7-evm and for our build
> and testing scripts. I will need to test this and work with Minas
> to make changes on the testing side before I can merge it in.
Right. This was a good and timely change for kirkstone, but is it worth the
effort for dunfell? Supposed to be a stable release branch and avoid breakages
like this...
--
Denys
next prev parent reply other threads:[~2022-09-01 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 17:53 [meta-ti][dunfell][PATCH 0/3] J7 name backports from master/kirkstone Andrew Davis
2022-08-31 17:53 ` [meta-ti][dunfell][PATCH 1/3] meta-ti: Rename j7-evm to j721e-evm Andrew Davis
2022-09-01 15:31 ` Ryan Eatmon
2022-09-01 16:10 ` Denys Dmytriyenko [this message]
2022-09-01 16:20 ` Andrew Davis
2022-09-01 16:33 ` Ryan Eatmon
2022-09-01 16:45 ` Andrew Davis
2022-09-06 22:25 ` Ryan Eatmon
2022-08-31 17:53 ` [meta-ti][dunfell][PATCH 2/3] meta-ti: Add SoC families for the J7 SoCs Andrew Davis
2022-08-31 17:53 ` [meta-ti][dunfell][PATCH 3/3] meta-ti: Use new J7 SoC names over specific board names Andrew Davis
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=20220901161027.GK18429@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.