From: Borlizzi Giacomo <giacomo.borlizzi@tei.ericsson.se>
To: Dan Malek <dan@mvista.com>
Cc: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>,
"Giacomo Borlizzi (TEI)" <giacomo.borlizzi@tei.ericsson.se>
Subject: Re: KERNELBASE and MMU
Date: Wed, 17 Jan 2001 19:31:55 +0100 [thread overview]
Message-ID: <3A65E51B.50FC28EC@tei.ericsson.se> (raw)
In-Reply-To: 3A64C847.D2414D1D@mvista.com
Does you say that linux code is not PIC? (position indipendent code)
Why such constraint on physical memory area? It don't make some
limitation on portability of code?
/Giacomo Borlizzi
Dan Malek wrote:
> Borlizzi Giacomo wrote:
>
> > My configuration foreseen KERNELBASE set to 0x00000000 instead of
> > 0xC0000000
>
> I don't really understand, but you should not be changing anything
> in the source code or Makefiles or configuration files that affect
> the MMU or virtual address mapping.
>
> -- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-17 18:31 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 [this message]
2001-01-17 18:54 ` Dan Malek
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=3A65E51B.50FC28EC@tei.ericsson.se \
--to=giacomo.borlizzi@tei.ericsson.se \
--cc=dan@mvista.com \
--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).