From: "Denys Dmytriyenko" <denis@denix.org>
To: Lokesh Vutla <lokeshvutla@ti.com>
Cc: Nishanth Menon <nm@ti.com>, meta-ti <meta-ti@yoctoproject.org>,
"Bajjuri, Praneeth" <praneeth@ti.com>
Subject: Re: [EXTERNAL,dunfell] ti-rtos: Fix J7200 builds by dropping evm
Date: Fri, 5 Mar 2021 12:14:12 -0500 [thread overview]
Message-ID: <20210305171412.GU4892@denix.org> (raw)
In-Reply-To: <72eb91ce-5e29-a79b-cdb4-0a12e6200ee4@ti.com>
On Fri, Mar 05, 2021 at 02:38:00PM +0530, Lokesh Vutla wrote:
> Hi Denys,
>
> On 05/03/21 1:53 pm, Denys Dmytriyenko wrote:
> > On Fri, Mar 05, 2021 at 01:11:05AM -0600, Nishanth Menon wrote:
> >> On 12:34-20210305, Lokesh Vutla wrote:
> >>>
> >>>
> >>> On 05/03/21 6:11 pm, Nishanth Menon via lists.yoctoproject.org wrote:
> >>>> "evm" prefix messes up the pattern matchup for J7200 and falls back into
> >>>> default, as a result, we attempt to pull [1] instead of [2].
> >>>>
> >>>> [1] https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/firmware/07_03_00_12/coresdk_rtos_j7200_07_03_00_12_firmware.tar.xz
> >>>> [2] https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/firmware/07_03_00_10/coresdk_rtos_j7200_07_03_00_12_firmware.tar.xz
> >>>>
> >>>> Fixes: 77cdfa9f6560 ("ti-rtos: Update metadata and versions for RTOS firmware")
> >>>> Signed-off-by: Nishanth Menon <nm@ti.com>
> >>>
> >>> For the sake of completeness can you add default web link for j7200? I still
> >>> couldn't figure out how the weblink is populated when default is undefined.
> >>>
> >>> DEFAULT_RTOS_WEBLINK_j7200 =
> >>> "https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/firmware/${CORESDK_RTOS_VERSION}"
> >>>
> >>
> >> I believe _j7 does matchup j7200, hence it works and adding _j7200 will
> >> be redundant..
> >
> > From least specific to most specific for j7200-evm machine:
> >
> > MACHINEOVERRIDES="aarch64:ti-soc:k3:j7:j7200-evm"
>
> Thanks for the explanation. Where does this variable (MACHINEOVERRIDES) get
> populated?
It is being composed from different places. It starts with MACHINE on the
right. Then SOC_FAMILY list gets built from different .inc files in meta-ti.
And finally tune features for arch-arm64 prepend it with "aarch64" on the
left. And it would be "armv5", "armv7a" or "armv7ve" for legacy platforms.
So, roughly MACHINEOVERRIDES=${ARCH}:${SOC_FAMILY}:${MACHINE}
> Thanks and regards,
> Lokesh
>
> >
> > For comparison, the same for j7-evm:
> >
> > MACHINEOVERRIDES="aarch64:ti-soc:k3:j7:j7-evm"
> >
> > Or j7-hs-evm:
> >
> > MACHINEOVERRIDES="aarch64:ti-soc:k3:j7:j7-hs-evm"
> >
> > All of them are in the same "j7" SOC_FAMILY, as that was supposed to be a
> > superset for J7 family, even though ended up being rather specific to j721e...
> >
> > So, when you use _j7 override, that covers j7-evm, j7-hs-evm, j7200-evm an so
> > on.
> >
> >
> >> DEFAULT_RTOS_WEBLINK_j7 = "https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/firmware/${CORESDK_RTOS_VERSION}"
> >>
> >> I am a noobie on this, so will be interested in folk's feedback.
> >>
> >> --
> >> Regards,
> >> Nishanth Menon
> >> Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
> >>
> >
>
--
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
prev parent reply other threads:[~2021-03-05 17:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 6:41 [PATCH dunfell] ti-rtos: Fix J7200 builds by dropping evm Nishanth Menon
2021-03-05 6:45 ` Nishanth Menon
2021-03-05 8:06 ` Denys Dmytriyenko
[not found] ` <166963B5CCB828E3.16425@lists.yoctoproject.org>
2021-03-05 8:13 ` [meta-ti] " Denys Dmytriyenko
2021-03-05 7:04 ` [EXTERNAL,dunfell] " Lokesh Vutla
2021-03-05 7:11 ` Nishanth Menon
2021-03-05 7:44 ` Lokesh Vutla
2021-03-05 8:23 ` Denys Dmytriyenko
2021-03-05 9:08 ` Lokesh Vutla
2021-03-05 17:14 ` Denys Dmytriyenko [this message]
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=20210305171412.GU4892@denix.org \
--to=denis@denix.org \
--cc=lokeshvutla@ti.com \
--cc=meta-ti@yoctoproject.org \
--cc=nm@ti.com \
--cc=praneeth@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.