Dev Mazumdar wrote: > Yes, this is a known problem You should look at the OSS driver for the > fix. > > http://mercurial.opensound.com/?file/0bd0ed4d102c/kernel/drv/oss_solo/oss_solo.c > > > > look at the trigger routine: > > 700 { > 701 solo_setmixer (devc, 0x78, 0x92); /* stablilze fifos */ > 702 oss_udelay(100); > 703 solo_setmixer (devc, 0x78, 0x93); /* Go */ > 704 OUTB (devc->osdev, 0x0A, devc->base + 6); /*unmask dac2 intr */
I actually figured it out last night... turns that the order of umasking the DAC2 was the root cause. I've got it working now. If anyone wants a binary, let me know. http://gdamore.blogspot.com/2009/09/crazy-sunday-ess-solo-1.html - Garrett > > > --------------------------- > 4Front Technologies > > 9826 Beverlywood Street > Los Angeles, CA 90064, USA > Tel: (310) 202 8530 > Fax: (310) 202 0496 > > Garrett D'Amore wrote: >> I have a driver that I ported from FreeBSD yesterday (Sunday). It >> *mostly* works. >> >> However, I seem to have troubles where the channel offset is often >> mis-set. That is to say, it sounds at times like the channels are >> swapped. Whether they are swapped or not appears to be random, no >> matter whether I restart the device from get go (including modunload >> and reload, so a full device reset) or not. >> >> Occasionally it will even sound like the audio data is badly >> corrupted. But only infrequently. >> >> Does anyone around here know of any special tricks with the Solo-1 >> that I might be missing? After looking at various other sources, I >> can't seem to find the source of the problem.... >> >> - Garrett >> >>
