[alsa-devel] Backported sbxfi driver (UNTESTED!)
The Source
thesourcehim at gmail.com
Thu Oct 16 20:18:07 CEST 2008
Takashi Iwai пишет:
> At Thu, 16 Oct 2008 19:06:58 +0400,
> The Source wrote:
>
>> Takashi Iwai пишет:
>>
>>> At Thu, 16 Oct 2008 19:00:16 +0400,
>>> The Source wrote:
>>>
>>>
>>>> Takashi Iwai пишет:
>>>>
>>>>
>>>>> At Thu, 16 Oct 2008 18:41:08 +0400,
>>>>> The Source wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Takashi Iwai пишет:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> At Thu, 16 Oct 2008 18:15:45 +0400,
>>>>>>> The Source wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Takashi Iwai пишет:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> At Thu, 16 Oct 2008 17:36:04 +0400,
>>>>>>>>> The Source wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>> And, which X-Fi model do you have?
>>>>>>>>>>>> Please show the lspci -nv output, too.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> I've got the X-Fi Elite Pro.
>>>>>>>>>>> That's The one with the external In/Out box.
>>>>>>>>>>>
>>>>>>>>>>> Speaking of which, the headphone jack on it does not output a signal
>>>>>>>>>>> yet, the signal only goes to line out.
>>>>>>>>>>>
>>>>>>>>>>> There's some relais on the card that seem to switch these, they click
>>>>>>>>>>> multiple times with the windows driver and not all all with yours, I
>>>>>>>>>>> think that's the reason :)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> Original OSS driver doesn't output to external block also, so it
>>>>>>>>>> wouldn't be easy to make this support I think.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> The values for port->conv[0] and [1] values in sbxfi_playback_open()
>>>>>>>>> might play some role. It's I2SA_L and I2SA_R, alias DAI_CH_I2SAL
>>>>>>>>> and DAI_CH_I2SAR, as default. You can try other values, such as,
>>>>>>>>> DAI_CH_I2SBL, DAI_CH_I2SA1L, and so on.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Takashi
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> Latest snapshot has a bug:
>>>>>>>> make[3]: *** No rule to make target
>>>>>>>> `/mnt/e/temp/alsa-driver-unstable/acore/jack.o', needed by
>>>>>>>> `/mnt/e/temp/alsa-driver-unstable/acore/snd.o'. Stop.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> Already fixed.
>>>>>>>
>>>>>>>
>>>>>>> Takashi
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> In file included from /mnt/e/temp/alsa-driver-unstable/acore/jack.c:3:
>>>>>> /mnt/e/temp/alsa-driver-unstable/acore/../alsa-kernel/core/jack.c: In
>>>>>> function ‘snd_jack_new’:
>>>>>> /mnt/e/temp/alsa-driver-unstable/acore/../alsa-kernel/core/jack.c:107:
>>>>>> error: ‘SW_MICROPHONE_INSERT’ undeclared (first use in this function)
>>>>>> /mnt/e/temp/alsa-driver-unstable/acore/../alsa-kernel/core/jack.c:107:
>>>>>> error: (Each undeclared identifier is reported only once
>>>>>> /mnt/e/temp/alsa-driver-unstable/acore/../alsa-kernel/core/jack.c:107:
>>>>>> error: for each function it appears in.)
>>>>>> /mnt/e/temp/alsa-driver-unstable/acore/../alsa-kernel/core/jack.c: In
>>>>>> function ‘snd_jack_report’:
>>>>>> /mnt/e/temp/alsa-driver-unstable/acore/../alsa-kernel/core/jack.c:157:
>>>>>> error: ‘SW_MICROPHONE_INSERT’ undeclared (first use in this function)
>>>>>>
>>>>>>
>>>>>>
>>>>> Hmm, it seems broken for older kernels right now.
>>>>> The easy workaround is to pass --with-cards=sbxfi to configure.
>>>>>
>>>>> Anyway, I'll fix it now.
>>>>>
>>>>> thanks,
>>>>>
>>>>> Takashi
>>>>>
>>>>>
>>>>>
>>>>>
>>>> --Hey, man, this is cool! Plays just fine (volume ok, speed ok, no
>>>> --glitches) with 96000, 48000, 44100, 22050, 16/24 bit, Stereo and --Mono!!
>>>> --I didn't change anything in the source code, so I don't use system
>>>> --timer. Yes!!
>>>>
>>>> However oss (alsa-emulated) is unstable. I'll test more.
>>>>
>>>>
>>> Could be due to 96kHz base-rate? Try base_rate=48000.
>>> If you get still problems, please show the kernel logs with debug=2.
>>>
>>> BTW, the jack.c compile error should have been fixed now (hopefully).
>>> Let me know if you still have the build errors.
>>>
>>>
>>> thanks,
>>>
>>> Takashi
>>>
>>>
>>>
>> Ok. OpenAL with alsa also seem to cause problems.
>>
>
> In both cases, check the period_size and buffer_size values (shown in
> the kernel message, or /proc/asound/card0/pcm0p/sub0/hw_params).
> And, try to aplay with these parameters, whether you get the similar
> problem.
>
> % aplay -v --period-size=xxx --buffer-size=yyy foo.wav
>
>
> Takashi
>
>
I'm sorry, but any attemp to play file with ossplay results in complete
system hang with error:
unable to handle NULL ponter dereference at address
0000000000000008.....(hang, no more output).
I tried many wav formats. So I can't get error log or period and buffer
sizes, sorry.
More information about the Alsa-devel
mailing list