From: "Simon Dunn" <sdunn@mpc-data.co.uk>
To: alsa-devel@alsa-project.org
Subject: Alsa Driver on Coldfire
Date: Fri, 18 Apr 2008 11:02:56 +0100 [thread overview]
Message-ID: <op.t9swu605hpbl6d@derby> (raw)
Hi
I've been given the job of writing a sound card driver using the alsa
architecture for a
development platform that uses a coldfire chip.
The first thing I came across was a chunky 'if !M68K' in sound/Kconfig,
which excludes all
the alsa components. I can't find any reason for this in the mailing list
archives or
on the web in general, so I'm wondering if anybody knows why the M68K
architecture is
excluded?
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 reply other threads:[~2008-04-18 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 10:02 Simon Dunn [this message]
2008-04-18 10:22 ` Alsa Driver on Coldfire Takashi Iwai
2008-04-18 11:23 ` Mark Brown
2008-04-18 15:47 ` Simon Dunn
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.t9swu605hpbl6d@derby \
--to=sdunn@mpc-data.co.uk \
--cc=alsa-devel@alsa-project.org \
/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.