linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Michael D. Crawford" <crawford@goingware.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Conserving memory for an embedded application
Date: Wed, 25 Sep 2002 02:52:38 +0200	[thread overview]
Message-ID: <20020925025237.A30316@linux-mips.org> (raw)
In-Reply-To: <3D91413C.1050603@goingware.com>; from crawford@goingware.com on Wed, Sep 25, 2002 at 12:53:16AM -0400

On Wed, Sep 25, 2002 at 12:53:16AM -0400, Michael D. Crawford wrote:

> on.  An important concern is to minimize the amount of ROM and flash ram that 
> the device has, both to save manufacturing cost and to minimize power consumption.
> 
> One question I have is whether it is possible to burn an uncompressed image of 
> the kernel into flash, and then boot the kernel in-place, so that it is not 
> copied to RAM when it runs.  Of course the kernel would need RAM for its data 
> structures and user programs, but it would seem to me I should be able to run 
> the kernel without making a RAM copy.

Flash is much slower than normal memory so if you want any performance
beyond the level of Eniac I suggest to copy it to RAM ...

> don't think the user program would be very large.
> 
> Also, what is the minimum amount of physical ram that you think I can get any 
> version of the kernel later than 2.0 or so to run in?  I heard somewhere that 
> someone can boot an x86 system with as little as 2MB of RAM.  Is that the case?

That's rather old kernels and also heavily hacked.

  Ralf

  parent reply	other threads:[~2002-09-25  0:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25  4:53 Michael D. Crawford
2002-09-24 21:59 ` Brad Hards
2002-09-25  0:52 ` Ralf Baechle [this message]
2002-09-25  5:18 ` Robert Schwebel
2002-09-25  6:25 Greg Ungerer
2002-09-30  0:38 ` Pavel Machek

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=20020925025237.A30316@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=crawford@goingware.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Conserving memory for an embedded application' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).