OSS driver removal, 3nd round
Now that the second round of removing options for OSS drivers where ALSA drivers without regressions exist for the same hardware got included in Linus' tree, it's time for a third round amongst the remaining drivers.
Removing OSS drivers where ALSA drivers for the same hardware exists has 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
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
The proposed timeline is:
- 2.6.20: let the drivers under 1. in the list below depend on OSS_OBSOLETE
- 2.6.22: remove the options depending on OSS_OBSOLETE
- 2.6.24: remove the code for the drivers that were depending on OSS_OBSOLETE from the kernel tree
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 listed under 1. below, send me an email with a bug number in the ALSA bug tracking system now.
A small FAQ:
Q: But OSS is kewl and ALSA sucks!
A: The decision for the OSS->ALSA move was four years ago.
If ALSA sucks, please help to improve ALSA.
Q: What about the OSS emulation in ALSA?
A: The OSS emulation in ALSA is not affected by my patches
(and it's not in any way scheduled for removal).
Please review the following list:
1. ALSA drivers for the same hardware
DMASOUND_PMACSOUND_ES1371
2. ALSA drivers for the same hardware with known problems
SOUND_CS4232
- ALSA #1520 (Soundchip was not detected on HP Omnibook 5700 CTX)
SOUND_ICH
- Alan Cox:
ALSA driver lacks "support for AC97 wired touchscreens and the like"
SOUND_SSCAPE
- ALSA #2234 (driver does not find Soundscape Elite)
SOUND_TRIDENT
- maintainer of the OSS driver wants his driver to stay
SOUND_VIA82CXXX
- ALSA #1906 (1-second overruns reported by arecord, complete system hang with jackd -d alsa)
3. no ALSA drivers for the same hardware
DMASOUND_ATARIDMASOUND_PAULADMASOUND_Q40SOUND_AEDSP16SOUND_AU1550_AC97SOUND_BCM_CS4297ASOUND_HAL2SOUND_KAHLUASOUND_MSNDCLASSOUND_MSNDPINSOUND_MSS (also due to SOUND_PSS, SOUND_TRIX and perhaps SOUND_AEDSP16) SOUND_PASSOUND_PSSSOUND_SB (also due to SOUND_KAHLUA, SOUND_PAS and perhaps SOUND_AEDSP16) SOUND_SH_DAC_AUDIOSOUND_TRIXSOUND_VIDCSOUND_VRC5477SOUND_VWSNDSOUND_WAVEARTIST
Thomas Sailer
Acked-byQuoted 3 lines · Adrian Bunk
1. ALSA drivers for the same hardware
SOUND_ES1371
Kyle Moffett
Acked-byQuoted 3 lines · Adrian Bunk
1. ALSA drivers for the same hardware
DMASOUND_PMAC
I don't think I've ever used this sound driver on any of my PowerMacs, ranging back to my aged 400MHz box, which is (I believe) the only piece of hardware I own which it supports, and the ALSA driver plays sound on that system perfectly. Admittedly the ALSA driver's a bit more flaky on my newer G5 and powerbook but I don't think the DMASOUND_PMAC driver _ever_ supported those (and I doubt it ever will).
Cheers,
Kyle Moffett
Kyle Moffett
Acked-byQuoted 3 lines · Adrian Bunk
1. ALSA drivers for the same hardware
DMASOUND_PMAC
I don't think I've ever used this sound driver on any of my PowerMacs, ranging back to my aged 400MHz box, which is (I believe) the only piece of hardware I own which it supports, and the ALSA driver plays sound on that system perfectly. Admittedly the ALSA driver's a bit more flaky on my newer G5 and powerbook but I don't think the DMASOUND_PMAC driver _ever_ supported those (and I doubt it ever will).
Cheers,
Kyle Moffett
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV