From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Muli Ben-Yehuda <mulix@mulix.org>, Jos Hulzink <jos@hulzink.net>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: OSS: cleanup or throw away
Date: Mon, 22 Mar 2004 23:17:18 +0000 [thread overview]
Message-ID: <20040322231718.G11212@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040322222329.GW16746@fs.tum.de>; from bunk@fs.tum.de on Mon, Mar 22, 2004 at 11:23:29PM +0100
On Mon, Mar 22, 2004 at 11:23:29PM +0100, Adrian Bunk wrote:
> On Tue, Mar 23, 2004 at 12:03:27AM +0200, Muli Ben-Yehuda wrote:
> > On Mon, Mar 22, 2004 at 10:59:21PM +0100, Adrian Bunk wrote:
> > > Wouldn't it be better to get the ALSA drivers working in such cases?
> >
> > It would; but until they do, ditching OSS is a regression.
> >...
>
> Clearly.
>
> Ditching OSS at the beginning of 2.7 will give several years to identify
> and fix such regressions.
Seriously, ALSA has some issues at the moment which OSS doesn't have.
The main one is that OSS does not require mmap() access, whereas ALSA
native does at present - and there are architectures where the ALSA
method of mmap() both the ring buffer and the control data does not
work.
These issues aren't simple to resolve - as can be seen from the
recent lkml threads on the subject. I've been seriously considering
submitting the existing OSS drivers I have here for ARM hardware
instead of trying to convert them to ALSA drivers first, and
considering whether I should be writing new OSS drivers in
preference to ALSA drivers.
That's not to say I don't want to see ALSA progress though - which is
why I'm working to try to get these issues resolved.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-03-22 23:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 18:55 OSS: cleanup or throw away Jos Hulzink
2004-03-22 20:22 ` Muli Ben-Yehuda
2004-03-22 21:32 ` Jos Hulzink
2004-03-22 21:53 ` Muli Ben-Yehuda
2004-03-22 21:59 ` Adrian Bunk
2004-03-22 22:03 ` Muli Ben-Yehuda
2004-03-22 22:23 ` Adrian Bunk
2004-03-22 23:17 ` Russell King [this message]
2004-03-23 8:23 ` Gábor Lénárt
2004-03-23 10:35 ` Jos Hulzink
2004-03-23 17:18 ` Markus Hästbacka
2004-03-23 17:29 ` Jaroslav Kysela
2004-03-23 17:49 ` Jochen Hein
2004-03-23 19:39 ` Markus Hästbacka
2004-03-24 21:00 ` Jos Hulzink
2004-03-22 21:57 ` Adrian Bunk
2004-03-22 22:27 ` Diego Calleja García
2004-03-22 22:54 ` Luiz Fernando Capitulino
2004-03-23 6:27 ` Jos Hulzink
2004-03-24 17:02 ` Jos Hulzink
[not found] <1CD8E-65d-33@gated-at.bofh.it>
[not found] ` <1CFMG-8wf-61@gated-at.bofh.it>
[not found] ` <1CGft-ry-3@gated-at.bofh.it>
2004-03-23 17:16 ` Bill Davidsen
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=20040322231718.G11212@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=bunk@fs.tum.de \
--cc=jos@hulzink.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@mulix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox