Messages in this thread Patch in this message | | | Date | Sat, 11 Feb 2006 15:50:50 +0100 | From | Adrian Bunk <> | Subject | [2.6 patch] update OBSOLETE_OSS_DRIVER schedule and dependencies |
| |
This patch updates the schedule for the removal of drivers depending on OBSOLETE_OSS_DRIVER as follows: - adjust OBSOLETE_OSS_DRIVER dependencie - 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
Additionally, it corrects some OBSOLETE_OSS_DRIVER dependencies. A rationale of the changes is in http://lkml.org/lkml/2006/1/28/135
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
Documentation/feature-removal-schedule.txt | 2 +- sound/oss/Kconfig | 16 ++++++++-------- 2 files changed, 9 insertions(+), 9 deletions(-)
--- linux-2.6.16-rc2-mm1-full/Documentation/feature-removal-schedule.txt.old 2006-02-11 15:25:07.000000000 +0100 +++ linux-2.6.16-rc2-mm1-full/Documentation/feature-removal-schedule.txt 2006-02-11 15:26:04.000000000 +0100 @@ -26,7 +26,7 @@ --------------------------- What: drivers depending on OBSOLETE_OSS_DRIVER -When: January 2006 +When: before 2.6.18 Why: OSS drivers with ALSA replacements Who: Adrian Bunk <bunk@stusta.de> --- linux-2.6.16-rc2-mm1-full/sound/oss/Kconfig.old 2006-02-11 15:20:12.000000000 +0100 +++ linux-2.6.16-rc2-mm1-full/sound/oss/Kconfig 2006-02-11 15:24:06.000000000 +0100 @@ -21,7 +21,7 @@ config SOUND_BT878 tristate "BT878 audio dma" - depends on SOUND_PRIME && PCI && OBSOLETE_OSS_DRIVER + depends on SOUND_PRIME && PCI ---help--- Audio DMA support for bt878 based grabber boards. As you might have already noticed, bt878 is listed with two functions in /proc/pci. @@ -76,7 +76,7 @@ config SOUND_EMU10K1 tristate "Creative SBLive! (EMU10K1)" - depends on SOUND_PRIME && PCI && OBSOLETE_OSS_DRIVER + depends on SOUND_PRIME && PCI ---help--- Say Y or M if you have a PCI sound card using the EMU10K1 chipset, such as the Creative SBLive!, SB PCI512 or Emu-APS. @@ -102,7 +102,7 @@ config SOUND_FUSION tristate "Crystal SoundFusion (CS4280/461x)" - depends on SOUND_PRIME && PCI + depends on SOUND_PRIME && PCI && OBSOLETE_OSS_DRIVER help This module drives the Crystal SoundFusion devices (CS4280/46xx series) when wired as native sound drivers with AC97 codecs. If @@ -140,7 +140,7 @@ config SOUND_ES1371 tristate "Creative Ensoniq AudioPCI 97 (ES1371)" - depends on SOUND_PRIME && PCI && OBSOLETE_OSS_DRIVER + depends on SOUND_PRIME && PCI help Say Y or M if you have a PCI sound card utilizing the Ensoniq ES1371 chipset, such as Ensoniq's AudioPCI97. To find out if @@ -571,7 +571,7 @@ config SOUND_AD1889 tristate "AD1889 based cards (AD1819 codec) (EXPERIMENTAL)" - depends on EXPERIMENTAL && SOUND_OSS && PCI + depends on EXPERIMENTAL && SOUND_OSS && PCI && OBSOLETE_OSS_DRIVER help Say M here if you have a sound card based on the Analog Devices AD1889 chip. @@ -742,7 +742,7 @@ config SOUND_NM256 tristate "NM256AV/NM256ZX audio support" - depends on SOUND_OSS && OBSOLETE_OSS_DRIVER + depends on SOUND_OSS help Say M here to include audio support for the NeoMagic 256AV/256ZX chipsets. These are the audio chipsets found in the Sony @@ -919,7 +919,7 @@ config SOUND_YM3812 tristate "Yamaha FM synthesizer (YM3812/OPL-3) support" - depends on SOUND_OSS && OBSOLETE_OSS_DRIVER + depends on SOUND_OSS ---help--- Answer Y if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4). Answering Y is usually a safe and recommended choice, however some @@ -947,7 +947,7 @@ config SOUND_OPL3SA2 tristate "Yamaha OPL3-SA2 and SA3 based PnP cards" - depends on SOUND_OSS + depends on SOUND_OSS && OBSOLETE_OSS_DRIVER help Say Y or M if you have a card based on one of these Yamaha sound chipsets or the "SAx", which is actually a SA3. Read - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |