From: Kent Borg <kentborg@borg.org>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Hardcoded Hash_base?
Date: Thu, 13 Mar 2003 12:22:32 -0500 [thread overview]
Message-ID: <20030313122232.F3222@borg.org> (raw)
In arch/ppc/mm/hashtable.S Hash_base is hardcoded at 0xc0180000, with
a comment suggesting that that value is "just an example". It seems
to be colliding with my initrd, so I am thinking I want to move it.
What restrictions are there for where it goes? Why doesn't it get
defined from the link? How is it that other things are supposed to be
kept clear of it? (Because it is in an mm-directory, does that mean
that the memory manager knows not to allocate that RAM?)
Thanks for any help,
-kb
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-03-13 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 17:22 Kent Borg [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-13 17:44 Hardcoded Hash_base? Jean-Denis Boyer
2003-03-13 22:06 ` Kent Borg
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=20030313122232.F3222@borg.org \
--to=kentborg@borg.org \
--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).