linux-mips
[Top] [All Lists]

Re: 2.6 on IP22 (Indy)

To: Markus Dahms <mad@automagically.de>
Subject: Re: 2.6 on IP22 (Indy)
From: "Maciej W. Rozycki" <macro@linux-mips.org>
Date: Wed, 29 Jun 2005 17:54:25 +0100 (BST)
Cc: linux-mips@linux-mips.org
In-reply-to: <20050628170425.GA5189@gaspode.automagically.de>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20050627100757.GA27679@gaspode.automagically.de> <Pine.LNX.4.61L.0506271401280.15406@blysk.ds.pg.gda.pl> <20050627141842.GA28236@gaspode.automagically.de> <Pine.LNX.4.61L.0506271632380.23903@blysk.ds.pg.gda.pl> <20050628062107.GA8665@gaspode.automagically.de> <Pine.LNX.4.61L.0506280918380.13758@blysk.ds.pg.gda.pl> <20050628102013.GA10442@gaspode.automagically.de> <Pine.LNX.4.61L.0506281204190.13758@blysk.ds.pg.gda.pl> <20050628170425.GA5189@gaspode.automagically.de>
Sender: linux-mips-bounce@linux-mips.org
Hello Markus,

> I think I found the trick. Just following the hint that the R4600
> is similar to the R5000 I added CPU_R4600 to build_tlb_probe_entry().

 Well, they are not meant to be errata-compatible. ;-)  I haven't been 
able to locate any reference for tlbp being problematic on the R4600, in 
particular not in the chip errata document, and the old handlers used to 
have a nop before that instruction unconditionally (perhaps just in case 
;-) ), so the problem was covered.  If it fixes the problem for you, then 
it should probably be applied, too.  Not sure about the R4700 -- it fixed 
a few problems that were there in the R4600 as a side effect, so perhaps 
we should wait for some report first.

  Maciej

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