Clemens Ladisch wrote:
Harry van Haaren wrote:
[ 190.433203] snd-fireworks fw1.0: Detect discontinuity of CIP: 00 0A [ 190.591959] snd-fireworks fw1.0: Detect discontinuity of CIP: 00 02 [ 190.749202] snd-fireworks fw1.0: Detect discontinuity of CIP: 00 12 [ 190.908270] snd-fireworks fw1.0: Detect discontinuity of CIP: 00 12 [ 191.066267] snd-fireworks fw1.0: Detect discontinuity of CIP: 00 0A [ 191.225139] snd-fireworks fw1.0: Detect discontinuity of CIP: 00 02 [ 191.383942] snd-fireworks fw1.0: Detect discontinuity of CIP: 00 02
JACK also reports xruns, same as before: flashing the firmware to the latest doesn't seem to have changed anything. The firmware of this device was at 5.7 before the flash, perhaps its "too new" for snd-fireworks in its current state?
I suspect these counter values are generated by the hardware; I don't think that the firmware can do anything to affect this.
I do not get any discontinuities with ARM firmware 3.0.2. So much for that theory.
Anyway, if you're up to experimentation, try removing the entire "if (lost)" block from sound/firewire/amdtp.c, and recompiling the drivers. (This will make the driver accept all packets, without fixing the wrong order.)
Regards, Clemens