From: "Rolf Liu" <rolfl@sc.mcel.mot.com>
To: <linuxppc-dev@lists.linuxppc.org>
Subject: separate kernel as code segment and data segment for linux ppc ?
Date: Thu, 4 Jan 2001 09:45:55 +0800 [thread overview]
Message-ID: <017b01c075f0$15265b50$bf0102c8@sc.mcel.mot.com> (raw)
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 !
BRs
Rolf Liu
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-01-04 1:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 1:45 Rolf Liu [this message]
2001-01-04 3:14 ` separate kernel as code segment and data segment for linux p Gary Thomas
2001-01-04 3:49 ` 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='017b01c075f0$15265b50$bf0102c8@sc.mcel.mot.com' \
--to=rolfl@sc.mcel.mot.com \
--cc=linuxppc-dev@lists.linuxppc.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).