Re: Mapping small memory region
- From: "Bruce Eitman \(eMVP\)" <beitmannospam@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 28 Apr 2005 09:42:37 -0400
Give us the big picture of what you are doing. What do you mean by map?
What do you mean by "small"? How do you plan to use the memory? What do
you mean by region?
Putting the region in OEMAddressTable is a possible solution, not the
problem that you are trying to solve. Assuming that you mean that this is a
fraction of your available RAM, then I would assume that the region is
already mapped in OEMAddressTable as part of your overall RAM, is that
correct?
--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net
Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member
"Helge Kruse" <Helge.Kruse-nospam@xxxxxxx> wrote in message
news:eYSv1E$SFHA.2872@xxxxxxxxxxxxxxxxxxxxxxx
> In my x86 OAL I need to map a small region of physical memory. The comment
> for OEMAddressTable requests for a multiple of 4M for each region. But the
> size of the region I need is only 4k.(FFFEF000-FFFEFFFF)
>
> What is the best way to map this small memory region?
>
> /Helge
>
>
>
.
- Follow-Ups:
- Re: Mapping small memory region
- From: Helge Kruse
- Re: Mapping small memory region
- References:
- Mapping small memory region
- From: Helge Kruse
- Mapping small memory region
- Prev by Date: Re: XXX_Open not being called !!
- Next by Date: Re: Why am I getting an assert when I try to Load a bitmap that I have added to the image?
- Previous by thread: Mapping small memory region
- Next by thread: Re: Mapping small memory region
- Index(es):
Relevant Pages
|
|
