From: James Hilliard <james.hilliard1@gmail.com>
To: buildroot@buildroot.org
Cc: Stefan Hager <stefan.hager@ginzinger.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
James Hilliard <james.hilliard1@gmail.com>
Subject: [Buildroot] [PATCH v8 01/10] package/cpuinfo: new package
Date: Tue, 28 Jan 2025 10:01:44 -0700 [thread overview]
Message-ID: <20250128170153.2298242-1-james.hilliard1@gmail.com> (raw)
From: Stefan Hager <stefan.hager@ginzinger.com>
This package is required by tensorflow-lite.
Tested-by: Stefan Hager <stefan.hager@ginzinger.com>
Signed-off-by: Stefan Hager <stefan.hager@ginzinger.com>
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
---
Changes v6 -> v7:
- update to latest commit
- drop patch which is now upstream
Changes v5 -> v6:
- update patch to latest pull request version
- add architecture restrictions
- update to latest commit
Changes v4 -> v5:
- don't require cpp
Changes v2 -> v3:
- move to libraries->hardware handling
---
DEVELOPERS | 3 +++
package/Config.in | 1 +
package/cpuinfo/Config.in | 17 +++++++++++++++++
package/cpuinfo/cpuinfo.hash | 4 ++++
package/cpuinfo/cpuinfo.mk | 17 +++++++++++++++++
5 files changed, 42 insertions(+)
create mode 100644 package/cpuinfo/Config.in
create mode 100644 package/cpuinfo/cpuinfo.hash
create mode 100644 package/cpuinfo/cpuinfo.mk
diff --git a/DEVELOPERS b/DEVELOPERS
index fde9360ad6..8e33b20bba 100644
--- a/DEVELOPERS
+++ b/DEVELOPERS
@@ -3032,6 +3032,9 @@ F: package/libvpx/
F: package/mesa3d-demos/
F: package/ti-gfx/
+N: Stefan Hager <stefan.hager@ginzinger.com>
+F: package/cpuinfo/
+
N: Stefan Nickl <Stefan.Nickl@gmail.com>
F: board/freescale/imx8dxlevk/
F: configs/freescale_imx8dxlevk_defconfig
diff --git a/package/Config.in b/package/Config.in
index 3f4dd42cbe..70ad2af568 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -1801,6 +1801,7 @@ menu "Hardware handling"
source "package/bcm2835/Config.in"
source "package/c-periphery/Config.in"
source "package/ccid/Config.in"
+ source "package/cpuinfo/Config.in"
source "package/dtc/Config.in"
source "package/gnu-efi/Config.in"
source "package/hackrf/Config.in"
diff --git a/package/cpuinfo/Config.in b/package/cpuinfo/Config.in
new file mode 100644
index 0000000000..257480f068
--- /dev/null
+++ b/package/cpuinfo/Config.in
@@ -0,0 +1,17 @@
+config BR2_PACKAGE_CPUINFO_ARCH_SUPPORTS
+ bool
+ default y if BR2_aarch64
+ default y if BR2_arm
+ default y if BR2_i386
+ default y if BR2_x86_64
+
+config BR2_PACKAGE_CPUINFO
+ bool "cpuinfo"
+ depends on BR2_PACKAGE_CPUINFO_ARCH_SUPPORTS
+ depends on BR2_TOOLCHAIN_HAS_THREADS
+ help
+ CPU INFOrmation library, cpuinfo is a library to detect
+ essential for performance optimization information about
+ host CPU.
+
+ https://github.com/pytorch/cpuinfo
diff --git a/package/cpuinfo/cpuinfo.hash b/package/cpuinfo/cpuinfo.hash
new file mode 100644
index 0000000000..499363cd09
--- /dev/null
+++ b/package/cpuinfo/cpuinfo.hash
@@ -0,0 +1,4 @@
+# Locally calculated
+sha256 37bb2fd2d1e87102baea8d131a0c550c4ceff5a12fba61faeb1bff63868155f1 cpuinfo-8a1772a0c5c447df2d18edf33ec4603a8c9c04a6.tar.gz
+# License files, locally calculated
+sha256 8e7e60636c3aa0cb03571a1a841ce5697f9551ff92b3c426c2561613d15ade70 LICENSE
diff --git a/package/cpuinfo/cpuinfo.mk b/package/cpuinfo/cpuinfo.mk
new file mode 100644
index 0000000000..0aafb1b4dd
--- /dev/null
+++ b/package/cpuinfo/cpuinfo.mk
@@ -0,0 +1,17 @@
+################################################################################
+#
+# cpuinfo
+#
+################################################################################
+
+CPUINFO_VERSION = 8a1772a0c5c447df2d18edf33ec4603a8c9c04a6
+CPUINFO_SITE = $(call github,pytorch,cpuinfo,$(CPUINFO_VERSION))
+CPUINFO_LICENSE = BSD-2-Clause
+CPUINFO_LICENSE_FILES = LICENSE
+CPUINFO_INSTALL_STAGING = YES
+CPUINFO_CONF_OPTS = \
+ -DCPUINFO_BUILD_UNIT_TESTS=OFF \
+ -DCPUINFO_BUILD_MOCK_TESTS=OFF \
+ -DCPUINFO_BUILD_BENCHMARKS=OFF
+
+$(eval $(cmake-package))
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2025-01-28 17:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 17:01 James Hilliard [this message]
2025-01-28 17:01 ` [Buildroot] [PATCH v8 02/10] package/ruy: new package James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 03/10] package/gemmlowp: " James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 04/10] package/pthreadpool: " James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 05/10] package/psimd: " James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 06/10] package/fp16: " James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 07/10] package/xnnpack: " James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 08/10] package/fft2d: " James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 09/10] package/farmhash: " James Hilliard
2025-01-28 17:01 ` [Buildroot] [PATCH v8 10/10] package/tensorflow-lite: " James Hilliard
2025-01-28 22:40 ` Julien Olivain
2025-01-28 23:00 ` James Hilliard
2025-01-28 22:36 ` [Buildroot] [PATCH v8 01/10] package/cpuinfo: " Julien Olivain
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=20250128170153.2298242-1-james.hilliard1@gmail.com \
--to=james.hilliard1@gmail.com \
--cc=buildroot@buildroot.org \
--cc=stefan.hager@ginzinger.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox