mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: core: check for 1394a compliant IRM,	fix inaccessibility of Sony camcorder
Date: Wed, 02 Jun 2010 20:26:14 +0200	[thread overview]
Message-ID: <4C06A246.9030405@s5r6.in-berlin.de> (raw)
In-Reply-To: <hu22tj$ne4$1@dough.gmane.org>

H.S. wrote:
> H.S. wrote:
>> So, what is verdict?
> 
> Should have been "So, what is the verdict?"

I committed the patch to linux1394-2.6.git now, exposed it in the
linux-next branch, and will send a pull request sometime next week.

I marked the commit to be back-merged into the stable kernel branches
(2.6.32.y and newer).  Distributors will pick it up from there at their
leisure, or earlier if they get a distro bug report that points them to
the commit.

Thanks for testing the patched kernel.

> Anyway, just wanted to give a little additional information, in case
> this is significant. While testing the camcorder on a different Debian
> machine running Unstable and 2.6.32-5-686-bigmem kernel, I did not face
> the face problem I reported earlier. On this new machine, I was able to
> connect the camera and grab a footage using dvgrab. The syslog had this
> in it:
> May 30 19:31:42 blue kernel: [ 5203.926694] firewire_core: skipped bus generations, destroying all nodes
> May 30 19:31:42 blue kernel: [ 5204.424019] firewire_core: rediscovered device fw0
> May 30 19:31:42 blue kernel: [ 5204.516343] firewire_core: created device fw1: GUID 08004601024aca36, S100
> May 30 19:31:42 blue kernel: [ 5204.516346] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
> May 30 19:31:42 blue kernel: [ 5204.525209] firewire_core: skipped bus generations, destroying all nodes
> May 30 19:31:43 blue kernel: [ 5205.024019] firewire_core: rediscovered device fw0
> May 30 19:31:43 blue kernel: [ 5205.116912] firewire_core: rediscovered device fw1

I suppose either the local node became root node (node with highest node
ID) and thus the camcorder stopped doing bus management things, or the
camcorder chose the optimum gap count 5 for some reason and thus the
Linux node saw no reason to do its bus management routine.  If you are
very curious, you can look at node IDs and gap counts and more with the
FireWire inspection utility gscanbus.
-- 
Stefan Richter
-=====-==-=- -==- ---=-
http://arcgraph.de/sr/

  parent reply	other threads:[~2010-06-02 18:26 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
     [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 [this message]
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=4C06A246.9030405@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.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

all inboxes | Powered by JetHome®