From: Stefan R. <st...@s5...> - 2010-07-24 15:42:08
|
Hi, as Arnold told me on IRC, Focusrite Saffire Pro24 does not work correctly yet on the newer kernel stack. Arnold saw this with different controllers. I did a few quick tests myself now, so far on a VT6306. Jackd seems to start up and keep running fine but I don't get any sounds on the outputs when I have a jack client playing. I can stop jackd, unload the drivers, load the other drivers, and start jackd again, and thus confirm that the "mute" issue only exists with the new drivers underneath while playback works fine with the old drivers. Of course I am running latest svn of ffado + latest kernel.org git of libraw1394 (with the ARM/FCP source node ID fix) + latest firewire drivers (with the ARM/FCP source node ID fix and with Clemens' Split_Timeout implementation; i.e. drivers like they will very likely be released in kernel 2.6.36-rc1). Attached are -v3 logs from the old and the new drivers. There are three differences, all of them look irrelevant: 1.) -dhw:4 vs. -dhw:0. This is jaut because enumeration of the buses is different in the libraw1394 kernel backends. The device was actually connected to the same controller all the time. 2.) The old Could not set SPLIT_TIMEOUT... message. This doesn't actually matter. The reason for it is that usually device file permission disallow access to /dev/fw* of local nodes. If I allow rw access to these files, these messages go away because ffado can increase Split_Timeout now. 3.) Three lines at the end of the new-stack log: got write request, offset=0xffffe0000000, length=4 got write request, offset=0xffffe0000000, length=4 got write request, offset=0xffffe0000000, length=4 These lines come from libraw1394, src/fw.c::handle_arm_request(). Apparently debug messages that somebody forgot to remove. "nosy-dump --view=stats" shows that there is plenty of isochronous traffic on the bus. (Well, I also could have triggered firewire-ohci's IRQ debug logging to confirm that.) I had a quick look at nosy-dump's packet logging during jackd's startup but saw nothing suspicious, just a bunch of read and write transactions that completed all fine. Maybe I should compare packet dumps from nosy on top of the old and the new drivers side by side next... -- Stefan Richter -=====-==-=- -=== ==--- http://arcgraph.de/sr/ |