From: Martin Michlmayr Subject: Re: [PATCH, RESEND] Add MWI workaround for Tulip DC21143 Date: Mon, 27 Mar 2006 08:01:12 +0100 Message-ID: <20060327070112.GA10906@deprecation.cyrius.com> 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> <20060308224139.GA7536@electric-eye.fr.zoreil.com> <20060309224456.GB9103@electric-eye.fr.zoreil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Geert Uytterhoeven , netdev@vger.kernel.org, Linux/MIPS Development , Francois Romieu Return-path: To: "P. Horton" Content-Disposition: inline In-Reply-To: <20060309224456.GB9103@electric-eye.fr.zoreil.com> Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org List-Id: netdev.vger.kernel.org * Francois Romieu [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/