From: "Simon Dunn" <sdunn@mpc-data.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Alsa Driver on Coldfire
Date: Fri, 18 Apr 2008 16:47:40 +0100 [thread overview]
Message-ID: <op.t9tctqwjhpbl6d@derby> (raw)
In-Reply-To: <20080418112340.GB19457@rakim.wolfsonmicro.main>
On Fri, 18 Apr 2008 12:23:41 +0100, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
>> I don't remember exact reason, too. It was so when ALSA was merged,
>> IIRC.
>
> I think I'd formed the impression from somewhere or other (probably
> related to Debian m68k) that it was that there were no relevant drivers
> for m68k that had been ported to ALSA so there wasn't much point
> building it. I could be misremembering, though.
>
> With regard to ColdFire I'm guessing that this is an embedded system?
> If so you might want to have a look at working with the ASoC framework
> (see sound/soc and Documentation/sound/alsa/soc).
Thanks for the info guys, I couldn't see any reason why alsa would be
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?
Cheers
Simon
--
Simon Dunn, Software Engineer
MPC Data Limited
e-mail: sdunn@mpc-data.co.uk
web: www.mpc-data.co.uk
tel: +44 (0) 1225 710600
fax: +44 (0) 1225 710601
ddi: +44 (0) 1225 710631
MPC Data Limited is a company registered in England and Wales with company
number 05507446
Registered Address: County Gate, County Way, Trowbridge, Wiltshire, BA14
7FJ
VAT no: 850625238
The information in this email and in the attached documents is
confidential and may be legally privileged. Any unauthorized review,
copying, disclosure or distribution is prohibited and may be unlawful. It
is intended solely for the addressee. Access to this email by anyone else
is unauthorized. If you are not the intended recipient, please contact the
sender by reply email and destroy all copies of the original message. When
addressed to our clients any opinions or advice contained in this email is
subject to the terms and conditions expressed in the governing contract.
next prev parent reply other threads:[~2008-04-18 15:47 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 [this message]
2008-04-18 17:11 ` 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=op.t9tctqwjhpbl6d@derby \
--to=sdunn@mpc-data.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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.