linux-mips-fnet
[Top] [All Lists]

Re: [update] [patch] linux: Cache coherency fixes

To: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
Subject: Re: [update] [patch] linux: Cache coherency fixes
From: Ralf Baechle <ralf@oss.sgi.com>
Date: Fri, 2 Aug 2002 12:16:00 +0200
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>, linux-mips@fnet.fr, linux-mips@oss.sgi.com
In-reply-to: <20020801170649.GB15334@rembrandt.csv.ica.uni-stuttgart.de>; from ica2_ts@csv.ica.uni-stuttgart.de on Thu, Aug 01, 2002 at 07:06:49PM +0200
References: <20020801152500.A31808@dea.linux-mips.net> <Pine.GSO.3.96.1020801173504.8256H-100000@delta.ds2.pg.gda.pl> <20020801184929.B22824@dea.linux-mips.net> <20020801170649.GB15334@rembrandt.csv.ica.uni-stuttgart.de>
User-agent: Mutt/1.2.5.1i
On Thu, Aug 01, 2002 at 07:06:49PM +0200, Thiemo Seufer wrote:

> [snip]
> > Back in time I prefered CONFIG_NONCOHERENT_IO over CONFIG_COHERENT_IO
> > because the noncoherent case needs additional code and in general I'm
> > trying to reduce the number of the #if !defined conditionals for easier
> > readability.
> > 
> > The R10000 is our standard example why looking at the processor type doesn't
> > work.  It's used in coherent mode in IP27 but in coherent mode but in
> > coherent mode in IP28 or IP32.  Otoh I don't know of any system that
> 
> JFTR: non-coherent mode in IP28 or IP32.

Yep, you're right.  I hope everybody concluded that from my non-coherent
sentence ;-)

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