From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: i.MX SDMA support
Date: Wed, 11 Aug 2010 14:43:52 +0100 [thread overview]
Message-ID: <1281534232.3080.112.camel@odin> (raw)
In-Reply-To: <20100811084213.GN27749@pengutronix.de>
On Wed, 2010-08-11 at 10:42 +0200, Sascha Hauer wrote:
> On Tue, Aug 10, 2010 at 03:07:43PM +0100, Liam Girdwood wrote:
> > On Tue, 2010-08-10 at 15:15 +0200, Sascha Hauer wrote:
> >
> > > I just looked at the i.MX part in the multi-component update and this
> > > is currently far from being in a working state, so there's still some
> > > work to do before thinking about possible conflicts...
> >
> > Ok, I don't think it's that far off. Everything builds for i.MX and all
> > components should register. The part I can't test is the component
> > probe() and playback/capture.
> >
> > Have you seen an oops ?
>
> Many of them, yes ;)
>
> The following patch puts i.MX (nearly) back into business.
>
> Sascha
>
Both applied. I'll do the string change for SSI shortly.
Thanks
Liam
next prev parent reply other threads:[~2010-08-11 13:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 9:11 i.MX SDMA support Sascha Hauer
2010-08-09 10:47 ` Liam Girdwood
2010-08-09 12:19 ` Sascha Hauer
2010-08-09 14:09 ` Mark Brown
2010-08-10 13:15 ` Sascha Hauer
2010-08-10 13:39 ` Mark Brown
2010-08-10 14:07 ` Liam Girdwood
2010-08-11 8:42 ` Sascha Hauer
2010-08-11 10:09 ` Liam Girdwood
2010-08-11 11:59 ` Sascha Hauer
2010-08-11 12:32 ` Liam Girdwood
2010-08-11 13:43 ` Liam Girdwood [this message]
2010-08-11 8:44 ` Sascha Hauer
2010-08-11 10:24 ` Liam Girdwood
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=1281534232.3080.112.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=s.hauer@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).