linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "gongzhuo" <gongzhuo@163.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Does anyone know the memory mapping rules of linuxppc for mvme2600 ?
Date: Thu, 14 Sep 2000 09:29:15 +0800 (CST)	[thread overview]
Message-ID: <39C029EB.23243@bjsmtp3.163.net> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]


Hi:
  I'm sorry for the copies of my last mail . It seems to be the problem of my ISP.
  Does anyone know the memory mapping rules for linuxppc on MVME2600?
  If I want to write lkm to add some mappings in the kernel space for my hacking, what functions can I use for memory mapping ?




Thanks.
Gong Zhuo


-----------------------------------------------
163µç×ÓÓʾ֣¬¸øÄú¸üÍêÃÀEmail·þÎñ£¡
http://www.163.net


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-09-14  1:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-14  1:29 gongzhuo [this message]
2000-09-26 18:18 ` Does anyone know the memory mapping rules of linuxppc for mvme2600 ? Gabriel Paubert

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=39C029EB.23243@bjsmtp3.163.net \
    --to=gongzhuo@163.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).