Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Crossfire <xfire@xware.cx>
To: kjlin <kj.lin@viditec-netmedia.com.tw>
Cc: linux-mips@oss.sgi.com
Subject: Re: Does linux support for microprocessor without MMU?
Date: Thu, 22 Feb 2001 13:36:02 +1100	[thread overview]
Message-ID: <20010222133602.A24899@eris.xware.cx> (raw)
In-Reply-To: <00ba01c09c6e$84788380$056aaac0@kjlin>; from kj.lin@viditec-netmedia.com.tw on Thu, Feb 22, 2001 at 09:26:44AM +0800

kjlin was once rumoured to have said:
> Howdy,
> 
> I got an embedded MIPS board recently.
> It has the following features:
> - CPU implements a five-stage pipeline with performance similar to the MIPS R3000 pipeline.
> - MIPS32 compatible instruction set
> - R4000 style privileged resource architecture.
> - Without MMU.
> 
> I am estimating the possibility of porting linux on it.
> Can Linux/MIPS 2.2 or 2.4 support for such a board which without MMU ?
> Because i consider it is the most difficult part in the porting process.
> Am i right?

the Standard Linux kernels all require an MMU.  However, there is a
version of the kernel known as "ucLinux" (Microcontroller Linux) which
will run on CPUs without MMU.

I don't know if ucLinux has a MIPS target yet.

C.
-- 
--==============================================--
  Crossfire      | This email was brought to you
  xfire@xware.cx | on 100% Recycled Electrons
--==============================================--

  parent reply	other threads:[~2001-02-22  2:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-22  1:26 Does linux support for microprocessor without MMU? kjlin
2001-02-22  1:26 ` kjlin
2001-02-22  2:36 ` Crossfire [this message]
2001-02-22  4:15   ` Joe deBlaquiere
2001-02-22  6:53     ` Geert Uytterhoeven
2001-02-23  5:42       ` Joe deBlaquiere
2001-02-26  9:17         ` kjlin
2001-02-26  9:17           ` kjlin

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=20010222133602.A24899@eris.xware.cx \
    --to=xfire@xware.cx \
    --cc=kj.lin@viditec-netmedia.com.tw \
    --cc=linux-mips@oss.sgi.com \
    /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