public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: rpurdie@rpsys.net, lenz@cs.wisc.edu,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: ucb1x00 audio & zaurus touchscreen
Date: Wed, 22 Mar 2006 15:11:26 +0100	[thread overview]
Message-ID: <20060322141126.GA23975@elf.ucw.cz> (raw)
In-Reply-To: <20060322135337.GA26357@flint.arm.linux.org.uk>

On St 22-03-06 13:53:37, 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:

Do you still have copy, somewhere? I have something here, but it does
not even compile due to missing headers.

> (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.)

Do you mean ./sound/arm/sa11xx-uda1341.c here? Do you have any patches?

> (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.

								Pavel
-- 
Picture of sleeping (Linux) penguin wanted...

  reply	other threads:[~2006-03-22 14:11 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 [this message]
2006-03-22 15:21   ` Richard Purdie
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=20060322141126.GA23975@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=lenz@cs.wisc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /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