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: Mon, 31 May 2010 11:14:02 -0400 [thread overview]
Message-ID: <hu0jnr$10b$1@dough.gmane.org> (raw)
In-Reply-To: <htuebt$l80$1@dough.gmane.org>
H.S. wrote:
>
> I will report back how it goes as soon as I am able to do the experiments.
>
Well, good news. The patch seems to be worked as you designed.
Compiled the kernel with your patch, rebooted the machine and plugged in
the camcorder to the firewire port. This is what the log said:
May 31 11:06:47 red kernel: [ 924.228439] firewire_ohci: isochronous
cycle inconsistent
May 31 11:06:48 red kernel: [ 924.821383] firewire_core: created device
fw1: GUID 08004601024aca36, S100
May 31 11:06:48 red kernel: [ 924.821396] firewire_core: phy config:
card 0, new root=ffc1, gap_count=5
May 31 11:06:48 red kernel: [ 924.833768] firewire_core: IRM is not
1394a compliant, making local node (ffc0) root.
May 31 11:06:48 red kernel: [ 924.833777] firewire_core: phy config:
card 0, new root=ffc0, gap_count=5
And that is all it said ever after I captured a footage of some seconds.
I used the following command:
$> dvgrab -a -f raw -t video-
Then I switched off the camera, and still there were no messages in the log.
So, what is verdict?
Meanwhile, I will continue using this kernel.
Thanks.
--
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-05-31 16:15 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. [this message]
[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='hu0jnr$10b$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.