The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jarod Wilson <jwilson@redhat.com>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firewire: fw-ohci: TSB43AB22/A dualbuffer workaround
Date: Wed, 23 Jul 2008 01:05:36 +0200	[thread overview]
Message-ID: <488667C0.5070708@s5r6.in-berlin.de> (raw)
In-Reply-To: <200807221811.26653.jwilson@redhat.com>

Jarod Wilson wrote:
> Still hoping we can get some confirmation of a chipset bug or a fix from TI 
> for this controller,

Well, indeed, a chipset/board bug isn't entirely ruled out yet.  But 
given that data buffers above 2G don't hurt, only descriptors do, the 
controller is definitely the primary suspect here.
-- 
Stefan Richter
-=====-==--- -=== =-===
http://arcgraph.de/sr/

      reply	other threads:[~2008-07-22 23:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 16:41 [PATCH] firewire: fw-ohci: TSB43AB22/A dualbuffer workaround Stefan Richter
2008-07-22 22:11 ` Jarod Wilson
2008-07-22 23:05   ` Stefan Richter [this message]

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=488667C0.5070708@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=jwilson@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox