From: Jarod Wilson <jwilson@redhat.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: wait until PHY configuration packet was transmitted
Date: Fri, 21 Mar 2008 23:12:41 -0400 [thread overview]
Message-ID: <200803212312.41277.jwilson@redhat.com> (raw)
In-Reply-To: <tkrat.47c2348a94015e02@s5r6.in-berlin.de>
On Thursday 20 March 2008 06:48:23 pm Stefan Richter wrote:
> We now exit fw_send_phy_config /after/ the PHY config packet has been
> transmitted, instead of before. A subsequent fw_core_initiate_bus_reset
> will therefore not overlap with the transmission. This is meant to make
> the send PHY config packet + reset bus routine more deterministic.
>
> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Will double-check Monday that this solves never-ending (until panic) bus
resets with a jmicron controller in the office, but this does indeed prevent
a very similar looking case with a via vt6307 ohci 1.0 controller + iogear
hub + unibrain fire-i camera:
http://bugzilla.kernel.org/show_bug.cgi?id=10128
Wondering if this will be the ticket for nForce2 controllers as well. Still
trying to track one down to poke at myself, although we can probably find
someone out there to test. Also wondering how we hold up against a bus reset
storm initiated by another host, thinking maybe we can still trigger the
list_add corruption in that bug, but stopping the endless bus reset loops is
definitely an improvement.
Signed-off-by: Jarod Wilson <jwilson@redhat.com>
--
Jarod Wilson
jwilson@redhat.com
next prev parent reply other threads:[~2008-03-22 3:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 22:48 [PATCH] firewire: wait until PHY configuration packet was transmitted Stefan Richter
2008-03-22 3:12 ` Jarod Wilson [this message]
2008-03-22 10:22 ` Stefan Richter
2008-03-23 3:38 ` Jarod Wilson
2008-03-24 13:04 ` Jarod Wilson
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=200803212312.41277.jwilson@redhat.com \
--to=jwilson@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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