From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: [PATCH] firewire: core: check for 1394a compliant IRM, fix inaccessibility of Sony camcorder
Date: Sun, 30 May 2010 19:56:55 +0200 (CEST) [thread overview]
Message-ID: <tkrat.e4ca403b4d64cca4@s5r6.in-berlin.de> (raw)
In-Reply-To: <tkrat.740b506673ccbf6d@s5r6.in-berlin.de>
> Per IEEE 1394 clause 8.4.2.3, a contender for the IRM role shall check
> whether the current IRM complies to 1394a-2000 or later. If not force a
> compliant node (e.g. itself) to become IRM. This was implemented in the
> older ieee1394 driver but not yet in firewire-core.
While I don't have an IRM that features the DCR-TRV25 bug, I did at
least quick tests of the patch with the following consistent results:
- Joined three nodes to a bus, only one node of them IRM capable,
but being a 1394-1995-only implementation.
- Plugged in Linux node into this bus, got the following log:
firewire_ohci: isochronous cycle inconsistent
firewire_core: created device fw8: GUID 00d04b21010212c8, S400
firewire_core: created device fw9: GUID 008088030960484b, S100
firewire_core: phy config: card 4, new root=ffc3, gap_count=7
firewire_core: IRM is not 1394a compliant, making local node (ffc1) root.
firewire_core: phy config: card 4, new root=ffc1, gap_count=7
and all is well as far as kernel, gscanbus, and Kino can tell.
--
Stefan Richter
-=====-==-=- -=-= ====-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2010-05-30 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimIFRbKWYjFd56acxT2A6nnH6l3-7Q_UyORnonW@mail.gmail.com>
[not found] ` <4C017477.8000008@s5r6.in-berlin.de>
[not found] ` <4C0284E7.3050803@s5r6.in-berlin.de>
2010-05-30 17:43 ` Stefan Richter
2010-05-30 17:56 ` Stefan Richter [this message]
[not found] ` <htu993$60f$1@dough.gmane.org>
2010-05-30 18:54 ` Stefan Richter
[not found] ` <htuebt$l80$1@dough.gmane.org>
2010-05-31 15:14 ` H.S.
[not found] ` <hu22tj$ne4$1@dough.gmane.org>
2010-06-02 18:26 ` Stefan Richter
2010-06-02 23:23 ` H.S.
[not found] ` <20101120202044.283f1212@stein>
[not found] ` <20110112151921.0a363daa@stein>
2011-01-15 17:19 ` [PATCH] firewire: core: fix unstable I/O with Canon camcorder Stefan Richter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tkrat.e4ca403b4d64cca4@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome