Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: sathis kanna <sathiskanna@yahoo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: physical memory Limitation
Date: Thu, 4 Mar 2004 08:59:06 +0100	[thread overview]
Message-ID: <20040304075906.GB23688@linux-mips.org> (raw)
In-Reply-To: <20040303153505.2825.qmail@web14913.mail.yahoo.com>

On Wed, Mar 03, 2004 at 07:35:05AM -0800, sathis kanna wrote:

> For mips,
> is there any limitation for physical memory while
> uncomressing the image??(like i386 it is 4MB)
> 
> How to locate in code written in the kernel source?

We currently don't support compressed kernels.

But if we were supporting it the limitation would depend on size of
available memory and how it's used at boot time, that is the limit would
depend on the exact system.

  Ralf

  reply	other threads:[~2004-03-04  7:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03 15:35 physical memory Limitation sathis kanna
2004-03-04  7:59 ` Ralf Baechle [this message]
2004-03-04 16:56   ` Dan Malek

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=20040304075906.GB23688@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=sathiskanna@yahoo.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