From: Ralf Baechle <ralf@linux-mips.org>
To: Chris Boot <bootc@bootc.net>
Cc: linux-mips@linux-mips.org
Subject: Re: Execute-in-Place (XIP)
Date: Thu, 27 Oct 2005 11:29:12 +0100 [thread overview]
Message-ID: <20051027102912.GB17645@linux-mips.org> (raw)
In-Reply-To: <18E0376E-A524-42EE-A5ED-BDF9A0668DE6@bootc.net>
On Thu, Oct 27, 2005 at 10:02:40AM +0100, Chris Boot wrote:
> Due to the puny amounts of RAM (2MB) on my board, I'm going to have
> to use XIP so that RAM isn't being taken up by kernel code. I was
> looking around for MIPS XIP patches and all I could find was in the
> linux-vr tree which seems, well, dead.
The linux-vr tree is kept online for people to dig out the goodies which
may be left in there :-)
> Does anyone know of any more
> recent patches or should I undertake the work of porting the patch to
> a more recent 2.4 kernel?
I guess you'll have to do that. The alternative would be to port the
2.6 ARM XIP_KERNEL implementation.
Ralf
next prev parent reply other threads:[~2005-10-27 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 9:02 Execute-in-Place (XIP) Chris Boot
2005-10-27 10:29 ` Ralf Baechle [this message]
2005-10-28 22:20 ` Chris Boot
2005-10-28 22:51 ` Chris Boot
2005-10-28 23:08 ` David Daney
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=20051027102912.GB17645@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=bootc@bootc.net \
--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