public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: "Diego Calleja García" <diegocg@teleline.es>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: OSS: cleanup or throw away
Date: Tue, 23 Mar 2004 12:16:41 -0500	[thread overview]
Message-ID: <406070F9.2070900@tmr.com> (raw)
In-Reply-To: <1CGft-ry-3@gated-at.bofh.it>

Diego Calleja García wrote:
> El Mon, 22 Mar 2004 22:57:09 +0100 Adrian Bunk <bunk@fs.tum.de> escribió:
> 
> 
>>OSS will stay in 2.6 (2.6 is a stable kernel series) but it will most
>>likely be removed in 2.7.
> 
> 
> Personally, as an user, I'd like to have the OSS drivers which don't have
> a ALSA equivalent for my old hardware. There're several
> sound cards with both ALSA and OSS drivers where ALSA works
> much better 99% of the time. Those could be safely removed
> (even in the 2.6 timeframe, I'd argue) but I'd like to keep the ones
> without an alsa equivalent for my old hardware (specially now that we
> have a -tiny tree ;) however I can understand that if they don't
> have a maintainer they'll get removed...

The real issue with removing OSS from a stable kernel is that a kernel 
update should not break existing system software (at least compliant 
software). As of early 2.6 it seemed that you had to update to the ALSA 
mixer and {something I don't remember} if you used the OSS emulation. I 
just used OSS and it worked. Based on only two systems, so it may not apply.

Stable and install new sound software don't seem to mix well. I suggest 
that the current course is a good one, keep both systems in the stable 
kernel.


-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

       reply	other threads:[~2004-03-23 17:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
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

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=406070F9.2070900@tmr.com \
    --to=davidsen@tmr.com \
    --cc=diegocg@teleline.es \
    --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