From: Takashi Iwai <tiwai@suse.de>
To: TJ <systemloc@earthlink.net>
Cc: linux-raid@vger.kernel.org, perex@suse.cz
Subject: Re: via82xx driver: reporting dxs_support experience
Date: Tue, 19 Apr 2005 11:13:09 +0200 [thread overview]
Message-ID: <s5hbr8bceoq.wl@alsa2.suse.de> (raw)
In-Reply-To: <200504171251.03980.systemloc@earthlink.net>
At Sun, 17 Apr 2005 12:51:03 -0400,
TJ wrote:
>
> I was using the 2.6.7 kernel without APIC or ACPI support, and the via82xx
> driver worked perfectly, compiled as a module, without any options. I built a
> new 2.6.7 kernel on the same hardware with APIC and ACPI support in the
> kernel, as the board supports it, and the driver did not work correctly. When
> sound was played, a short, 1 second long bit of the sound to be played was
> looped. Possibly this is the clicking noise described by some people? The
> driver works fine with this new kernel after adding the option
> "dxs_support=1". I hope this interaction with ACPI and APIC sheds some light
> on some of the troubles with this driver. I can provide more information if
> anyone wants it. Please CC me, I'm not on the list.
Please try dxs_support=4 and check a non-48kHz sample (e.g. normal MP3
playback). Usually, dxs_support=4 is the "right" value for most
devices. dxs_support=1 might work on old hardwares, though.
thanks,
Takashi
>
> TJ
>
> Motherboard: MSI K7T266 Pro2
>
> lspci -nv:
>
> 00:00.0 Class 0600: 1106:3099
> Subsystem: 1106:0000
> Flags: bus master, medium devsel, latency 0
> Memory at e0000000 (32-bit, prefetchable) [size=64M]
> Capabilities: [a0] AGP version 2.0
> Capabilities: [c0] Power Management version 2
>
> 00:01.0 Class 0604: 1106:b099
> Flags: bus master, 66Mhz, medium devsel, latency 0
> Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
> Memory behind bridge: dfc00000-dfcfffff
> Prefetchable memory behind bridge: dfa00000-dfafffff
> Capabilities: [80] Power Management version 2
>
> 00:06.0 Class 0200: 8086:100e (rev 02)
> Subsystem: 8086:002e
> Flags: bus master, 66Mhz, medium devsel, latency 96, IRQ 17
> Memory at dffc0000 (32-bit, non-prefetchable) [size=128K]
> Memory at dffa0000 (32-bit, non-prefetchable) [size=128K]
> I/O ports at d800 [size=64]
> Expansion ROM at dff80000 [disabled] [size=128K]
> Capabilities: [dc] Power Management version 2
> Capabilities: [e4] PCI-X non-bridge device.
> Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0
> Enable
> -
>
> 00:07.0 Class 0200: 1317:0985 (rev 11)
> Subsystem: 1317:0570
> Flags: bus master, medium devsel, latency 96, IRQ 18
> I/O ports at d400 [size=256]
> Memory at dfffbc00 (32-bit, non-prefetchable) [size=1K]
> Expansion ROM at dff60000 [disabled] [size=128K]
> Capabilities: [c0] Power Management version 2
>
> 00:08.0 Class 0180: 105a:4d69 (rev 02) (prog-if 85)
> Subsystem: 105a:4d68
> Flags: bus master, 66Mhz, slow devsel, latency 96, IRQ 19
> I/O ports at ec00 [size=8]
> I/O ports at e800 [size=4]
> I/O ports at e400 [size=8]
> I/O ports at e000 [size=4]
> I/O ports at dc00 [size=16]
> Memory at dfffc000 (32-bit, non-prefetchable) [size=16K]
> Expansion ROM at dffe0000 [disabled] [size=16K]
> Capabilities: [60] Power Management version 1
>
> 00:09.0 Class 0180: 1095:0680 (rev 01)
> Subsystem: 1095:0680
> Flags: bus master, medium devsel, latency 96, IRQ 16
> I/O ports at d000 [size=8]
> I/O ports at cc00 [size=4]
> I/O ports at c800 [size=8]
> I/O ports at c400 [size=4]
> I/O ports at c000 [size=16]
> Memory at dfffbb00 (32-bit, non-prefetchable) [size=256]
> Expansion ROM at dfe80000 [disabled] [size=512K]
> Capabilities: [60] Power Management version 2
>
> 00:11.0 Class 0601: 1106:3074
> Subsystem: 1106:0000
> Flags: bus master, stepping, medium devsel, latency 0
> Capabilities: [c0] Power Management version 2
>
> 00:11.1 Class 0101: 1106:0571 (rev 06) (prog-if 8a [Master SecP PriP])
> Subsystem: 1106:0571
> Flags: bus master, medium devsel, latency 32
> I/O ports at fc00 [size=16]
> Capabilities: [c0] Power Management version 2
>
> 00:11.5 Class 0401: 1106:3059 (rev 10)
> Subsystem: 4005:4710
> Flags: medium devsel, IRQ 28
> I/O ports at bc00 [size=256]
> Capabilities: [c0] Power Management version 2
>
prev parent reply other threads:[~2005-04-19 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 16:51 via82xx driver: reporting dxs_support experience TJ
2005-04-17 16:55 ` TJ
2005-04-19 9:13 ` Takashi Iwai [this message]
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=s5hbr8bceoq.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=perex@suse.cz \
--cc=systemloc@earthlink.net \
/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).