From: Liam Girdwood <liam@exize.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, torvalds@transmeta.com,
Liam Girdwood <liam.girdwood@wolfsonmicro.com>
Subject: Re: PATCH: AC97 updates from 2.4
Date: 11 Jul 2003 21:26:47 +0100 [thread overview]
Message-ID: <1057955207.3607.25.camel@odin> (raw)
In-Reply-To: <20030711184706.GD16037@gtf.org>
On Fri, 2003-07-11 at 19:47, Jeff Garzik wrote:
> On Fri, Jul 11, 2003 at 07:09:35PM +0100, Alan Cox wrote:
> >
> > This deals with several things
> > - Codecs that think they are modems but are not
> > - Abstracting modem detection out of drivers
> > - Abstracting digital switching out of drivers
> > - Codecs that have no volume control
> > - Codec plugins for specific setups
> > - Codec plugins for things like touchscreen/batmon on AC97
> > - More codec handlers
> >
> > The plugin API is intentionally modelled on the other driver_register
> > type interfaces.
>
> Adding another relevant point:
> Only weirdos like me use the old OSS drivers, so this patch does not
> affect the current (rather than deprecated) audio drivers.
>
I would eventually like to see something similar to this in ALSA.
I wrote the touchscreen driver plugin and an ALSA AC97 plugin API will
probably be needed before this time next year to keep Linux up to date
in the PDA/Tablet/Portable space. Eventually we may need an I2S and/or
Azalia (next gen audio) API layer for such devices.
I intend to speak to the ALSA guys as soon as the OSS plugin driver has
stabilised.
Cheers
Liam
next prev parent reply other threads:[~2003-07-11 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 18:09 PATCH: AC97 updates from 2.4 Alan Cox
2003-07-11 18:47 ` Jeff Garzik
2003-07-11 20:26 ` Liam Girdwood [this message]
2003-07-11 21:57 ` Alan Cox
2003-07-14 15:22 ` Takashi Iwai
2003-07-14 15:37 ` Alan Cox
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=1057955207.3607.25.camel@odin \
--to=liam@exize.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=liam.girdwood@wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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.