Re: came makes bus angry
Brought to you by:
aeb,
bencollins
From: Clemens L. <cl...@la...> - 2011-07-29 08:00:25
|
Carl Karsten wrote: > ASUS motherboard, one on board firewire, one pci card. PCI or PCI Express? > plug camera into card, all works fine. plug into on board and things fail Which points to a hardware error. > (veyepar)juser@cnt2:~$ lspci |grep 13 > 04:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series Firewire Controller (rev 01) > 08:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 46) The VT6315 is a rather new PCIe chip; the VT6308 is a rather old PCI chip that is known to have problems. In theory, both should work with a camera like yours, but it's possible that your VT6308 has smaller tolerances, that the signal is degraded because of long lines on the motherboard, or that it's just plain broken. Does it work when you connect the VT6315 directly to the VT6308 (i.e., do you get four devices fw0..fw3)? > (veyepar)juser@cnt2:~$ dvgrab > Error: no camera exists > > ... > [ 1572.087990] firewire_ohci: isochronous cycle inconsistent > [ 1572.798527] firewire_core: created device fw2: GUID 008045821097902b, S100 Here, after many bus resets, a device from Matsushita is found. > [ 1572.798534] firewire_core: phy config: card 1, new root=ffc1, gap_count=5 > [ 1572.799208] firewire_core: IRM is not 1394a compliant, making local node (ffc0) root. But it complies only with the oldest 1394 standard, so it is not allowed to be root (the root node does some bus management functions; if an old node is root, some new 1394a features would not be available). Switching the root node should, in theory, not be a problem, however ... > [ 1572.799211] firewire_core: phy config: card 1, new root=ffc0, gap_count=5 ... after the bus reset that made the switch, the camera has vanished again. This looks very much like this bug <https://bugzilla.redhat.com/show_bug.cgi?id=633260> that was worked around with commit 6044565af458 (fix unstable I/O with Canon camcorder). It's possible that these Canon and Matsushita cameras use the same PHY chip, or the same FireWire interface firmware. Carl, to find out which PHY chip the camera uses, please try to run the lsfirewirephy tool from the jujuutils package (<http://code.google.com/p/jujuutils/>) with the camera connected to the working controller. To check if the Canon workaround works with your camera, recompile firewire-core after changing the value of CANON_OUI in drivers/firewire/core-card.c from 0x000085 to 0x008045. Stefan, might it be a good idea to allow all old IRMs that look like such a camera, i.e., if they are a S100 device? Regards, Clemens |