Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: sknauert@wesleyan.edu
Cc: Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: O2 RM7000 Issues
Date: Wed, 4 Jul 2007 16:27:29 +0100	[thread overview]
Message-ID: <20070704152729.GA2925@linux-mips.org> (raw)
In-Reply-To: <50451.70.107.91.207.1183381723.squirrel@webmail.wesleyan.edu>

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

  reply	other threads:[~2007-07-04 15:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-01 16:57 O2 RM7000 Issues Kumba
2007-07-01 22:07 ` freshy98
2007-07-02 13:08   ` sknauert
2007-07-02 13:08   ` sknauert
2007-07-04 15:27     ` Ralf Baechle [this message]
2007-07-04 19:22       ` Ralf Baechle
2007-07-16 11:53         ` Sergey Rogozhkin
2007-07-16 12:33           ` Ralf Baechle
2007-07-16 17:38             ` Andrew Sharp
2007-07-17 14:01               ` Kumba
2007-07-19 18:58                 ` Andrew Sharp
2007-07-19 22:26                   ` Shane McDonald
2007-07-17  7:54             ` Gleb O. Raiko
2007-07-17  9:04         ` Sergey Rogozhkin
2007-07-17 10:14           ` Ralf Baechle
2007-07-17 12:27           ` Ralf Baechle
2007-09-17 23:04             ` Steve Graham
2007-09-18  8:52               ` Ralf Baechle
2007-09-17 23:20             ` David Daney
2007-09-18  8:47               ` Ralf Baechle
2007-07-02 14:34 ` Maciej W. Rozycki
2007-09-21  6:27 ` Sagar Borikar
2007-09-21 13:47   ` Ralf Baechle
2007-09-22  3:20     ` Steve Graham
2007-09-24 11:58       ` Ralf Baechle
2007-09-26 17:06         ` Steve Graham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070704152729.GA2925@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=sknauert@wesleyan.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox