Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Binder <phoenix.diablo@googlemail.com>
To: alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>,
	Raymond Yau <superquad.vortex2@gmail.com>,
	alex.baldacchino.alsasub@gmail.com, haraldwelte@viatech.com,
	lydiawang <lydiawang@viatech.com.cn>
Subject: Re: Major reworks on patch_via.c (TESTERS WANTED)
Date: Wed, 22 Jun 2011 10:02:25 +0200	[thread overview]
Message-ID: <201106221002.26119.phoenix.diablo@gmail.com> (raw)
In-Reply-To: <s5hvcw04k50.wl%tiwai@suse.de>

Am Montag, 20. Juni 2011, 17:06:51 schrieb Takashi Iwai:
> Hi,
> 
> as there have many problems reported for VIA codecs, I started looking
> at the driver code, and decided to rework on it.
> 
> The current development is found in sound git tree topic/via-cleanup
> branch:
>    git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
> 
> You can pull into the latest Linus tree from topic/via-cleanup
> branch:
>    # this is the vanilla tree
>    % cd linux-2.6
>    % git pull \
>       git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git \
>       topic/via-cleanup
> 
> A good thing is that a fair amount of code reduction is done there:
> 
> % git diff HEAD..topic/via-cleanup --stat sound/pci/hda/patch_via.c
>  sound/pci/hda/patch_via.c | 5892
> +++++++++++---------------------------------- 1 files changed, 1453
> insertions(+), 4439 deletions(-)
> 
> But, the driver isn't tested with real machines, yet.  That is, I need
> testers with real machines.
> 
> Could VIA machine owners take a look at these commits and test it if
> possible?  Especially, I'd like to know whether the headphone
> auto-mute works in this form or not.

I will have a look at this.
On a related note, I am experiencing a bug regarding SPDIF output as  
described here: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4330
If this could be fixed within this rework, it would be greatly appreciated.

> FWIW, the branch was merged to sound-unstable tree, so you can build
> from alsa-driver-unstable snapshot tarball if you'd like to build
> external modules without the kernel tree and git-merge.
>  
> ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-un
> stable-snapshot.tar.gz
> 
> 
> Also, if anyone has alsa-info.sh outputs of VIA codecs, please let me
> know.  It'd be very helpful for debugging, since I can check it via
> hda-emu with alsa-info.sh output.  For now, I have the files of only
> VT1702, VT1708S, VT1718S, VT1828S and VT2020 codecs.  The alsa-info.sh
> outputs of other VIA codecs would be greatly appreciated.

You can find the info-alsa.sh output for my VIA VT1708B 8-Ch at
http://www.alsa-project.org/db/?f=05281895eb77de2a22257e27fb2ecab1a959cb92
 
> thanks,
> 
> Takashi
--
Jan Binder

  parent reply	other threads:[~2011-06-22  8:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20 15:06 Major reworks on patch_via.c (TESTERS WANTED) Takashi Iwai
2011-06-20 15:16 ` Takashi Iwai
2011-06-21 10:01 ` David Henningsson
2011-06-21 11:01   ` Takashi Iwai
2011-06-21 11:38     ` David Henningsson
2011-06-21 12:28       ` Takashi Iwai
2011-06-22  8:02 ` Jan Binder [this message]
2011-06-22  8:52   ` Takashi Iwai
2011-06-22 14:28 ` Takashi Iwai
2011-07-02 16:00   ` alex dot baldacchino dot alsasub at gmail dot com
2011-07-04 12:55     ` Takashi Iwai
2011-07-04 14:02       ` Takashi Iwai
2011-07-06  0:55         ` alex dot baldacchino dot alsasub at gmail dot com
2011-07-06  0:49       ` alex dot baldacchino dot alsasub at gmail dot com
2011-07-04 19:37   ` Jan Binder
2011-07-05  5:25     ` Takashi Iwai
2011-07-05  9:20       ` Raymond Yau
2011-07-06  0:58       ` alex dot baldacchino dot alsasub at gmail dot com
2011-07-15  6:03         ` 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=201106221002.26119.phoenix.diablo@gmail.com \
    --to=phoenix.diablo@googlemail.com \
    --cc=alex.baldacchino.alsasub@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=haraldwelte@viatech.com \
    --cc=lydiawang@viatech.com.cn \
    --cc=superquad.vortex2@gmail.com \
    --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