From: Nishanth Menon <nm@ti.com>
To: <denis@denix.org>, <reatmon@ti.com>
Cc: <d-gerlach@ti.com>, <j-humphreys@ti.com>, <khilman@ti.com>,
<meta-arago@lists.yoctoproject.org>, <minas@ti.com>,
<nikhil.nd@ti.com>, <praneeth@ti.com>, <spatton@ti.com>,
Nishanth Menon <nm@ti.com>
Subject: [master/dunfell PATCH V5 08/12] packagegroups: Add a new bootstrap package group
Date: Tue, 22 Mar 2022 12:48:04 -0500 [thread overview]
Message-ID: <20220322174808.16341-9-nm@ti.com> (raw)
In-Reply-To: <20220322174808.16341-1-nm@ti.com>
Lets try and create a minimal package group for board bringup. Lets
call this basic system necessary for board bringup as "bootstrap".
Signed-off-by: Nishanth Menon <nm@ti.com>
---
Changes since V4: None
V4: https://lore.kernel.org/yocto-meta-arago/20220319123310.8546-9-nm@ti.com/
.../packagegroup-arago-bootstrap.bb | 53 +++++++++++++++++++
1 file changed, 53 insertions(+)
create mode 100644 meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-bootstrap.bb
diff --git a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-bootstrap.bb b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-bootstrap.bb
new file mode 100644
index 000000000000..9d961c282c5d
--- /dev/null
+++ b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-bootstrap.bb
@@ -0,0 +1,53 @@
+SUMMARY = "Task to install additional utilities for initial board bringup"
+LICENSE = "MIT"
+PR = "r0"
+
+PACKAGE_ARCH = "${MACHINE_ARCH}"
+
+inherit packagegroup
+
+UTILS = " \
+ arm-benchmarks \
+ evtest \
+ memtester \
+ nbench-byte \
+ pcitest \
+ serialcheck \
+ yavta \
+ hdparm \
+ i2c-tools \
+ libdrm-tests \
+ rt-tests \
+ iozone3 \
+ mtd-utils-ubifs-tests \
+ net-tools \
+ ethtool \
+ pciutils \
+ rng-tools \
+ stress-ng \
+ iperf \
+ lmbench \
+ usbutils \
+ devmem2 \
+ phytool \
+"
+
+UTILS_append_ti33x = " \
+ omapconf \
+"
+
+UTILS_append_ti43x = " \
+ omapconf \
+"
+
+UTILS_append_omap-a15 = " \
+ omapconf \
+"
+
+UTILS_append_k3 = " \
+ k3conf \
+"
+
+RDEPENDS_${PN} = "\
+ ${UTILS} \
+"
--
2.31.1
next prev parent reply other threads:[~2022-03-22 17:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 17:47 [master/dunfell PATCH V5 00/12] recipes-core: Add a bootstrap Linux image Nishanth Menon
2022-03-22 17:47 ` [master/dunfell PATCH V5 01/12] Revert "tisdk-tiny-image: remove packagedata task breaking initramfs packaging" Nishanth Menon
2022-03-22 17:47 ` [master/dunfell PATCH V5 02/12] tisdk-tiny-image: Split common components into include file Nishanth Menon
2022-03-22 17:47 ` [master/dunfell PATCH V5 03/12] tisdk-tiny-image: Add some usability notes Nishanth Menon
2022-03-22 17:48 ` [master/dunfell PATCH V5 04/12] tisdk-base-image: Reformat documentation and clarify usage Nishanth Menon
2022-03-22 17:48 ` [master/dunfell PATCH V5 05/12] tisdk-default-image: " Nishanth Menon
2022-03-22 17:48 ` [master/dunfell PATCH V5 06/12] tisdk-thinlinux-image: Reformat documentation Nishanth Menon
2022-03-22 17:48 ` [master/dunfell PATCH V5 07/12] tisdk-core-bundle: Add documentation to clarify usage Nishanth Menon
2022-03-22 17:48 ` Nishanth Menon [this message]
2022-03-22 17:48 ` [master/dunfell PATCH V5 09/12] recipes-core: images: Add a basic bootstrap base image Nishanth Menon
2022-03-22 17:48 ` [master/dunfell PATCH V5 10/12] recipes-bsp: Create a bootstrap-initrd package Nishanth Menon
2022-03-22 22:21 ` Denys Dmytriyenko
2022-03-23 13:10 ` Nishanth Menon
2022-03-22 17:48 ` [master/dunfell PATCH V5 11/12] recipes-core: images: Introduce tisdk-bootstrap-image Nishanth Menon
2022-03-22 17:48 ` [master/dunfell PATCH V5 12/12] images: Build tisdk-bootstrap-image with tisdk-core-bundle Nishanth Menon
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=20220322174808.16341-9-nm@ti.com \
--to=nm@ti.com \
--cc=d-gerlach@ti.com \
--cc=denis@denix.org \
--cc=j-humphreys@ti.com \
--cc=khilman@ti.com \
--cc=meta-arago@lists.yoctoproject.org \
--cc=minas@ti.com \
--cc=nikhil.nd@ti.com \
--cc=praneeth@ti.com \
--cc=reatmon@ti.com \
--cc=spatton@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.