public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Sat, 22 Mar 2008 23:38:30 -0400	[thread overview]
Message-ID: <47E5D0B6.6090307@redhat.com> (raw)
In-Reply-To: <47E4DDFB.4050600@s5r6.in-berlin.de>

Stefan Richter wrote:
> Jarod Wilson wrote:
>> Will double-check Monday that this solves never-ending (until panic) bus
> 
> s/that/whether/? :-)

Either one works here. I went with "that", because I'm reasonably 
certain that it does solve the problem and I'll just be confirming it, 
vs. suspecting it might and finding out whether it does or not... Or 
something like that. :)

>> 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
> 
> The wonders of brainstorming on IRC.  Let's implement all far-off and 
> weird ideas we can possibly get, distill those which don't cause 
> regressions, and we will end up with perfectly working drivers. :-)

Definitely! We've certainly been getting closer and closer, anyhow...

-- 
Jarod Wilson
jwilson@redhat.com

  reply	other threads:[~2008-03-23  3:39 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
2008-03-22 10:22   ` Stefan Richter
2008-03-23  3:38     ` Jarod Wilson [this message]
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=47E5D0B6.6090307@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