mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl via ptxdist <ptxdist@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alexander Dahl <ada@thorsis.com>
Subject: [ptxdist] [PATCH] phytool: Add new package
Date: Wed, 19 Nov 2025 10:29:59 +0100	[thread overview]
Message-ID: <20251119092959.50582-1-ada@thorsis.com> (raw)

While the user interface is not intuitive at all, the tool gets the job
done of poking in PHY registers through MDIO.

Link: https://github.com/wkz/phytool
Signed-off-by: Alexander Dahl <ada@thorsis.com>
---
 rules/phytool.in   |  9 +++++++
 rules/phytool.make | 63 ++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 72 insertions(+)
 create mode 100644 rules/phytool.in
 create mode 100644 rules/phytool.make

diff --git a/rules/phytool.in b/rules/phytool.in
new file mode 100644
index 000000000..95a64afd5
--- /dev/null
+++ b/rules/phytool.in
@@ -0,0 +1,9 @@
+## SECTION=networking
+
+config PHYTOOL
+	tristate
+	prompt "phytool"
+	help
+	  Linux MDIO register access
+
+# vim: ft=kconfig tw=80
diff --git a/rules/phytool.make b/rules/phytool.make
new file mode 100644
index 000000000..c38a2f19c
--- /dev/null
+++ b/rules/phytool.make
@@ -0,0 +1,63 @@
+# -*-makefile-*-
+#
+# Copyright (C) 2025 by Alexander Dahl <ada@thorsis.com>
+#
+# For further information about the PTXdist project and license conditions
+# see the README file.
+#
+
+#
+# We provide this package
+#
+PACKAGES-$(PTXCONF_PHYTOOL) += phytool
+
+#
+# Paths and names
+#
+PHYTOOL_VERSION	:= 2
+PHYTOOL_MD5	:= 972982f8e5f7237cbccfc6d275da7348
+PHYTOOL		:= phytool-$(PHYTOOL_VERSION)
+PHYTOOL_SUFFIX	:= tar.xz
+PHYTOOL_URL	:= https://github.com/wkz/phytool/releases/download/v$(PHYTOOL_VERSION)/$(PHYTOOL).$(PHYTOOL_SUFFIX)
+PHYTOOL_SOURCE	:= $(SRCDIR)/$(PHYTOOL).$(PHYTOOL_SUFFIX)
+PHYTOOL_DIR	:= $(BUILDDIR)/$(PHYTOOL)
+PHYTOOL_LICENSE	:= GPL-2.0-or-later
+PHYTOOL_LICENSE_FILES := \
+	file://LICENSE;md5=39bba7d2cf0ba1036f2a6e2be52fe3f0
+
+# ----------------------------------------------------------------------------
+# Prepare
+# ----------------------------------------------------------------------------
+
+PHYTOOL_CONF_TOOL	:= NO
+
+PHYTOOL_MAKE_ENV	:= $(CROSS_ENV)
+PHYTOOL_MAKE_OPT	:= \
+	PREFIX=/usr \
+	all
+
+PHYTOOL_INSTALL_OPT	:= \
+	PREFIX=/usr \
+	DESTDIR=$(PHYTOOL_PKGDIR) \
+	install
+
+# ----------------------------------------------------------------------------
+# Target-Install
+# ----------------------------------------------------------------------------
+
+$(STATEDIR)/phytool.targetinstall:
+	@$(call targetinfo)
+
+	@$(call install_init, phytool)
+	@$(call install_fixup, phytool,PRIORITY,optional)
+	@$(call install_fixup, phytool,SECTION,base)
+	@$(call install_fixup, phytool,AUTHOR,"Alexander Dahl <ada@thorsis.com>")
+	@$(call install_fixup, phytool,DESCRIPTION,missing)
+
+	@$(call install_copy, phytool, 0, 0, 0755, -, /usr/bin/phytool)
+
+	@$(call install_finish, phytool)
+
+	@$(call touch)
+
+# vim: ft=make

base-commit: 385f5478624d37733e102ee30b7f9ec434fc7c33
-- 
2.39.5




                 reply	other threads:[~2025-11-19  9:30 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=20251119092959.50582-1-ada@thorsis.com \
    --to=ptxdist@pengutronix.de \
    --cc=ada@thorsis.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