Any thoughts?
#
# Sound
#
CONFIG_SOUND=y
# CONFIG_SOUND_ES1370 is not set
# CONFIG_SOUND_ES1371 is not set
# CONFIG_SOUND_SONICVIBES is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
CONFIG_SOUND_OSS=y
# CONFIG_SOUND_PAS is not set
CONFIG_SOUND_SB=y
CONFIG_SB_BASE=220
CONFIG_SB_IRQ=7
CONFIG_SB_DMA=1
CONFIG_SB_DMA2=5
CONFIG_SB_MPU_BASE=330
#
# MPU401 IRQ is only required with Jazz16, SM Wave and ESS1688.
#
#
# Enter -1 to the following question if you have something else such
#as SB16/32.
#
CONFIG_SB_MPU_IRQ=-1
CONFIG_SOUND_ADLIB=y
# CONFIG_SOUND_GUS is not set
# CONFIG_SOUND_MPU401 is not set
# CONFIG_SOUND_PSS is not set
# CONFIG_SOUND_MSS is not set
# CONFIG_SOUND_SSCAPE is not set
# CONFIG_SOUND_TRIX is not set
# CONFIG_SOUND_MAD16 is not set
# CONFIG_SOUND_WAVEFRONT is not set
# CONFIG_SOUND_CS4232 is not set
# CONFIG_SOUND_OPL3SA2 is not set
# CONFIG_SOUND_MAUI is not set
# CONFIG_SOUND_SGALAXY is not set
# CONFIG_SOUND_OPL3SA1 is not set
# CONFIG_SOUND_SOFTOSS is not set
CONFIG_SOUND_YM3812=y
# CONFIG_SOUND_VMIDI is not set
# CONFIG_SOUND_UART6850 is not set
#
# Additional low level sound drivers
#
# CONFIG_LOWLEVEL_SOUND is not set
On Wed, Oct 28, 1998 at 01:44:37PM +0100, Daniel J. Rodriksson wrote:
> Craig Condit wrote:
> >
> > The sound code is broken in 2.1.126 and 2.1.127pre2 for other programs
> > besides quake. Direct output to /dev/dsp works fine, as does x11amp.
> > However, xgal also has problems - it outputs no sound whatsoever.
> >
> > My theory is that xgal is opening /dev/dsp read-write as quake is, and
> > therefore is getting a full duplex connection, causing it to fail on
> > 16-bit sound output. Any ideas here? Is this a kernel problem or a
> > problem with xgal? I suspect the kernel, as it worked flawlessly in
> > kernel <= 2.1.125.
>
> Let's try to make it clear:
> 2.1.126 ( deriving from 2.1.125-ac3 ) includes the sb16 full duplex
> support but removes the possibility to have a full duplex program
> use mmap ( 8-16 and 16-8 format conversion happen when you use
> read and write ).
>
> I'm working in having quake and others that open the device readwrite
> but only use playback work.
>
> But, I would say that these programs can be considered buggy, since
> they do something they are not suppossed to do ( open in readwrite
> when writeonly should suffice ).
>
> I love quake too, so I'll make it work. Other choices would be
> removing the full duplex support from the sb16 driver or getting
> to technical docs, describing how to have true 16 bit duplex
> support using sb16 ( I don't really know whether this can
> be done :) )
>
> Cheers
>
>
> --
> -------------------------------------------------------------|
> | Remember Scotch: 'THERE CAN BE ONLY ONE' |
> -------------------------------------------------------------|
> | Daniel J. Rodriksson | C-220,ETSI Telecomunicaciones |
> | djr@dit.upm.es | Avda Paraninfo S/N |
> | http://www.dit.upm.es/~djr | 28040 Madrid |
> | +34-1-3367366 + ext 469 | SPAIN |
> |------------------------------------------------------------|
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
-- Eric Brunson * _ o * Faster and faster, brunson@brunson.com * / //\ until the thrill of speed brunson@l3.net \>>| * overcomes the fear of death page-eric@l3.net \\,- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/