linux-mips
[Top] [All Lists]

Re: O2 RM7000 Issues

To: sknauert@wesleyan.edu
Subject: Re: O2 RM7000 Issues
From: Ralf Baechle <ralf@linux-mips.org>
Date: Wed, 4 Jul 2007 16:27:29 +0100
Cc: Linux MIPS List <linux-mips@linux-mips.org>
In-reply-to: <50451.70.107.91.207.1183381723.squirrel@webmail.wesleyan.edu>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <4687DCE2.8070302@gentoo.org> <468825BE.6090001@gmx.net> <50451.70.107.91.207.1183381723.squirrel@webmail.wesleyan.edu>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.14 (2007-02-12)
On Mon, Jul 02, 2007 at 09:08:43AM -0400, sknauert@wesleyan.edu wrote:
> From: sknauert@wesleyan.edu
> Date: Mon, 2 Jul 2007 09:08:43 -0400 (EDT)
> To: Linux MIPS List <linux-mips@linux-mips.org>
> Subject: Re: O2 RM7000 Issues
> Content-Type: text/plain;charset=UTF-8
> 
> I have one of the 600 Mhz RM7000s, i.e. no tertiary cache since the module
> was originally a 300 Mhz RM5200. However, mine hasn't given any problems
> with Debian or Gentoo.
> 
> What kernel and target are you compiling for? I'm using 2.6.21.3 compiled
> for R5K. All my userspace is compiled for R5K too. I'll compile a new
> kernel for RM7000 and see if I have any issue then poke around to see what
> kernel code gets changed. I'm not 100% sure, but I didn't think it was
> that much so my gut reaction is this might be a gcc issue since the RM7000
> isn't a common processor.

R5000, RM5200 and RM7000 are all MIPS IV processors so have the same
instruction set.  That leaves the usual suspects - pipeline hazards,
cache problems and CPU bugs to research.

  Ralf

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