Hi Bernard, thanks for your reply.
At 27 Dec 2002 10:19:10 +0100, Bernard Urban wrote: > > Takashi Iwai <[EMAIL PROTECTED]> writes: > > > Hi, > > > > can anyone who owns the CMI8330 ISA test the attached patch? > > I am your man !!! Happy to see that this card is no longer forgotten. > 1 month ago, I have written the following to > [EMAIL PROTECTED], but it never got there (I was not a > subscriber at this time). > > ****************************************** > > Short story: (and main problem) > ========= > I have tried to hack the cmi8330 driver version 0.9.0beta10, which > does not work, by relying on the (semi) functional last 0.5 driver. It > is difficult to appreciate the changes done between 0.5 and 0.9, > as the CVS Changelog misses the 0.5 era. > Any hint to fill this hole would be appreciated. > > More generally, I am wondering if ALSA is still considering > maintenance on old sound chips drivers? we can maintain the code but none of us have these hardwares for test... > As an alsa-1.0 release is near, this topic seems important to the > credibility of the project. > > Long story: (plus a lot of other minor problems) > ========= > I have access to 4 different Linux machines, with different sound > cards. All the machine run Debian Woody, kernel 2.4.18, > same config for 4 machines, as far as hardware permits: > AMD K6-II with a SB Vibra 16x PnP > AMD K6-II with a CMI8330 > PIII with a intel 810 > Athlon with a VIA8233 > > First, the two K6-II machines run fine the OSS sb driver. > When I got the Athlon machines, as via8233 is not supported by OSS > drivers, I decided to switch to ALSA 0.9 (woody packages 0.9.0beta12). > > The Athlon with snd-via8233 runs fine, no problems with using the OSS > compatibility level. > The PIII with snd-intel8x0 runs well, except that xquake (original bin > from Id) runs without producing any sound. Moot point, because > quakeforge version works well (alsa plugin). > > So the problem here seems to be in the oss compatibility level ? most likely the problem is due to mmap on OSS emulation. the OSS emulation should be "direct" mode in some cases. you can change the behavior via writing to oss proc file like echo "xquake 0 0 direct" > /proc/asound/card0/pcm0p/oss please check alsa-kernel/Documentation/ALSA-Configuration.txt for details. > Now the AMD K6-II with a SB Vibra 16X PnP: runs with snd-sb16. In the > mixer I must force the 16 bit DMA to be allocated to Capture > to have PCM sound for all kind of audio formats. If set to Auto, for instance > .au format is not recognized. Also, xquake runs and produces sound only with > option 8bits sound. perhaps this is also related with the above. > quakeforge works well, but there is a time lag in > producing sound, which does not exist with the OSS driver. > Tuning snd-mixahead does not help. this is not sure. does the delay happen only on quake or do you mean it generally? if it's general behavior, then it's easier to debug. anyway we need to trace at which point the delay occurs. > Finally the AMD K6-II with the CMI8330 and the snd-cmi8330 driver. > Version 0.9 does not produce sound at all. But going back to alsa 0.5, > I was able to produce PCM sound and play CDs. The mixer tuning is very > buggy (this was documented in the alsa-user mail list 2 years ago!), > but you can have it working. xquake does not produce sound though. > quakeforge cannot be run (they use the 0.9 alsa API). > > Another real pain with this driver is the use of > two devices (pcmC0D1p and pcmC0d0c) on the same card. This requires > editing several configuration files to have OSS applications work. > For instance, I must switch /dev/dsp with /dev/adsp and change in > alsa.conf to the following line: > defaults.pcm.device 1 > > This was corrected in the 0.9 snd-cmi8330 driver, but as it now does not > produce sound... I have analyzed the driver code differences between > 0.5 and 0.9. The main difference in handling the hardware seems to be that > in the 0.5 version, the SB mixer part is initialized, not in the 0.9 > one. So I added such an initialization step. I added also the SB mixer > controls to the cmi8330 ones, as it is no more possible to add a second > mixer device in the 0.9 API, at least I do not see how. > (This addition is not understood > by alsamixer, but amixer with the complex controls works, with the > same kind of curious behaviour as amixer-0.5) well, the mixers are all mixed up on alsa 0.9. it's possible to assign the ad1848 mixer elements with the index 1, though. > And guess what, bingo, I got PCM sound ! But an horrible sound, very > distorted, so something is still working badly. This > was just after removing the 0.5 driver and installing the modified 0.9 one. > After rebooting the machine with the 0.9 running, no more sound! ok, it explains the hardware init problem. i'll check the difference between 0.5 and 0.9. btw, my last patch was already committed to cvs. ciao, Takashi ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
