From: Stefan R. <st...@s5...> - 2010-08-27 11:00:58
|
Luis Pablo Gasparotto wrote: [...] > [luispa@LPGDELL ~]$ sudo rmmod ohci1394 > [luispa@LPGDELL ~]$ sudo rmmod raw1394 > [luispa@LPGDELL ~]$ sudo modprobe raw1394 > [luispa@LPGDELL ~]$ sudo modprobe ohci1394 > [luispa@LPGDELL ~]$ ffado-test ListDevices > ----------------------------------------------- > FFADO test and diagnostic utility > Part of the FFADO project -- www.ffado.org > Version: 2.999.0-1881 > (C) 2008, Daniel Wagner, Pieter Palmers > This program comes with ABSOLUTELY NO WARRANTY. > ----------------------------------------------- > > === 1394 PORT 0 === > Node id GUID VendorId ModelId Vendor - Model > 0 0x000595040040045a 0x00000595 0x00000001 Alesis - > 1 0x394fc00030c15e01 0x00394FC0 0x00000000 Linux - ohci1394 - > no message buffer overruns > [luispa@LPGDELL ~]$ ffado-test ListDevices > ----------------------------------------------- > FFADO test and diagnostic utility > Part of the FFADO project -- www.ffado.org > Version: 2.999.0-1881 > (C) 2008, Daniel Wagner, Pieter Palmers > This program comes with ABSOLUTELY NO WARRANTY. > ----------------------------------------------- > > === 1394 PORT 0 === > Node id GUID VendorId ModelId Vendor - Model > 02345351508: Error (configrom.cpp)[ 150] initialize: Could not parse config rom > of node 0 on port 0 > no message buffer overruns Oh, this answers my question from the other post whether "ffado-test ListDevices" succeeds when repeated. Since this fails without any isochronous I/O setup in the picture, it means that this is not an issue with potential iso DMA uni bugs in the Ricoh controller. Maybe the csr->max_rom = 4; modification that I suggested in the other post brings us somewhere. Before your very first and successful run of "ffado-test ListDevices", the ieee1394 driver already read the Config ROM but only with quadlet reads. Then there is the successful ffado-test run that involved quadlet reads and 64 bytes sized reads. And then any repetition of that obviously fails... But as I said, there are other FFADO users with Alesis iO|14 without this problem. Hence a bad interaction with the Ricoh controller is not entirely ruled out as the error source yet --- if it does not turn out to be just a flaw with your particular version of the iO|14 firmware. -- Stefan Richter -=====-==-=- =--- ==-== http://arcgraph.de/sr/ |