From: Jarkko Nikula <jhnikula@gmail.com>
To: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Jaroslav Kysela <perex@perex.cz>
Subject: Re: [RFC][PATCH] ASoC: OMAP: Fix capture pointer handling for OMAP1510 to work correctly with recent ALSA PCM code
Date: Fri, 2 Apr 2010 11:10:36 +0300 [thread overview]
Message-ID: <20100402111036.3de0e6c7.jhnikula@gmail.com> (raw)
In-Reply-To: <201004012145.51284.jkrzyszt@tis.icnet.pl>
On Thu, 1 Apr 2010 21:45:49 +0200
Janusz Krzysztofik <jkrzyszt@tis.icnet.pl> wrote:
> Thursday 01 April 2010 14:25:21 Mark Brown napisał(a):
> > Any updates on this one?
>
> Hi Mark,
>
> I can only confirm that using 2.6.34-rc3, already containing Jarkko's patch, I
> still have to apply mine to get sound working on Amstrad Delta.
>
> However, I still don't understand what happened to capture stream handling
> that it stopped working for me.
>
While I either don't understand the broke I think there's something in
the capture DMA pointer which shows up only now. So I'm fine if you
Janusz like to get your patch in and can have my ack. Or do you want to
debug it further?
Acked-by: Jarkko Nikula <jhnikula@gmail.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-02 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 20:29 [RFC][PATCH] ASoC: OMAP: Fix capture pointer handling for OMAP1510 to work correctly with recent ALSA PCM code Janusz Krzysztofik
2010-03-29 8:54 ` Jarkko Nikula
2010-03-29 12:14 ` Janusz Krzysztofik
2010-04-01 12:25 ` Mark Brown
2010-04-01 19:45 ` Janusz Krzysztofik
2010-04-02 8:10 ` Jarkko Nikula [this message]
2010-04-02 9:36 ` Mark Brown
2010-04-02 10:51 ` Janusz Krzysztofik
2010-04-02 16:12 ` Mark Brown
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=20100402111036.3de0e6c7.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-omap@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@nokia.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