From: Gary Thomas <gthomas@redhat.com>
To: Rolf Liu <rolfl@sc.mcel.mot.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: RE: separate kernel as code segment and data segment for linux p
Date: Wed, 03 Jan 2001 20:14:04 -0700 (MST) [thread overview]
Message-ID: <XFMail.20010103201404.gthomas@redhat.com> (raw)
In-Reply-To: <017b01c075f0$15265b50$bf0102c8@sc.mcel.mot.com>
On 04-Jan-2001 Rolf Liu wrote:
>
> Hi,all,
> I am planning to run linux-ppc on ppc823 FADS board.
> As all know, the kernel is resided in flash rom, then upon power-on, kernel
> is copied to RAM.
> I wonder if I can just put data segment to ram and leave code segment to
> FLASH, just as uClinux
> has done. such method will save some ram space, which makes sense on
> embedded solutions.
> Can you give me a hint how to realize it ?
> Any suggestion is appreciated !
This method is called XIP (for execute in place) and is available on
some other architectures. I don't know what it would take for the PPC,
but you could look at the work done on the Hitachi SH - I know it's supported
there.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-04 3:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 1:45 separate kernel as code segment and data segment for linux ppc ? Rolf Liu
2001-01-04 3:14 ` Gary Thomas [this message]
2001-01-04 3:49 ` separate kernel as code segment and data segment for linux p Rolf Liu
2001-01-04 4:07 ` Critical section - pSOS+ Srinivas Rao.M
2001-01-04 21:03 ` Jerry Van Baren
2001-01-05 5:19 ` Srinivas Rao.M
2001-01-04 18:07 ` separate kernel as code segment and data segment for linux p Dan Malek
2001-01-04 8:50 ` separate kernel as code segment and data segment for linux ppc ? Wolfgang Denk
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=XFMail.20010103201404.gthomas@redhat.com \
--to=gthomas@redhat.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rolfl@sc.mcel.mot.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;
as well as URLs for NNTP newsgroup(s).