From: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Jarkko Nikula <jhnikula@gmail.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: Thu, 1 Apr 2010 21:45:49 +0200 [thread overview]
Message-ID: <201004012145.51284.jkrzyszt@tis.icnet.pl> (raw)
In-Reply-To: <20100401122520.GF32025@rakim.wolfsonmicro.main>
Thursday 01 April 2010 14:25:21 Mark Brown napisał(a):
> On Mon, Mar 29, 2010 at 02:14:51PM +0200, Janusz Krzysztofik wrote:
> > I should have mention that I was already aware of your patch; applied
> > alone, it didn't solve the problem for me. However, when configuring ALSA
> > with debugging turned off, I have to use both patches, yours and mine, in
> > order to get things working.
>
> 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.
Thanks,
Janusz
--
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-01 19:45 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 [this message]
2010-04-02 8:10 ` Jarkko Nikula
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=201004012145.51284.jkrzyszt@tis.icnet.pl \
--to=jkrzyszt@tis.icnet.pl \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jhnikula@gmail.com \
--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