Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Nemanja Popov <Nemanja.Popov@micronasnit.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Lexra' s MMU
Date: Mon, 3 Feb 2003 13:26:34 +0100	[thread overview]
Message-ID: <20030203132634.C18186@linux-mips.org> (raw)
In-Reply-To: <001701c2cb62$3eccd500$e000a8c0@micronasnit.com>; from Nemanja.Popov@micronasnit.com on Mon, Feb 03, 2003 at 09:57:02AM +0100

On Mon, Feb 03, 2003 at 09:57:02AM +0100, Nemanja Popov wrote:

>   Does Lexra's CPU LX4280 has MMU. I've found from dateaheet LX4280 that
> there is only SMMU (S stands for Simple) which does not include TLB and
> exceptions related to that.
>   I've noticed port for lexra (among others also for LX4280) on cvs. Is it
> possible to run linux on that kind of processor, and if so will it manage
> user space application as it should  with mmu.

TLB-less processors aren't supported at all by Linux 2.4.  Linux 2.5 has
the infrastructure in place to support TLB-less processors but we don't
support that on MIPS.  I guess it's probably not interesting because
TLB-less CPUs tend to be part of systems that are too resource constrained
to be of interest for use with Linux but I certainly wouldn't refuse such
patches.

The CVS kernel does not support Lexra processors.  There are a bit over one
year old Lexra patches for 2.4.  Me and the author agreed to not merge those
patches into the CVS kernel because Lexra is a dead company.

  Ralf

      parent reply	other threads:[~2003-02-03 12:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03  8:57 Lexra' s MMU Nemanja Popov
2003-02-03  8:57 ` Nemanja Popov
2003-02-03 12:26 ` Ralf Baechle [this message]

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=20030203132634.C18186@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=Nemanja.Popov@micronasnit.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