From: Adrian Bunk <bunk@stusta.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
perex@suse.cz, Olaf Hering <olh@suse.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: OSS driver removal, 2nd round
Date: Mon, 3 Jul 2006 21:42:44 +0200 [thread overview]
Message-ID: <20060703194244.GA26941@stusta.de> (raw)
In-Reply-To: <1151927579.13828.6.camel@localhost.localdomain>
On Mon, Jul 03, 2006 at 09:52:59PM +1000, Benjamin Herrenschmidt wrote:
>
> > DMASOUND_PMAC
> > - Olaf Hering regarding regressions in SND_POWERMAC:
> > Some tumbler models work only after one plug/unplug cycle of
> > the headphone. early powerbooks report/handle the mute settings
> > incorrectly. there are likely more bugs.
>
> dmasound_pmac is crippled with bugs too... We should look at reported
> bug reports on snd-powermac (and snd-aoa which replaces the later for
> recent machines) and kill dmasound-pmac. I'm ok with that. snd-aoa is
> the only one to be properly maintained anyway, we'll add support for
> older machines to it over time and hopefully, it's a much saner codebase
> in the first place so handling weird machines regressions will be
> easier.
Thanks for this information.
I'll include DMASOUND_PMAC in the list of OSS drivers that might be
removed in this round (if people report regressions in the ALSA drivers,
this can still be undone (if someone observes such a regression, he
should send me the bug number in the ALSA BTS (this is also what
will be written in the help text of the OSS_OBSOLETE_DRIVER option))).
> Ben.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2006-07-03 19:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 19:21 OSS driver removal, 2nd round Adrian Bunk
2006-06-30 15:48 ` Ralf Baechle
2006-06-30 16:13 ` [Alsa-devel] " James Courtier-Dutton
2006-06-30 16:31 ` Olivier Galibert
2006-06-30 21:29 ` Lee Revell
2006-06-30 21:34 ` Arjan van de Ven
2006-06-30 21:54 ` Lee Revell
2006-07-01 8:54 ` Jan Engelhardt
2006-07-01 13:54 ` Lee Revell
2006-07-01 22:51 ` Jan Engelhardt
[not found] ` <200607010042.15765.ismail@pardus.org.tr>
2006-06-30 21:56 ` Lee Revell
[not found] ` <200607010249.05140.ismail@pardus.org.tr>
2006-07-03 22:38 ` Bill Davidsen
2006-07-05 7:27 ` Stefan Smietanowski
2006-07-05 19:34 ` Lee Revell
2006-07-05 21:56 ` Alan Cox
2006-07-01 7:31 ` [Alsa-devel] " Olivier Galibert
2006-07-01 7:43 ` James Courtier-Dutton
2006-07-01 13:52 ` Lee Revell
2006-07-02 6:55 ` James Courtier-Dutton
2006-07-02 9:58 ` Jan Engelhardt
2006-07-02 15:28 ` Lee Revell
2006-07-02 21:08 ` Jan Engelhardt
2006-07-02 21:16 ` Lee Revell
2006-07-03 9:26 ` Jan Engelhardt
2006-07-05 7:29 ` Stefan Smietanowski
2006-07-01 9:26 ` Jaroslav Kysela
2006-07-01 16:01 ` Adrian Bunk
2006-07-01 23:12 ` Adrian Bunk
2006-07-03 11:52 ` Benjamin Herrenschmidt
2006-07-03 19:42 ` Adrian Bunk [this message]
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=20060703194244.GA26941@stusta.de \
--to=bunk@stusta.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
--cc=perex@suse.cz \
/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