From: Martin Michlmayr <tbm@cyrius.com>
To: "P. Horton" <pdh@colonel-panic.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
netdev@vger.kernel.org,
Linux/MIPS Development <linux-mips@linux-mips.org>,
Francois Romieu <romieu@fr.zoreil.com>
Subject: Re: [PATCH, RESEND] Add MWI workaround for Tulip DC21143
Date: Mon, 27 Mar 2006 08:01:12 +0100 [thread overview]
Message-ID: <20060327070112.GA10906@deprecation.cyrius.com> (raw)
In-Reply-To: <20060309224456.GB9103@electric-eye.fr.zoreil.com>
* Francois Romieu <romieu@fr.zoreil.com> [2006-03-09 23:44]:
> > So when compiling for Cobalt, we work around the hardware bug, while for other
> > platforms, we just disable MWI?
> >
> > Wouldn't it be possible to always (I mean, when a rev 65 chip is detected)
> > work around the bug?
>
> Of course it is possible but it is not the same semantic as the initial
> patch (not that I know if it is right or not).
>
> So:
> - does the issue exist beyond Cobalt hosts ?
> - is the fix Cobalt-only ?
I don't think anyone has replied to this message yet. My
understanding is that it's not Cobalt only but a problem in a specific
revision of the chip, which the Cobalt happens to use. However, I'd
be glad if somone else could comment. Peter, you read the errata
right?
--
Martin Michlmayr
http://www.cyrius.com/
next prev parent reply other threads:[~2006-03-27 11:03 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 ` [PATCH, RESEND] Add MWI workaround for Tulip DC21143 Martin Michlmayr
2006-03-06 23:15 ` 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 [this message]
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=20060327070112.GA10906@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=netdev@vger.kernel.org \
--cc=pdh@colonel-panic.org \
--cc=romieu@fr.zoreil.com \
/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.