From: David Henningsson <david.henningsson@canonical.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>,
741825@bugs.launchpad.net, "Xu, Andiry" <Andiry.Xu@amd.com>
Subject: Should we really use POS_FIX_VIACOMBO for AMD/ATI chipsets?
Date: Fri, 20 May 2011 15:33:56 +0200 [thread overview]
Message-ID: <4DD66DC4.4060902@canonical.com> (raw)
I'm far from sure, but I could be on to something...
Looking at the code for azx_via_get_position, it seems that for
recording streams, it accesses a register at position
VIA_IN_STREAM0_FIFO_SIZE_OFFSET = 0x90. Looking at the datasheet for
SB700, that register is not even present. This does not seem right to me.
Could it be that we should use POS_FIX_LPIB by default for AMD/ATI
chipsets instead? It seems more reasonable to me.
In addition, I looked through some of the commits for quirking to
POS_FIX_LPIB and the four I checked were all ATI chipsets.
So; I've tried adding:
options snd-hda-intel position_fix=1
to /etc/modprobe.d/alsa-base.conf
...to my machine with the infamous [1002:4383] controller (and
rebooted), and the few times I've tested, recording worked successfully
with pulseaudio. So could you please follow this up with testing on your
machines to see if we have actually managed to solve this long-standing bug?
The only annoying thing is that I didn't realise this earlier :-/
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next reply other threads:[~2011-05-20 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 13:33 David Henningsson [this message]
2011-05-20 13:46 ` Should we really use POS_FIX_VIACOMBO for AMD/ATI chipsets? Takashi Iwai
2011-05-20 14:19 ` Takashi Iwai
2011-05-20 14:32 ` Takashi Iwai
2011-05-20 14:51 ` David Henningsson
2011-05-20 14:54 ` 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=4DD66DC4.4060902@canonical.com \
--to=david.henningsson@canonical.com \
--cc=741825@bugs.launchpad.net \
--cc=Andiry.Xu@amd.com \
--cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.