alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Éric Piel" <eric.piel@tremplin-utc.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jaroslav Kysela <perex@perex.cz>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	alsa-devel@alsa-project.org, Frank Griffin <ftg@roadrunner.com>
Subject: Re: [REGRESSION bisected] Sound goes too fast due to commit 7b3a177b0
Date: Wed, 14 Apr 2010 13:54:48 +0200	[thread overview]
Message-ID: <4BC5AD08.8040606@tremplin-utc.net> (raw)
In-Reply-To: <4BC5A566.8060106@tremplin-utc.net>

On 14/04/10 13:22, Éric Piel wrote:
:
> I don't fully grasp the meaning of bdl_pos_adj, so I don't know if it's
> a bug to not play correctly when forcing it to 0. Is it?
> 
> I'll ask to another reporter who had the same problem if bdl_pos_adj is
> also set to 0...
Frank (cc'd here) has the same problem of music going too fast (on a
2.6.33 kernel with the "culprit" commit applied). On his system  "cat
/sys/module/snd_hda_intel/parameters/bdl_pos_adj" gives:
32,32,-1,-1,-1,-1,-1,-1

He also mentioned that on another system also using snd_hda_intel, with
the same bdl_pos_adj, it works fine.

Eric

  reply	other threads:[~2010-04-14 11:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13 21:54 [REGRESSION bisected] Sound goes too fast due to commit 7b3a177b0 Éric Piel
2010-04-14  6:08 ` Takashi Iwai
2010-04-14 11:22   ` Éric Piel
2010-04-14 11:54     ` Éric Piel [this message]
2010-04-14 13:39       ` Takashi Iwai
2010-04-14 14:36         ` Éric Piel
2010-04-14 15:39           ` Frank Griffin
2010-04-14 16:02             ` Takashi Iwai
2010-04-14 16:01     ` Takashi Iwai
2010-04-15 21:19       ` Éric Piel
2010-04-16  7:53         ` Takashi Iwai
2010-04-16 10:35           ` Frank Griffin
2010-04-16 10:33         ` Frank Griffin
2010-04-17 15:21         ` Frank Griffin

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=4BC5AD08.8040606@tremplin-utc.net \
    --to=eric.piel@tremplin-utc.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=ftg@roadrunner.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=rjw@sisk.pl \
    --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;
as well as URLs for NNTP newsgroup(s).