mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Pierre Ossman <drzeus@drzeus.cx>,
	Jaroslav Kysela <perex@perex.cz>,
	ALSA devel <alsa-devel@alsa-project.org>,
	mulix@mulix.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [alsa-devel] looping S/PDIF data
Date: Tue, 01 Jul 2008 12:16:53 +0200	[thread overview]
Message-ID: <s5hzlp1ewoa.wl%tiwai@suse.de> (raw)
In-Reply-To: <48692415.3070204@keyaccess.nl>

At Mon, 30 Jun 2008 20:21:09 +0200,
Rene Herman wrote:
> 
> On 30-06-08 19:11, Pierre Ossman wrote:
> 
> > On Sat, 21 Jun 2008 14:14:38 +0200
> > Rene Herman <rene.herman@keyaccess.nl> wrote:
> > 
> >> On 21-06-08 01:09, Pierre Ossman wrote:
> >>
> >>> trident: pause s/pdif output
> >>>
> >>> Stop the S/PDIF DMA engine and output when the device is told to pause.
> >>> It will keep on looping the current buffer contents if this isn't done.
> >>>
> >>> Signed-off-by: Pierre Ossman <drzeus@drzeus.cx>
> >> Verified to fix the reported pause problem on a 4DWaveNX (and indeed to 
> >> not affect a 4DWaveDX). The Trident SPDIF doesn't seem capable of 44100 
> >> which for me means it's not all that useful but you no doubt know 
> >> yourself that/if it is for you...
> >>
> >> Tested-by: Rene Herman <rene.herman@gmail.com>
> > 
> > 
> > Sooo.... ack? nak? limbo?
> 
> ... come on shake your body baby, do the limbo, I know ...
> 
> Your fix is commit f19a62ecba9d0963cee2b673f0ad34917b5e57ad in the 
> "sound-2.6" git repo (Takashi Iwai's tree), branch "master", at
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
> 
> also viewable at:
> 
> http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=commit;h=f19a62ecba9d0963cee2b673f0ad34917b5e57ad
> 
> That commit is pre the 1.0.17-rc3 release/tag so it's in. Will find its 
> way into the kernel during the next merge window no doubt...

Yep.  Sorry, I simply forgot to send ACK message.


thanks,

Takashi

  parent reply	other threads:[~2008-07-01 10:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-31  9:26 Pierre Ossman
2008-06-02  8:00 ` Takashi Iwai
2008-06-17 19:55 ` Pierre Ossman
2008-06-18  7:24   ` Rene Herman
2008-06-19 10:05     ` [alsa-devel] " Takashi Iwai
2008-06-19 12:39       ` Jaroslav Kysela
2008-06-19 12:48         ` Takashi Iwai
2008-06-20 19:45           ` Pierre Ossman
2008-06-20 19:52             ` Rene Herman
2008-06-20 22:00               ` Pierre Ossman
2008-06-20 22:23                 ` Rene Herman
2008-06-20 23:09                   ` Pierre Ossman
2008-06-21 12:14                     ` Rene Herman
2008-06-30 17:11                       ` Pierre Ossman
2008-06-30 18:21                         ` Rene Herman
2008-06-30 19:22                           ` Pierre Ossman
2008-07-01 10:16                           ` Takashi Iwai [this message]
2008-06-19 23:02         ` Pierre Ossman
2008-06-19 10:05     ` 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=s5hzlp1ewoa.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=drzeus@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mulix@mulix.org \
    --cc=perex@perex.cz \
    --cc=rene.herman@keyaccess.nl \
    /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

all inboxes | Powered by JetHome®