From: mator@helminth.linuxhacker.ru
To: linux-kernel@vger.kernel.org
Subject: 2.4.24 VIA sound driver Config.in patch
Date: Tue, 9 Mar 2004 00:51:39 +0300 [thread overview]
Message-ID: <20040308215139.GA15630@helminth.linuxhacker.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 231 bytes --]
Hello.
This patch enables stats/info for VIA onboard sound codec driver
accessible via /proc fs.
CONFIG_SOUND_VIA82CXXX_PROCFS declared in source code, but missed in
Config.in.
Apply if needed. Same missing in 2.6.x kernel tree.
[-- Attachment #2: via-sound-codec.diff --]
[-- Type: text/plain, Size: 490 bytes --]
--- linux/drivers/sound/Config.in-orig 2004-01-18 15:52:57.000000000 +0300
+++ linux/drivers/sound/Config.in 2004-01-18 15:58:15.000000000 +0300
@@ -129,6 +129,7 @@
fi
dep_tristate ' VIA 82C686 Audio Codec' CONFIG_SOUND_VIA82CXXX $CONFIG_PCI
+dep_mbool ' VIA codec /proc entry' CONFIG_SOUND_VIA82CXXX_PROCFS $CONFIG_SOUND_VIA82CXXX
dep_mbool ' VIA 82C686 MIDI' CONFIG_MIDI_VIA82CXXX $CONFIG_SOUND_VIA82CXXX
dep_tristate ' OSS sound modules' CONFIG_SOUND_OSS $CONFIG_SOUND
reply other threads:[~2004-03-08 21:53 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=20040308215139.GA15630@helminth.linuxhacker.ru \
--to=mator@helminth.linuxhacker.ru \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).