Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Alan Alan <alanwww1@gmail.com>
Cc: alsa-devel@alsa-project.org, Wei Ni <wni@nvidia.com>
Subject: Re: ALSA patch Nvidia 8 channel hdmi audio
Date: Wed, 3 Jun 2009 02:00:54 +0200	[thread overview]
Message-ID: <200906030200.54455.marek.vasut@gmail.com> (raw)
In-Reply-To: <410e92830906021530l767478c4tae72c4b161583b6@mail.gmail.com>

On Wednesday 03 of June 2009 00:30:04 Alan Alan wrote:
> Thank's for the info.
> How can i contact him ?

He and alsa-devel mailing list are both in CC already, please preserve them 
there or fix your mailer.
>
>
> 2009/6/3 Marek Vasut <marek.vasut@gmail.com>
>
> > I'm not the author of the patch, CCing alsa-devel and the original
> > author.
> >
> > On Tuesday 02 of June 2009 23:58:26 Alan Alan wrote:
> > > Hi Marek !
> > >
> > > I just read your emailing with nvidia devs about alsa supporting 8
> >
> > channel
> >
> > > lpcm over hdmi.
> > >
> > > I checked it out an i have to tell it is working awsome, except for a
> > > few bugs:
> > >
> > > The channels are wrong mapped. Running a speakertest -Dhdmi -c6 gives
> > > the following result (first where it should sound)
> > > FL - FL
> > > C - RL
> > > FR - FR
> > > RR - LFE
> > > RL - C
> > >
> > > The other thing i realized that playback is limited to 16 bits 48 khz.
> > > I think the minimum which is supported by nvidia hardware is 24bits 96
> > > (or 192) khz.
> > > Why not ?
> > >
> > > Could you contact the devs as i don't know how to reach them.
> > >
> > > ps.: Mybe my build methot was not 100% ok ? I used 1.020 Alsa with the
> > > oatched nvidia.c file. Anyway the amplifier shows multichannel LPCM and
> > > that's great news.

  parent reply	other threads:[~2009-06-03  0:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <410e92830906021458x3d47a1d6jebba8bbe1150e76d@mail.gmail.com>
2009-06-02 22:22 ` ALSA patch Nvidia 8 channel hdmi audio Marek Vasut
     [not found]   ` <410e92830906021530l767478c4tae72c4b161583b6@mail.gmail.com>
2009-06-03  0:00     ` Marek Vasut [this message]
2009-06-03  7:14       ` Wei Ni
2009-06-03  7:22         ` Clemens Ladisch
2009-06-03  7:45         ` Takashi Iwai
2009-06-03  8:00         ` Alan Alan
2009-06-03  8:14           ` Takashi Iwai
2009-06-03  9:34             ` Alan Alan
2009-06-03  9:50               ` Takashi Iwai
2009-06-03 23:28                 ` Alan Alan
2009-06-03 23:38                   ` Takashi Iwai
     [not found]                     ` <410e92830906032318v4ed6987cr41c8f73a8a54a9e6@mail.gmail.com>
2009-06-04  6:33                       ` Takashi Iwai
2009-06-04  6:39                         ` Wei Ni
2009-06-04  6:50                           ` Takashi Iwai
2009-06-04 23:20                         ` Alan Alan
2009-06-05  2:38                           ` Wei Ni
2009-06-07 21:43                             ` Alan Alan
2009-06-08  5:20                               ` Takashi Iwai
2009-06-06  9:13                           ` Takashi Iwai
2009-06-03 10:25           ` Wei Ni
2009-06-03 11:02             ` Takashi Iwai
2009-06-04  6:05               ` Wei Ni
2009-06-04  6:29                 ` Takashi Iwai
2009-06-05  4:28                   ` Wu Fengguang
2009-06-05  5:40                     ` Takashi Iwai
2009-06-05  6:14                       ` Wu Fengguang
2009-06-03 11:07             ` Alan Alan
2009-07-01  4:47 Pau Rodriguez-Estivill

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=200906030200.54455.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=alanwww1@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=wni@nvidia.com \
    /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