Re: "aborting sbp2 command" expected in kernel.org FireWire maybe

Pat LaVarre wrote:
> Copies fail after 2.4 modprobe sbp2 sbp2_serialize_io=0, same as after 2.6
> modprobe serialize_io=0,
...
> Are we therefore concluding I should claim the device has a bug?
>
> I should now go borrow a bus analyser and collect a 1394 bus trace, because

If you are only interested in the traffic from and to the Linux host,
than you only need to enable "excessive debug logging" for the 1394
drivers. (If you want to analyze what other host OSs do, you need of
course a bus analyzer.)

> that (sbp2_)?serialize_io=0 trace will show a compliant host provoking a
> device to fail to comply in some way that doesn't bother Mac/ Windows?

Personally, I am not yet familiar enough with the SBP-2 spec to draw
any conclusions WRT compliance of either one.

-- 
Stefan Richter
-=====-=-=-- =--= =--=-
http://arcgraph.de/sr/
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
mailing list Linux1394-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-user