From: Chirag Shilwant <c-shilwant@ti.com>
To: <meta-arago@lists.yoctoproject.org>
Cc: Ryan Eatmon <reatmon@ti.com>, Gyan Gupta <g-gupta@ti.com>
Subject: [meta-arago][oe-layersetup][master][PATCH] configs: processor-sdk: Add new config for 9.2.1 SDK Release
Date: Tue, 21 May 2024 12:32:55 +0530 [thread overview]
Message-ID: <20240521070255.5298-1-c-shilwant@ti.com> (raw)
- Add processor-sdk-kirkstone-09.02.01.10-config.txt used for
building AM62SIP & AM64x.
- Add processor-sdk-kirkstone-chromium-09.02.01.10-config.txt used
for building AM62P, AM62x & AM62LP.
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
---
...cessor-sdk-kirkstone-09.02.01.10-config.txt | 17 +++++++++++++++++
...k-kirkstone-chromium-09.02.01.10-config.txt | 18 ++++++++++++++++++
2 files changed, 35 insertions(+)
create mode 100644 configs/processor-sdk/processor-sdk-kirkstone-09.02.01.10-config.txt
create mode 100644 configs/processor-sdk/processor-sdk-kirkstone-chromium-09.02.01.10-config.txt
diff --git a/configs/processor-sdk/processor-sdk-kirkstone-09.02.01.10-config.txt b/configs/processor-sdk/processor-sdk-kirkstone-09.02.01.10-config.txt
new file mode 100644
index 0000000..665b0c6
--- /dev/null
+++ b/configs/processor-sdk/processor-sdk-kirkstone-09.02.01.10-config.txt
@@ -0,0 +1,17 @@
+# 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,40fd5f4eef7460ca67f32cfce8e229e67e1ff607
+meta-tisdk,https://git.ti.com/git/ti-sdk-linux/meta-tisdk.git,kirkstone,09.02.01.10,layers=
+meta-arago,https://git.yoctoproject.org/meta-arago,kirkstone,09.02.00.010,layers=meta-arago-distro:meta-arago-extras:meta-arago-demos:meta-arago-test
+meta-qt5,https://github.com/meta-qt5/meta-qt5.git,kirkstone,644ebf220245bdc06e7696ccc90acc97a0dd2566,layers=
+meta-virtualization,https://git.yoctoproject.org/meta-virtualization,kirkstone,8f0eb65edaf6d280294c33446a9bb073a50b8c14,layers=
+meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,5a6f7925bd2b885955c942573f70a5594f231563,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
+meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone,09.02.00.010,layers=meta-ti-extras:meta-ti-bsp
+meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,260e3adc2bf322f52d81c0642c825088a88bb051,layers=meta-arm:meta-arm-toolchain
+meta-clang,https://github.com/kraj/meta-clang,kirkstone-clang12,c2e89dc7e1dfcc1bbe432afca2dc43d6560cb007,layers=
+oe-core,https://git.openembedded.org/openembedded-core,kirkstone,8a502301209ef144932ef5071c1a9b738db23270,layers=meta
+OECORELAYERCONF=./sample-files/bblayers.conf.sample
+meta-edgeai,https://git.ti.com/git/edgeai/meta-edgeai.git,kirkstone,fdb683aa69d4d70aca17c2d53be3f900ae9d5e72,layers=
+OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
+BITBAKE_INCLUSIVE_VARS=yes
diff --git a/configs/processor-sdk/processor-sdk-kirkstone-chromium-09.02.01.10-config.txt b/configs/processor-sdk/processor-sdk-kirkstone-chromium-09.02.01.10-config.txt
new file mode 100644
index 0000000..f39a317
--- /dev/null
+++ b/configs/processor-sdk/processor-sdk-kirkstone-chromium-09.02.01.10-config.txt
@@ -0,0 +1,18 @@
+# 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,40fd5f4eef7460ca67f32cfce8e229e67e1ff607
+meta-tisdk,https://git.ti.com/git/ti-sdk-linux/meta-tisdk.git,kirkstone,09.02.01.10,layers=
+meta-arago,https://git.yoctoproject.org/meta-arago,kirkstone,09.02.00.010,layers=meta-arago-distro:meta-arago-extras:meta-arago-demos:meta-arago-test
+meta-browser,https://github.com/OSSystems/meta-browser.git,master,d3d16b47e17dc899e5298cff698dc32e5e639ab4,layers=meta-chromium
+meta-qt5,https://github.com/meta-qt5/meta-qt5.git,kirkstone,644ebf220245bdc06e7696ccc90acc97a0dd2566,layers=
+meta-virtualization,https://git.yoctoproject.org/meta-virtualization,kirkstone,8f0eb65edaf6d280294c33446a9bb073a50b8c14,layers=
+meta-openembedded,https://git.openembedded.org/meta-openembedded,kirkstone,5a6f7925bd2b885955c942573f70a5594f231563,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems
+meta-ti,https://git.yoctoproject.org/meta-ti,kirkstone,09.02.00.010,layers=meta-ti-extras:meta-ti-bsp
+meta-arm,https://git.yoctoproject.org/meta-arm,kirkstone,260e3adc2bf322f52d81c0642c825088a88bb051,layers=meta-arm:meta-arm-toolchain
+meta-clang,https://github.com/kraj/meta-clang,kirkstone-clang12,c2e89dc7e1dfcc1bbe432afca2dc43d6560cb007,layers=
+oe-core,https://git.openembedded.org/openembedded-core,kirkstone,8a502301209ef144932ef5071c1a9b738db23270,layers=meta
+OECORELAYERCONF=./sample-files/bblayers.conf.sample
+meta-edgeai,https://git.ti.com/git/edgeai/meta-edgeai.git,kirkstone,fdb683aa69d4d70aca17c2d53be3f900ae9d5e72,layers=
+OECORELOCALCONF=./sample-files/local-arago64-v2.conf.sample
+BITBAKE_INCLUSIVE_VARS=yes
--
2.34.1
reply other threads:[~2024-05-21 7:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240521070255.5298-1-c-shilwant@ti.com \
--to=c-shilwant@ti.com \
--cc=g-gupta@ti.com \
--cc=meta-arago@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 read-only IMAP folder(s) and NNTP newsgroup(s).