From: Takashi Iwai <tiwai@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Liam Girdwood <liam@exize.com>, Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>,
Liam Girdwood <liam.girdwood@wolfsonmicro.com>
Subject: Re: PATCH: AC97 updates from 2.4
Date: Mon, 14 Jul 2003 17:22:29 +0200 [thread overview]
Message-ID: <s5h4r1puo96.wl@alsa2.suse.de> (raw)
In-Reply-To: <1057960677.20636.56.camel@dhcp22.swansea.linux.org.uk>
At 11 Jul 2003 22:57:58 +0100,
Alan Cox wrote:
>
> On Gwe, 2003-07-11 at 21:26, Liam Girdwood wrote:
> > 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.
>
> It would be great if we can get the same plugin API for both, although that
> may be trickier since the mixer side is quite different
i'm afraid this, too. both use completely different ac97 structs.
although it's possible to define an API which works for both drivers,
it would be a minimal subset, just only to read/write ac97 registers.
is the touchscreen plugin already in the latest 2.4 tree?
then i'd like to take a look and try to implement a tentative plugin
API.
--
Takashi Iwai <tiwai@suse.de> SuSE Linux AG - www.suse.de
ALSA Developer ALSA Project - www.alsa-project.org
next prev parent reply other threads:[~2003-07-14 15:08 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
2003-07-11 21:57 ` Alan Cox
2003-07-14 15:22 ` Takashi Iwai [this message]
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=s5h4r1puo96.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=liam.girdwood@wolfsonmicro.com \
--cc=liam@exize.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).