JackOfAll wrote: 
> Don't ask me why, cause I can't give you a scientific explanation, but
> 384k isn't a problem. You can throw pretty much any params at that and
> it doesn't matter. It's 352k8 that is tricky for me. My take is that if
> what I have configured works at 352k8, it works just fine at 384k.
> Assuming max rate out (hardware) is going to be 192k, what works fine
> for 176k4 will work just fine for 192k. 
> 
> Benefit.... There isn't any. Other than in my calculations, x bytes are
> going to be transferred in one interrupt, and how many interrupts a
> second will be needed to support 2822400 bytes/sec data transfer for the
> 352k8 rate. I just wanted to be able to set the values directly.

How about keeping the same syntax, but if the "buffer" value is less
than 500 then it is a time in ms, otherwise a size, if "period" is < 50
it is a count else a size?


------------------------------------------------------------------------
Triode's Profile: http://forums.slimdevices.com/member.php?userid=17
View this thread: http://forums.slimdevices.com/showthread.php?t=98544

_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix

Reply via email to