JohnSwenson wrote: > I got Squeezelite to run (armv6 version) everything works fine except > there are some clicks every so often, particularly if I have "top" > running I get a click every time it updates. I tried various -p options > and it makes no difference, I also tried various -b options and again no > difference. > > BTW what is the arm "hf" version? > > I checked with ps and didn't see any FIFO threads. > > In general this looks good, USB Async works, up to 192 works, UAC1 > doesn't need a hub. This is indicating to me that the processor itself > is probably quite good enough for our needs. There may need to be some > thread tweaking etc to get rid of the clicks. > > I looked at /sys and it does look like it has the alsa driver that talks > to the I2S,S/PDIF outputs. I have not found out how to configure and > turn these on. I probably have to look at the source code to figure that > one out. I'll spend some more time on that today. > > So from my point of view staying with this class of processor seems good > to me. I'm going to continue with the hardware design with the Ti > processor. I'm probably going to go for the AM3874 rather than the > AM3359 that is in the BeagleBone. The 3874 seems to have similar > subsystems, so there is a pretty good chance it will work as well. > > John S.
HF versions is hardfloat and is used if the distribution is using hardfloat calling conventions. This is used by Pi and other more modern linux distros as its faster to pass floating point parameters using this convention where the floating point registers are used. The soft float eabi (which is the default) passes float point parameters via the integer registers to remain compatible with cpus without floating point units. This used to be the default for all linux arm systems and is slower. Hence the migration to hardfloat as most machines now have floating point units. Did you run squeezelite as root. The output thread is automatically created as sched_fifo if the user has permission to do this (which root has and you otherwise need to add the relavent permissions). Should see one thread as FIFO when you do this. Start with -d output=debug to see a log message indicating whether it was able to set fifo. ------------------------------------------------------------------------ Triode's Profile: http://forums.slimdevices.com/member.php?userid=17 View this thread: http://forums.slimdevices.com/showthread.php?t=97881 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/discuss
