My bad for not reading the subject line more closely.
>
> For 2.5, the thing is i remember being able to successfully use my DV Camcorder
> Canon Optura 200MC ( MVX2i in Europe) with IEEE1394 , around 2.5.59 IIRC.
>
> Since then, i only got these "reset storms" versions over versions. Not that i complain about
> but it's just that i hope that reporting bugs will be helpful to IEEE1394 developers, because
> if it worked once, then i don't see why i wouldn't work either with newer versions 8)
The code that prints "ieee1394: Remote root is not IRM capable,
resetting..." was added almost 2 months ago to the 1394 SVN trunk, so
its still fairly recent and probably after 2.5.59. If this message
repeats rapidly under recent 2.5.*, then there is a problem with
initiating a bus reset and forcing the local node to be root. My
recollection of the 1394 spec is that PHY packet needs to be sent out to
all nodes to clear the their root hold-off bit and the local node sets
its own root hold-off bit. The OHCI 1394 code doesn't appear to do
anything special to send a PHY packet (it does set the root hold-off bit
in the local PHY chip) and I wonder if that might not be the source of
this problem. Does anyone, who understands the PHY chip, know if it
automatically sends the appropriate PHY packet when this bit is set? If
not, we may need to add code to send it.
If anyone can answer the one question I posed above, I'd greatly
appreciate it.
Thanks,
-- Steve Kinneberg ACM Systems 3034 Gold Canal Drive Rancho Cordova, CA 95670 Phone: (916) 463-7987 Email: kinnebergsteve@acmsystems.com- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/