Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: alsa-user@lists.sourceforge.net, intel-gfx@lists.freedesktop.org,
	Lennart Poettering <mznyfn@0pointer.de>,
	shane-alsa@csy.ca, alsa-devel@alsa-project.org
Subject: Re: [Intel-gfx] Problems with HDMI audio on Intel DG45FC	motherboard
Date: Sun, 08 Nov 2009 11:41:39 +0100	[thread overview]
Message-ID: <s5h1vk9qows.wl%tiwai@suse.de> (raw)
In-Reply-To: <20091021013812.GB7279@localhost>

At Wed, 21 Oct 2009 09:38:12 +0800,
Wu Fengguang wrote:
> 
> On Wed, Oct 21, 2009 at 06:37:58AM +0800, David Härdeman wrote:
> > On Tue, Oct 20, 2009 at 09:26:00AM +0800, Wu Fengguang wrote:
> > >On Thu, Oct 15, 2009 at 01:40:53AM +0800, David Härdeman wrote:
> > >> ii) Is there any documentation somewhere on how this mapping is supposed 
> > >> to be performed in user space?
> > >
> > >I think Shane has provided a good example for you in another email :)
> > >Here are more descriptions for the route plugin:
> > 
> > So perhaps I should still file a bug with the ALSA bugtracker asking for 
> > the default ALSA userspace to include a channel mapping along Shane's 
> > recommendation?
> 
> That would be good. I'm not sure if PulseAudio need a separate fix.
> (Lennart CCed).

Some ideas in my mind (and experimental patches in my archive) for
exposing the channel mapping to user-space.  But I've had too little
time to work on it until now.  Will try to find some time again.

Also, for remapping the channels, we can write another plugin that
is more optimized than the route plugin.


thanks,

Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  parent reply	other threads:[~2009-11-08 10:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091011214513.GB12771@hardeman.nu>
     [not found] ` <20091014015455.GI13364@zhen-devel.sh.intel.com>
     [not found]   ` <20091014020044.GA10032@localhost>
     [not found]     ` <20091014174053.GA31149@hardeman.nu>
2009-10-20  1:26       ` [Intel-gfx] Problems with HDMI audio on Intel DG45FC motherboard Wu Fengguang
2009-10-20 22:37         ` David Härdeman
2009-10-21  1:38           ` Wu Fengguang
2009-10-25 22:31             ` David Härdeman
2009-10-27  8:57               ` Wu Fengguang
2009-11-08 10:41             ` Takashi Iwai [this message]
2009-10-20 22:43         ` Shane W
2009-10-26 23:11           ` David Härdeman
2009-10-27  9:08             ` Wu Fengguang
2009-10-27  3:28           ` Wu Fengguang
     [not found]           ` <2da93e57183a480510f5b67c24ba11d0.squirrel@www.hardeman.nu>
     [not found]             ` <20091028044621.GA18453@localhost>
     [not found]               ` <0323437dc2fc33a33ec9285505a36434.squirrel@www.hardeman.nu>
     [not found]                 ` <20091029094602.GA3589@localhost>
     [not found]                   ` <20091029222932.GA1109@hardeman.nu>
2009-11-02  9:11                     ` Wu Fengguang
     [not found]                       ` <20091105004655.GA25580@hardeman.nu>
     [not found]                         ` <20091105074731.GB3016@localhost>
     [not found]                           ` <b3e8c2bfd1e1ff82a1e68a4e03950238.squirrel@www.hardeman.nu>
2009-11-05  9:22                             ` Wu Fengguang
     [not found]                               ` <5a703067d8395f3f80e4fb6a5227d117.squirrel@www.hardeman.nu>
2009-11-11  7:05                                 ` Wu Fengguang
2009-11-12  9:49                                   ` Paul Fertser

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=s5h1vk9qows.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=fengguang.wu@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mznyfn@0pointer.de \
    --cc=shane-alsa@csy.ca \
    /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