From: "H.S." <hs.samix@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux1394-devel@lists.sourceforge.net
Subject: Re: [PATCH] firewire: core: check for 1394a compliant IRM, fix inaccessibility of Sony camcorder
Date: Wed, 02 Jun 2010 19:23:51 -0400 [thread overview]
Message-ID: <hu6p68$ft0$1@dough.gmane.org> (raw)
In-Reply-To: <4C06A246.9030405@s5r6.in-berlin.de>
On 02/06/10 02:26 PM, Stefan Richter wrote:
>
> 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.
Great! I am glad I was able to help.
>
> 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.
Okay. Thanks again for the explanations.
Warm regards.
--
Please reply to this list only. I read this list on its corresponding
newsgroup on gmane.org. Replies sent to my email address are just
filtered to a folder in my mailbox and get periodically deleted without
ever having been read.
next prev parent reply other threads:[~2010-06-02 23:24 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 ` [PATCH] firewire: core: check for 1394a compliant IRM, fix inaccessibility of Sony camcorder 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
2010-06-02 23:23 ` H.S. [this message]
[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='hu6p68$ft0$1@dough.gmane.org' \
--to=hs.samix@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.