linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Habets <errandir_news@mph.eclipse.co.uk>
To: Adrian Bunk <bunk@stusta.de>, benh@kernel.crashing.org
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [Alsa-devel] RFC: OSS driver removal, a slightly different approach
Date: Fri, 20 Jan 2006 11:54:43 +0000	[thread overview]
Message-ID: <20060120115443.GA16582@palantir8> (raw)
In-Reply-To: <20060119174600.GT19398@stusta.de>

It seems to me we can already get rid of sound/oss/dmasound now.
I cannot find anything refering to it anymore, and the ALSA powermac
driver is being maintained.

Martin

On Thu, Jan 19, 2006 at 06:46:00PM +0100, Adrian Bunk wrote:
> My proposal to remove OSS drivers where ALSA drivers for the same 
> hardware exists had two reasons:
> 
> 1. remove obsolete and mostly unmaintained code
> 2. get bugs in the ALSA drivers reported that weren't previously
>    reported due to the possible workaround of using the OSS drivers
> 
> I'm slowly getting more and more reports for the second case.
> 
> 
> The list below divides the OSS drivers into the following three 
> categories:
> 1. ALSA drivers for the same hardware
> 2. ALSA drivers for the same hardware with known problems
> 3. no ALSA drivers for the same hardware
> 
> 
> My proposed timeline is:
> - shortly before 2.6.16 is released:
>   adjust OBSOLETE_OSS_DRIVER dependencies to match exactly the
>   drivers under 1.
> - from the release of 2.6.16 till the release of 2.6.17:
>   approx. two months for users to report problems with the ALSA
>   drivers for the same hardware
> - after the release of 2.6.17 (and before 2.6.18):
>   remove the subset of drivers marked at OBSOLETE_OSS_DRIVER without
>   known regressions in the ALSA drivers for the same hardware
> 
> 
> To make a long story short:
> 
> If you are using an OSS driver because the ALSA driver doesn't work 
> equally well on your hardware, send me an email with a bug number in the 
> ALSA bug tracking system now.

  parent reply	other threads:[~2006-01-20 11:55 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19 17:46 RFC: OSS driver removal, a slightly different approach Adrian Bunk
2006-01-19 18:22 ` Lee Revell
2006-01-19 18:28   ` Adrian Bunk
2006-01-19 18:39     ` Lee Revell
2006-01-19 19:44       ` Adrian Bunk
2006-01-19 20:22         ` Frédéric L. W. Meunier
2006-01-19 20:45           ` Lee Revell
2006-01-19 22:03             ` Alistair John Strachan
2006-01-20 14:19               ` Jan Engelhardt
2006-01-21  0:30                 ` Lee Revell
2006-01-21  9:06                   ` Jan Engelhardt
2006-01-19 18:54     ` [Alsa-devel] " Lee Revell
2006-01-19 19:04       ` Takashi Iwai
2006-01-19 19:01         ` Lee Revell
2006-01-19 22:09           ` Alan Cox
2006-01-20 10:20             ` Takashi Iwai
2006-01-20 13:14               ` Alan Cox
2006-01-20 14:30                 ` Takashi Iwai
2006-01-19 19:13         ` David Vrabel
2006-01-19 22:11       ` Alan Cox
2006-01-19 21:28     ` Alan Cox
2006-01-19 18:47 ` [Alsa-devel] " Peter Zubaj
2006-01-20 14:25   ` Jan Engelhardt
2006-01-20 14:56     ` Takashi Iwai
2006-01-20 16:30       ` Jan Engelhardt
2006-01-20 17:44         ` Peter Zubaj
2006-01-21  8:58           ` Jan Engelhardt
2006-01-22 15:34             ` Jaroslav Kysela
2006-01-21  2:27     ` Lee Revell
2006-01-21  9:01       ` Jan Engelhardt
2006-01-19 20:24 ` Krzysztof Halasa
2006-01-19 20:43   ` [Alsa-devel] " Lee Revell
2006-01-19 21:50     ` Bill Nottingham
2006-01-19 22:18       ` Adrian Bunk
2006-01-19 22:18     ` Alan Cox
2006-01-19 22:38       ` Lee Revell
2006-01-19 22:42       ` Dave Jones
2006-01-19 22:51         ` Lee Revell
2006-01-20  1:13           ` Alan Cox
2006-01-20  1:34             ` Dave Jones
2006-01-20 11:20               ` Takashi Iwai
2006-01-21  0:29                 ` Lee Revell
2006-01-21  0:57                   ` Adrian Bunk
2006-01-21  1:03                     ` Lee Revell
2006-01-21  1:01             ` Lee Revell
2006-01-20  8:21     ` Dag Nygren
2006-01-21  3:52       ` Lee Revell
2006-01-19 22:21   ` Alan Cox
2006-01-19 22:45     ` Adrian Bunk
2006-01-20  2:55       ` Erik Andersen
2006-01-21  1:53         ` [Alsa-devel] " Lee Revell
2006-01-19 22:45     ` Lee Revell
2006-01-20  3:46   ` Rene Herman
2006-01-20  7:04     ` [Alsa-devel] " Brent Cook
2006-01-21  0:55       ` Stuffed Crust
2006-01-20 14:32     ` Jan Engelhardt
2006-01-20  8:25   ` [Alsa-devel] " Clemens Ladisch
2006-01-20  9:53     ` Martin Langer
2006-01-20 12:41   ` Jamie Heilman
2006-01-20 16:09   ` Bob Tracy
2006-01-19 21:06 ` Jesper Juhl
2006-01-19 21:43   ` Adrian Bunk
2006-01-20 11:54 ` Martin Habets [this message]
2006-01-20 19:04   ` [Alsa-devel] " Adrian Bunk
2006-01-20 21:29     ` Olaf Hering
2006-01-20 23:16       ` Benjamin Herrenschmidt
2006-01-20 23:22         ` Ben Collins
2006-01-23 12:20           ` Takashi Iwai
2006-01-23 13:12             ` Ben Collins
2006-01-20 23:15     ` Benjamin Herrenschmidt
2006-01-21 21:05 ` Ralf Baechle
2006-01-23 14:11   ` Dan Malek
2006-01-23 15:06     ` Jordan Crouse
2006-01-25  2:47 ` Martin Michlmayr

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=20060120115443.GA16582@palantir8 \
    --to=errandir_news@mph.eclipse.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=benh@kernel.crashing.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).