From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Simon Dunn <sdunn@mpc-data.co.uk>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: Alsa Driver on Coldfire
Date: Fri, 18 Apr 2008 18:11:52 +0100 [thread overview]
Message-ID: <20080418171152.GA14011@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <op.t9tctqwjhpbl6d@derby>
On Fri, Apr 18, 2008 at 04:47:40PM +0100, Simon Dunn wrote:
> On Fri, 18 Apr 2008 12:23:41 +0100, Mark Brown
> excluded. Oh and thanks for the tip re the system on chip, I'll have
> a look into that though the kernel version we're working with is
> 2.6.10 and doesn't include it 'off the shelf'.
> Can't imagine it would be too difficult to merge across unless anyone
> knows different?
Tedious more than hard - there was a change in the ALSA APIs from using
typedefs to using 'struct foo' which creates a lot of code churn but is
not at all difficult to deal with. Other than that things should be
pretty straightforward.
prev parent reply other threads:[~2008-04-18 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 10:02 Alsa Driver on Coldfire Simon Dunn
2008-04-18 10:22 ` Takashi Iwai
2008-04-18 11:23 ` Mark Brown
2008-04-18 15:47 ` Simon Dunn
2008-04-18 17:11 ` Mark Brown [this message]
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=20080418171152.GA14011@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=sdunn@mpc-data.co.uk \
--cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.