From: Pavel Machek <pavel@suse.cz>
To: Greg Ungerer <gerg@snapgear.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Conserving memory for an embedded application
Date: Mon, 30 Sep 2002 00:38:23 +0000 [thread overview]
Message-ID: <20020930003822.A35@toy.ucw.cz> (raw)
In-Reply-To: <3D9156E6.1030703@snapgear.com>; from gerg@snapgear.com on Wed, Sep 25, 2002 at 04:25:42PM +1000
Hi!
> >> 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.
> > The uclinux guys have eXecute In Place - google search for uclinux and XIP
> > will produce a stack of hits - here's one:
> > http://www.snapgear.com/tb20010618.html
>
> Yep, we have this for uClinux. Currently we are only doing
> this on MMU-less processors though, I haven't heard of anyone
> doing kernel (or apps) XIP from flash on VM processors.
I thought they were doing XIP on VTechHelio? That's MIPS39xx and has MMU.
See linux-vr project.
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2002-10-01 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 6:25 Conserving memory for an embedded application Greg Ungerer
2002-09-30 0:38 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-25 4:53 Michael D. Crawford
2002-09-24 21:59 ` Brad Hards
2002-09-25 0:52 ` Ralf Baechle
2002-09-25 5:18 ` Robert Schwebel
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=20020930003822.A35@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=gerg@snapgear.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).