linux-mips
[Top] [All Lists]

Re: [PATCH, RESEND] Add MWI workaround for Tulip DC21143

To: "P. Horton" <pdh@colonel-panic.org>
Subject: Re: [PATCH, RESEND] Add MWI workaround for Tulip DC21143
From: Martin Michlmayr <tbm@cyrius.com>
Date: Mon, 27 Mar 2006 08:01:12 +0100
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>
In-reply-to: <20060309224456.GB9103@electric-eye.fr.zoreil.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20060129230816.GD4094@colonel-panic.org> <20060218220851.GA1601@colonel-panic.org> <20060306225131.GA23327@unjust.cyrius.com> <20060306231530.GB16082@electric-eye.fr.zoreil.com> <20060307035824.GA24018@linux-mips.org> <Pine.LNX.4.62.0603071031520.5292@pademelon.sonytel.be> <20060308224139.GA7536@electric-eye.fr.zoreil.com> <Pine.LNX.4.62.0603091032490.9741@pademelon.sonytel.be> <20060309224456.GB9103@electric-eye.fr.zoreil.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.11+cvs20060126
* 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/

<Prev in Thread] Current Thread [Next in Thread>