From: Richard Purdie <rpurdie@rpsys.net>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Pavel Machek <pavel@suse.cz>,
lenz@cs.wisc.edu, kernel list <linux-kernel@vger.kernel.org>,
Liam Girdwood <liam.girdwood@wolfsonmicro.com>
Subject: Re: ucb1x00 audio & zaurus touchscreen
Date: Wed, 22 Mar 2006 15:21:17 +0000 [thread overview]
Message-ID: <1143040877.6593.39.camel@localhost.localdomain> (raw)
In-Reply-To: <20060322135337.GA26357@flint.arm.linux.org.uk>
On Wed, 2006-03-22 at 13:53 +0000, Russell King wrote:
> On Wed, Mar 22, 2006 at 01:20:53PM +0100, Pavel Machek wrote:
> > First, I'd like to ask: what is status of ucb1x00 audio in 2.6? I do
> > have .c file here, but do not have corresponding header files...
>
> I never included the ucb1x00 audio patch into mainline because it
> depended on some obsolete SA11x0 OSS audio support, and I haven't had
> time to:
>
> (a) finish my SA11x0 ALSA audio support (the stuff which is in mainline
> is under the guise of being generic, but is actually completely ipaq
> specific.)
> (b) convert the ucb1x00 stuff to use this generic ALSA support.
>
> Plus there's issues surrounding where it should live (as ever). It
> would be stretched between drivers/mfd and sound/arm and would be very
> ARM specific.
I'd like to bring people's attention to the work done on ALSA ASoC.
Some information is available at:
http://www.rpsys.net/openzaurus/patches/alsa/info.html
(I think there are more supported codecs now.)
Patches are at:
http://www.rpsys.net/openzaurus/patches/alsa/
I've cc'd Liam in on this.
The PXA Zaurus machines are going down this route for audio support and
its proving extremely functional and stable. Mainline inclusion is
likely and there has been discussion about ASoC on the ALSA mailing
lists.
Richard
next prev parent reply other threads:[~2006-03-22 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 12:20 ucb1x00 audio & zaurus touchscreen Pavel Machek
2006-03-22 13:53 ` Russell King
2006-03-22 14:11 ` Pavel Machek
2006-03-22 15:21 ` Richard Purdie [this message]
2006-03-22 20:10 ` David Vrabel
2006-03-23 14:40 ` David Vrabel
2006-03-23 15:44 ` Russell King
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=1143040877.6593.39.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=lenz@cs.wisc.edu \
--cc=liam.girdwood@wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rmk+lkml@arm.linux.org.uk \
/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