From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [git commit] package/tbtools: new package
Date: Sat, 11 May 2024 22:15:11 +0200 [thread overview]
Message-ID: <20240511201528.963ED86FB4@busybox.osuosl.org> (raw)
commit: https://git.buildroot.net/buildroot/commit/?id=8d5b3aac435880333833d4a3909b1818fe8af045
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
This is a collection of tools for Linux Thunderbolt/USB4 development,
debugging and validation.
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Reviewed-by: Aapo Vienamo <aapo.vienamo@linux.intel.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
DEVELOPERS | 3 +++
package/Config.in | 1 +
package/tbtools/Config.in | 18 ++++++++++++++++++
package/tbtools/tbtools.mk | 13 +++++++++++++
4 files changed, 35 insertions(+)
diff --git a/DEVELOPERS b/DEVELOPERS
index 1c0cd336ca..67ce43e9cc 100644
--- a/DEVELOPERS
+++ b/DEVELOPERS
@@ -2300,6 +2300,9 @@ N: Michel Stempin <michel.stempin@wanadoo.fr>
F: board/sipeed/licheepi_zero/
F: configs/sipeed_licheepi_zero_defconfig
+N: Mika Westerberg <mika.westerberg@linux.intel.com>
+F: package/tbtools/
+
N: Mike Frampton <mikeframpo@gmail.com>
F: package/qcom-db410c-firmware/
diff --git a/package/Config.in b/package/Config.in
index edc56290ea..2af63c124e 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -156,6 +156,7 @@ menu "Debugging, profiling and benchmark"
source "package/stress-ng/Config.in"
source "package/sysdig/Config.in"
source "package/sysprof/Config.in"
+ source "package/tbtools/Config.in"
source "package/tcf-agent/Config.in"
source "package/trace-cmd/Config.in"
source "package/trinity/Config.in"
diff --git a/package/tbtools/Config.in b/package/tbtools/Config.in
new file mode 100644
index 0000000000..9c27bf0e30
--- /dev/null
+++ b/package/tbtools/Config.in
@@ -0,0 +1,18 @@
+config BR2_PACKAGE_TBTOOLS
+ bool "tbtools"
+ depends on BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS
+ depends on BR2_TOOLCHAIN_USES_GLIBC
+ depends on BR2_PACKAGE_HAS_UDEV
+ # Fails to build on 32-bit systems
+ depends on BR2_ARCH_IS_64
+ select BR2_PACKAGE_HOST_RUSTC
+ help
+ tbtools is a collection of tools for Linux Thunderbolt/USB4
+ development, debugging and validation.
+
+ https://github.com/intel/tbtools
+
+comment "tbtools needs udev /dev management w/ glibc toolchain"
+ depends on BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS
+ depends on BR2_ARCH_IS_64
+ depends on !BR2_PACKAGE_HAS_UDEV || !BR2_TOOLCHAIN_USES_GLIBC
diff --git a/package/tbtools/tbtools.mk b/package/tbtools/tbtools.mk
new file mode 100644
index 0000000000..94340616db
--- /dev/null
+++ b/package/tbtools/tbtools.mk
@@ -0,0 +1,13 @@
+################################################################################
+#
+# tbtools
+#
+################################################################################
+
+TBTOOLS_VERSION = v0.3.2
+TBTOOLS_SITE = $(call github,intel,tbtools,$(TBTOOLS_VERSION))
+TBTOOLS_LICENSE = MIT
+TBTOOLS_LICENSE_FILES = LICENSE
+TBTOOLS_DEPENDENCIES = udev
+
+$(eval $(cargo-package))
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2024-05-11 20:15 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=20240511201528.963ED86FB4@busybox.osuosl.org \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.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.