From: "zzh" <david-1z@263.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: memory map
Date: Fri, 21 Apr 2000 17:49:21 +0800 (CST) [thread overview]
Message-ID: <39002421.07687@mta1> (raw)
Hi,everyone.
I have some questions about the memory map on linux on 8xx and ppc
1)Some area eg BCSR mapped below KERNELBASE,is this safe?
I check some process's vm area,it does not fall in this area,will
it be unsafe under some circumstances?
2)I read mapin_ram() in mm/init.c ,found that phys mem is also mapped
both by bat and page table ,what is this for?
Can someone help me?
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-04-21 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-21 9:49 zzh [this message]
2000-04-21 16:58 ` memory map Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2000-04-24 3:24 zzh
2000-04-24 3:54 ` Dan Malek
2000-04-23 22:16 ` Steve Tarr
2000-04-24 16:07 ` Dan Malek
2000-04-24 5:11 Shuangjun Zhu
2000-04-24 16:09 ` Dan Malek
2000-04-25 9:31 zzh
2000-04-25 17:05 ` Dan Malek
2000-11-27 19:04 Memory map Konstantin Sabodash
2000-11-27 19:22 ` 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=39002421.07687@mta1 \
--to=david-1z@263.net \
--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).