From: Dan Malek <dan@mvista.com>
To: Borlizzi Giacomo <giacomo.borlizzi@tei.ericsson.se>
Cc: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: KERNELBASE and MMU
Date: Wed, 17 Jan 2001 13:54:32 -0500 [thread overview]
Message-ID: <3A65EA68.F75481A2@mvista.com> (raw)
In-Reply-To: 3A65E51B.50FC28EC@tei.ericsson.se
Borlizzi Giacomo wrote:
>
> Does you say that linux code is not PIC? (position indipendent code)
No it is not. You can move it around a little if you _really_
understand the details. For any PowerPC processor there is no
reason to change the location regardless of the system implementation.
> Why such constraint on physical memory area? It don't make some
> limitation on portability of code?
No portability problem. This code runs on more processors and
boards more easily than anything else in the world.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-01-17 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 17:31 KERNELBASE and MMU Borlizzi Giacomo
2001-01-16 22:16 ` Dan Malek
2001-01-17 18:31 ` Borlizzi Giacomo
2001-01-17 18:54 ` Dan Malek [this message]
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=3A65EA68.F75481A2@mvista.com \
--to=dan@mvista.com \
--cc=giacomo.borlizzi@tei.ericsson.se \
--cc=linuxppc-embedded@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).