On Tue, 3 Feb 2004, Ralf Baechle wrote: > Under a different bug number this bug also affects the R4600 V1.x; it's > fixed in post-2.0 R4600 (which all identify as 2.0) and post-1.1 R4700. > Since a workaround may be a bit performance sensitive I think I'll try if > it can be probed for reliably. The conditions appear clear, so they may be quite easy to reproduce for the erratum to trigger. I guess you may take the optimization hint from the document into account as well. -- + Maciej W. Rozycki, Technical University of Gdansk, Poland + +--------------------------------------------------------------+ + e-mail: macro@ds2.pg.gda.pl, PGP key available +
