public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Arnaud Patard <apatard@mandriva.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: AD1986a
Date: Wed, 11 Jan 2006 14:15:30 +0100	[thread overview]
Message-ID: <m3k6d6vrbh.fsf@anduin.mandrakesoft.com> (raw)
In-Reply-To: <s5hlkxpgzb4.wl%tiwai@suse.de> (Takashi Iwai's message of "Mon, 09 Jan 2006 17:07:27 +0100")

Takashi Iwai <tiwai@suse.de> writes:

> At Wed, 04 Jan 2006 19:22:21 +0100,
> Arnaud Patard wrote:
>> 
>> Hi,
>> 
>> 
>> I have the same problem as
>> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1678
>> 
>> I though that it was only a matter of how the hda verbs were initialised
>> so I made a patch allowing to change the channel configuration
>> (http://people.mandriva.com/~apatard/ad1986a_2channel_mode_fix.patch).
>> Unfortunately, this was not enough. 
>
> This patch looks fine.

okay. I'll probably wait for the noise bug to be fixed before sending it
for inclusion.

>
>> Today, I've added this patch
>> http://people.mandriva.com/~apatard/dont_copy_front.patch which is
>> working but it's rather something ugly.
>> 
>> Moreover, I'm only able to test this with two speakers, so I don't know
>> if these patches are working with 4 or 6 channels setups.
>
> Surely won't work since you disabled the signal to surrounds :)

hm.. so, I'm probably wrong but I though that this patch was only
preventing to send front signal to others DACs when a stereo sound is
playing (thus playing 5.1 sound on 5.1 systems should still work).

>
>> Any hint on how to debug and fix this bug ?
>
> What is the exact status on your board?  Is only the front left
> channel noisy or silence?  I still don't figure out how the latter
> patch fixes the problem...

Only the front left is noisy. The front right is fine. About how this is
fixing the bug, I have only guesses. I think it's a matter of codec
setup and doing this fixes it for unknown reasons. I've even noticed
that loading a module with this patch and then replacing it with the
original module was working too. It's weird :(

Arnaud



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

  reply	other threads:[~2006-01-11 13:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 18:22 AD1986a Arnaud Patard
2006-01-09 16:07 ` AD1986a Takashi Iwai
2006-01-11 13:15   ` Arnaud Patard [this message]
2006-01-11 15:03     ` AD1986a 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=m3k6d6vrbh.fsf@anduin.mandrakesoft.com \
    --to=apatard@mandriva.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --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