From: Timur Tabi <ttabi@interactivesi.com>
To: linux-mm@kvack.org
Subject: Re: How can I support memory hole in embedded system?
Date: Tue, 26 Jun 2001 11:16:30 -0500 [thread overview]
Message-ID: <XjIWBD.A.CUD.iVLO7@dinero.interactivesi.com> (raw)
In-Reply-To: <002001c02756$fe0b5480$671a6e0a@huawei.com.cn>
** Reply to message from "dony" <dony.he@huawei.com> on Tue, 26 Sep 2000
09:13:33 +0800
> I think we can modify the memory-mapping to support memory hole, but
> I don't know how to do it. In mm/bootmem.c it also mentions it can support
> memory hole with no more comments.
> Can you give me some information in detail about this? Thank you
> very much.
Just modify the E820 structure after setup.S calls the BIOS INT 15 routine.
--
Timur Tabi - ttabi@interactivesi.com
Interactive Silicon - http://www.interactivesi.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
prev parent reply other threads:[~2001-06-26 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-26 1:13 dony
2000-09-26 15:41 ` Timur Tabi
2001-06-26 16:16 ` Timur Tabi [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=XjIWBD.A.CUD.iVLO7@dinero.interactivesi.com \
--to=ttabi@interactivesi.com \
--cc=linux-mm@kvack.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