From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: alsa-devel@alsa-project.org
Subject: [PATCH] docs: sound: hda: drop mentions of hda-analyzer
Date: Wed, 5 Apr 2023 22:12:20 +0200 [thread overview]
Message-ID: <20230405201220.2197848-1-oswald.buddenhagen@gmx.de> (raw)
It's gone from the repos, presumably because nobody ported it to
Python 3.
I'm leaving hda-emu in, even though it isn't actually usable with
current kernels (but with some minor hacking, the encoding tools work).
Signed-off-by: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
---
Documentation/sound/hd-audio/notes.rst | 24 ++++--------------------
1 file changed, 4 insertions(+), 20 deletions(-)
diff --git a/Documentation/sound/hd-audio/notes.rst b/Documentation/sound/hd-audio/notes.rst
index a9e35b1f87bd..34865d3b7512 100644
--- a/Documentation/sound/hd-audio/notes.rst
+++ b/Documentation/sound/hd-audio/notes.rst
@@ -308,9 +308,9 @@ Direct Debugging
----------------
If no model option gives you a better result, and you are a tough guy
to fight against evil, try debugging via hitting the raw HD-audio
-codec verbs to the device. Some tools are available: hda-emu and
-hda-analyzer. The detailed description is found in the sections
-below. You'd need to enable hwdep for using these tools. See "Kernel
+codec verbs to the device. One tool is available: hda-emu.
+The detailed description is found in the section below.
+You'd need to enable hwdep for using this tool. See the "Kernel
Configuration" section.
@@ -339,7 +339,7 @@ When this is enabled, the driver creates hardware-dependent devices
(one per each codec), and you have a raw access to the device via
these device files. For example, ``hwC0D2`` will be created for the
codec slot #2 of the first card (#0). For debug-tools such as
-hda-verb and hda-analyzer, the hwdep device has to be enabled.
+hda-verb, the hwdep device has to be enabled.
Thus, it'd be better to turn this on always.
``CONFIG_SND_HDA_RECONFIG`` is a new option, and this depends on the
@@ -819,22 +819,6 @@ See README file in the tarball for more details about hda-verb
program.
-hda-analyzer
-------------
-hda-analyzer provides a graphical interface to access the raw HD-audio
-control, based on pyGTK2 binding. It's a more powerful version of
-hda-verb. The program gives you an easy-to-use GUI stuff for showing
-the widget information and adjusting the amp values, as well as the
-proc-compatible output.
-
-The hda-analyzer:
-
-* https://git.alsa-project.org/?p=alsa.git;a=tree;f=hda-analyzer
-
-is a part of alsa.git repository in alsa-project.org:
-
-* git://git.alsa-project.org/alsa.git
-
Codecgraph
----------
Codecgraph is a utility program to generate a graph and visualizes the
--
2.40.0.152.g15d061e6df
next reply other threads:[~2023-04-05 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 20:12 Oswald Buddenhagen [this message]
2023-04-06 6:19 ` [PATCH] docs: sound: hda: drop mentions of hda-analyzer Takashi Iwai
2023-04-06 8:08 ` Jaroslav Kysela
2023-04-06 8:14 ` Takashi Iwai
2023-04-06 8:29 ` Oswald Buddenhagen
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=20230405201220.2197848-1-oswald.buddenhagen@gmx.de \
--to=oswald.buddenhagen@gmx.de \
--cc=alsa-devel@alsa-project.org \
/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