Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Bob Lund" <bob.lund@visi.com>
To: <linux-mips@linux-mips.org>
Subject: Linux on LSI SC2005
Date: Sun, 17 Nov 2002 10:33:59 -0600	[thread overview]
Message-ID: <01cd01c28e57$21f37ee0$0a00000a@blund> (raw)

Hi,

I'm trying to figure out how much effort would be involved in getting Linux
running on the MIPS core found in the LSI Logic SC2005. According to the LSI
documentation:

MIPS R3000 CPU, executing MIPS I & II and 16 instructions
BBCC with four write back buffers included
Two 32-bit timers
MMU 64-entry TLB RAM
1 to 32 Kbytes of direct mapped or 2 to 64 Kbytes of set associative I-cache
1 to 32 Kbytes of direct mapped D-cache

Any information is appreciated.

Bob Lund

WARNING: multiple messages have this Message-ID (diff)
From: "Bob Lund" <bob.lund@visi.com>
To: linux-mips@linux-mips.org
Subject: Linux on LSI SC2005
Date: Sun, 17 Nov 2002 10:33:59 -0600	[thread overview]
Message-ID: <01cd01c28e57$21f37ee0$0a00000a@blund> (raw)
Message-ID: <20021117163359.YSz5tEHgk3hgEc4pq7K89JUlnq47dQkTVfNeOkp_n5w@z> (raw)

Hi,

I'm trying to figure out how much effort would be involved in getting Linux
running on the MIPS core found in the LSI Logic SC2005. According to the LSI
documentation:

MIPS R3000 CPU, executing MIPS I & II and 16 instructions
BBCC with four write back buffers included
Two 32-bit timers
MMU 64-entry TLB RAM
1 to 32 Kbytes of direct mapped or 2 to 64 Kbytes of set associative I-cache
1 to 32 Kbytes of direct mapped D-cache

Any information is appreciated.

Bob Lund

             reply	other threads:[~2002-11-17 16:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-17 16:33 Bob Lund [this message]
2002-11-17 16:33 ` Linux on LSI SC2005 Bob Lund
2002-11-18  3:49 ` Ralph Metzler
2002-11-18  3:49   ` Ralph Metzler
2002-11-18  8:58   ` Kevin D. Kissell
2002-11-18  8:58     ` Kevin D. Kissell

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='01cd01c28e57$21f37ee0$0a00000a@blund' \
    --to=bob.lund@visi.com \
    --cc=linux-mips@linux-mips.org \
    /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