From: Kees Bakker <kees.bakker@xs4all.nl>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.0-test6] Scratchy sound with via82xx (VT8233)
Date: Fri, 3 Oct 2003 18:40:17 +0200 [thread overview]
Message-ID: <200310031840.17289.kees.bakker@xs4all.nl> (raw)
In-Reply-To: <s5h7k3o0x8b.wl@alsa2.suse.de>
[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]
On Thursday 02 October 2003 12:07, you wrote:
> At Tue, 30 Sep 2003 20:46:47 +0200,
>
> Kees Bakker wrote:
> > I saw the note about dxs_support, but I have the driver built-in. How do
> > I set dxs_support from the /proc/cmdline?
>
> pass via boot parameter:
>
> snd-via82xx=1,0,,-1,48000,XXX
>
> where XXX is the value from 0 to 3 for dxs_support.
> see the comment in sound/via82xx.c.
Ah, I see. Well, I tested my VIA in another way. I applied this patch, which
adds it to the whitelist. So far it behaves OK. Are there any particular
tests that I can run to make sure?
Also, I want draw your attention to the fact that there DOES exist
a VIA8233-Pre in the wild. Here is my lspci output on my MSI KT266
motherboard:
iris:~ # cat /proc/asound/cards
0 [V8233Pre ]: VIA8233 - VIA 8233-Pre
VIA 8233-Pre at 0xd000, irq 10
iris:~ # lspci -nv -s 00:11.5
00:11.5 Class 0401: 1106:3059 (rev 10)
Subsystem: 1462:3800
Flags: medium devsel, IRQ 10
I/O ports at d000 [size=256]
Capabilities: [c0] Power Management version 2
And in case it helps, here is the output from /proc/asound/devices:
iris:~ # cat /proc/asound/devices
1: : sequencer
0: [0- 0]: ctl
17: [0- 1]: digital audio playback
25: [0- 1]: digital audio capture
16: [0- 0]: digital audio playback
24: [0- 0]: digital audio capture
33: : timer
Let me know if you need more information.
Kees
[-- Attachment #2: via82xx-add-kt266.patch --]
[-- Type: text/x-diff, Size: 513 bytes --]
--- linux-2.6.0/sound/pci/via82xx.c.orig 2003-10-03 18:30:25.000000000 +0200
+++ linux-2.6.0/sound/pci/via82xx.c 2003-10-03 18:31:38.615792728 +0200
@@ -1969,6 +1969,7 @@
static struct dxs_whitelist whitelist[] = {
{ .vendor = 0x1019, .device = 0x0996, .action = VIA_DXS_48K },
{ .vendor = 0x1297, .device = 0xc160, .action = VIA_DXS_ENABLE }, /* Shuttle SK41G */
+ { .vendor = 0x1462, .device = 0x3800, .action = VIA_DXS_ENABLE }, /* MSI KT266 */
{ } /* terminator */
};
struct dxs_whitelist *w;
next prev parent reply other threads:[~2003-10-03 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 18:46 Kees Bakker
2003-09-30 22:34 ` James Stevenson
2003-10-02 10:07 ` Takashi Iwai
2003-10-02 20:05 ` James Stevenson
2003-10-06 12:35 ` Takashi Iwai
2003-10-06 12:47 ` James Stevenson
2003-10-03 16:40 ` Kees Bakker [this message]
2003-10-06 12:34 ` Takashi Iwai
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=200310031840.17289.kees.bakker@xs4all.nl \
--to=kees.bakker@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®