Alsa initialization change

Jeremy White jwhite at codeweavers.com
Mon Jun 13 22:49:21 CDT 2005


What happens if you change the snd_pcm_open
line to tweak the 3rd parameter from 0 to
SND_PCM_NONBLOCK?

Cheers,

Jer

Kevin Koltzau wrote:
> On Monday 13 June 2005 10:01 am, Jeremy White wrote:
> 
>>Attached is a fairly sizable patch that revamps the
>>way Alsa initialization is done.
> 
> 
> In ALSA_TestDeviceForWine, the call to snd_pcm_open blocks if I have
> any applications currently using my sound card, and does not complete
> until all other apps accessing alsa close, effectively freezing wine
> mixing is not supported on my card, so only one application
> can open hw at a time, all others will block on snd_pcm_open
> it does, however, work with
> [ALSA]
> "AutoScanCards"="n"
> "DeviceCount"="1"
> "DevicePCM1"="default"
> "DeviceCTL1"="default"
> 
> Sound card is standard AC'97 that comes with nForce4
> # lspci -v -s 00:04.0
> 0000:00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2)
>         Subsystem: ASUSTeK Computer Inc.: Unknown device 812a
>         Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 22
>         I/O ports at dc00
>         I/O ports at e000 [size=256]
>         Memory at d2003000 (32-bit, non-prefetchable) [size=4K]
>         Capabilities: [44] Power Management version 2
> 
> 




More information about the wine-devel mailing list