netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Michlmayr <tbm@cyrius.com>
To: netdev@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: [PATCH, RESEND] Add MWI workaround for Tulip DC21143
Date: Mon, 6 Mar 2006 22:51:31 +0000	[thread overview]
Message-ID: <20060306225131.GA23327@unjust.cyrius.com> (raw)
In-Reply-To: <20060218220851.GA1601@colonel-panic.org>

* Peter Horton <pdh@colonel-panic.org> [2006-02-18 22:08]:
> This patch works around the MWI bug on the DC21143 rev 65 Tulip by
> ensuring that the receive buffers don't end on a cache line boundary (as
> documented in the errata).
> 
> This patch is required for the MIPs based Cobalt Qube/RaQ as supporting
> the extra PCI commands seems to reduce the chance of a hard lockup
> between the Tulip and the PCI bridge.

Does anyone have comments regarding this patch?  I received
confirmation from a number of Debian users that this patch
significantly improves the lockup situation on Cobalt, so
it would be nice if it could go in.
-- 
Martin Michlmayr
tbm@cyrius.com

       reply	other threads:[~2006-03-06 22:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060129230816.GD4094@colonel-panic.org>
     [not found] ` <20060218220851.GA1601@colonel-panic.org>
2006-03-06 22:51   ` Martin Michlmayr [this message]
2006-03-06 23:15     ` [PATCH, RESEND] Add MWI workaround for Tulip DC21143 Francois Romieu
2006-03-07  3:58       ` Ralf Baechle
2006-03-07  9:32         ` Geert Uytterhoeven
2006-03-08 22:41           ` Francois Romieu
2006-03-09  9:37             ` Geert Uytterhoeven
2006-03-09 22:44               ` Francois Romieu
2006-03-27  7:01                 ` Martin Michlmayr
2006-03-27 12:39                   ` Peter Horton

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=20060306225131.GA23327@unjust.cyrius.com \
    --to=tbm@cyrius.com \
    --cc=linux-mips@linux-mips.org \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).