From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Wu Zhangjin <wuzhangjin@gmail.com>,
linux-mips@linux-mips.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] MIPS: fix pfn_valid() for FLAGMEM
Date: Fri, 09 Oct 2009 19:48:07 +0400 [thread overview]
Message-ID: <4ACF5B37.2040907@ru.mvista.com> (raw)
In-Reply-To: <4ACF5A10.3020406@ru.mvista.com>
Hello, I wrote:
>>>> Are the non-memory parts marked as reserved?
>>> No, so, is that a need to mark them?
>> Initially all pages are marked as reserved.
>> Which seems to be good enough for x86:
>> $ cat /proc/iomem
>> 00000000-0009efff : System RAM
>> 0009f000-0009ffff : reserved
>> 000c0000-000cffff : pnp 00:0d
>> 000e0000-000fffff : pnp 00:0d
>> 00100000-7fe5b7ff : System RAM
>> [...]
>> The 0x9f000 - 0x9ffff range is the good old ISA I/O memory range (classic
>> MDA/CGA/VGA etc.), that is non-memory yet:
>
>
> Not really, it's a usual RAM. CGA/VGA video memory occupies
Oh, I meant EGA/VGA. CGA memory is at 000b8000-000bffff, of course.
> 000a0000-000bffff and MDA occupies 000b0000-000b7ffff (if not less).
> This range is probably reserved by BIOS for something like EBDA...
Which stands for Extended BIOS Data Area.
WBR, Sergei
prev parent reply other threads:[~2009-10-09 15:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 8:57 [PATCH] MIPS: fix pfn_valid() for FLAGMEM Wu Zhangjin
2009-10-08 9:29 ` Pavel Machek
2009-10-08 10:33 ` Wu Zhangjin
2009-10-08 10:36 ` Pavel Machek
2009-10-08 10:57 ` Wu Zhangjin
2009-10-08 9:58 ` Sergei Shtylyov
2009-10-08 10:36 ` Wu Zhangjin
2009-10-08 14:42 ` Ralf Baechle
2009-10-08 15:46 ` Wu Zhangjin
2009-10-08 18:50 ` Ralf Baechle
2009-10-09 15:43 ` Sergei Shtylyov
2009-10-09 15:48 ` Sergei Shtylyov [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=4ACF5B37.2040907@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=pavel@ucw.cz \
--cc=ralf@linux-mips.org \
--cc=rjw@sisk.pl \
--cc=wuzhangjin@gmail.com \
/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).