From: Denys Dmytriyenko <denis@denix.org>
To: Jon Cormier <jcormier@criticallink.com>
Cc: s-adivi@ti.com, Chirag Shilwant <c-shilwant@ti.com>,
Praneeth Bajjuri <praneeth@ti.com>, Ryan Eatmon <reatmon@ti.com>,
meta-arago@lists.yoctoproject.org,
Paresh Bhagat <p-bhagat@ti.com>, Khasim <khasim@ti.com>,
Gyan Gupta <g-gupta@ti.com>
Subject: Re: [meta-arago][oe-layersetup][PATCH] configs: processor-sdk: Add new config for AM33x, AM43x
Date: Tue, 31 Oct 2023 12:21:14 -0400 [thread overview]
Message-ID: <20231031162114.GG2408@denix.org> (raw)
In-Reply-To: <CADL8D3a5pGUyYqagHk=wK32g3ujYhQca9r7KJerbtMAH83vRyQ@mail.gmail.com>
AM33x, AM43x (and AM57x) are ARMv7-based TI platforms/families and are now
considered "legacy" - those are in maintenance mode, no new development.
That has been the case for at least couple years now...
All current active platforms are K3-based (ARMv8/Aarch64) with J7, AM6x, etc.
families of devices.
And my understanding is that this config is specific to those 2 legacy
platforms, hence the naming. Not sure if it's the right way to name it
though...
On Tue, Oct 31, 2023 at 12:00:48PM -0400, Jon Cormier wrote:
> Why is it labeled -legacy?
>
> On Tue, Oct 31, 2023 at 5:13 AM Sai Sree Kartheek Adivi via
> lists.yoctoproject.org <s-adivi=ti.com@lists.yoctoproject.org> wrote:
>
> > On 14:37-20231031, Chirag Shilwant wrote:
> > > - Add processor-sdk-09.01.00-legacy-config.txt used for building AM33x,
> > AM43x.
> > >
> > > Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
> >
> > Acked-by: Sai Sree Kartheek Adivi <s-adivi@ti.com>
> >
> > > ---
> > > .../processor-sdk-09.01.00-legacy-config.txt | 15 +++++++++++++++
> > > 1 file changed, 15 insertions(+)
> > > create mode 100644
> > configs/processor-sdk/processor-sdk-09.01.00-legacy-config.txt
> > >
> > > diff --git
> > a/configs/processor-sdk/processor-sdk-09.01.00-legacy-config.txt
> > b/configs/processor-sdk/processor-sdk-09.01.00-legacy-config.txt
> > > new file mode 100644
> > > index 0000000..66a47e3
> > > --- /dev/null
> > > +++ b/configs/processor-sdk/processor-sdk-09.01.00-legacy-config.txt
> > > @@ -0,0 +1,15 @@
> > > +# This file takes repo entries in the format
> > > +# repo name,repo uri,repo branch,repo
> > commit[,layers=layer1:layer2...:layern]
> > > +
> > > +bitbake,
> > https://git.openembedded.org/bitbake,2.0,9993a89e5b97dda5f3657e5a7cc3a4fa94ff7111
> > > +meta-processor-sdk,
> > https://git.ti.com/git/processor-sdk/meta-processor-sdk.git,kirkstone,09.01.00.001,layers=
> > > +meta-arago,
> > https://git.yoctoproject.org/meta-arago,kirkstone,09.01.00.001,layers=meta-arago-distro:meta-arago-extras:meta-arago-demos:meta-arago-test
> > > +meta-qt5,
> > https://github.com/meta-qt5/meta-qt5.git,kirkstone,ae8a97f79364bed1abc297636f7933d0e35f22be,layers=
> > > +meta-virtualization,
> > https://git.yoctoproject.org/meta-virtualization,kirkstone,2d8b3cba8ff27c9ec2187a52b6a551fe1dcfaa07,layers=
> > > +meta-openembedded,
> > https://git.openembedded.org/meta-openembedded,kirkstone,9c5541f7e18a1fac3b8dea71e1ebb8398d58e6ff,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems:meta-multimedia
> > > +meta-ti,
> > https://git.yoctoproject.org/meta-ti,kirkstone,09.01.00.001,layers=meta-ti-extras:meta-ti-bsp
> > > +meta-arm,
> > https://git.yoctoproject.org/meta-arm,kirkstone,b187fb9232ca0a6b5f8f90b4715958546fc41d73,layers=meta-arm:meta-arm-toolchain
> > > +oe-core,
> > https://git.openembedded.org/openembedded-core,kirkstone,2572b32e729831762790ebfbf930a1140657faea,layers=meta
> > > +OECORELAYERCONF=./sample-files/bblayers.conf.sample
> > > +OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
> > > +BITBAKE_INCLUSIVE_VARS=yes
> > > --
> > > 2.34.1
prev parent reply other threads:[~2023-10-31 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 9:07 [meta-arago][oe-layersetup][PATCH] configs: processor-sdk: Add new config for AM33x, AM43x Chirag Shilwant
2023-10-31 9:13 ` Sai Sree Kartheek Adivi
2023-10-31 16:00 ` Jon Cormier
2023-10-31 16:21 ` 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=20231031162114.GG2408@denix.org \
--to=denis@denix.org \
--cc=c-shilwant@ti.com \
--cc=g-gupta@ti.com \
--cc=jcormier@criticallink.com \
--cc=khasim@ti.com \
--cc=meta-arago@lists.yoctoproject.org \
--cc=p-bhagat@ti.com \
--cc=praneeth@ti.com \
--cc=reatmon@ti.com \
--cc=s-adivi@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 read-only IMAP folder(s) and NNTP newsgroup(s).