diff --git a/Documentation/NuttxPortingGuide.html b/Documentation/NuttxPortingGuide.html index fc6a4c82b3..a77df7f0fd 100644 --- a/Documentation/NuttxPortingGuide.html +++ b/Documentation/NuttxPortingGuide.html @@ -12,7 +12,7 @@
Last Updated: June 11, 2013
+Last Updated: July 26, 2013
@@ -4367,12 +4367,12 @@ void (*notify)(FAR struct pm_callback_s *cb, enum pm_state_e pmstate); Some architectures require a description of the RAM configuration:CONFIG_DRAM_SIZE
:
- Describes the installed DRAM.CONFIG_DRAM_START
:
- The start address of DRAM (physical)CONFIG_DRAM_VSTART
:
- The start address of DRAM (virtual)CONFIG_RAM_SIZE
:
+ Describes the primary installed RAM.CONFIG_RAM_START
:
+ The start address of primary RAM (physical)CONFIG_RAM_VSTART
:
+ The start address of primary RAM (virtual). This is only needed on platforms that support address mapping.CONFIG_PAGING_NLOCKED
:
This is the number of locked pages in the memory map.
- The locked address region will then be from CONFIG_DRAM_VSTART
through
- (CONFIG_DRAM_VSTART
+ CONFIG_PAGING_PAGESIZE
*CONFIG_PAGING_NLOCKED
)
+ The locked address region will then be from CONFIG_RAM_VSTART
through
+ (CONFIG_RAM_VSTART
+ CONFIG_PAGING_PAGESIZE
*CONFIG_PAGING_NLOCKED
)
CONFIG_PAGING_LOCKED_PBASE
and CONFIG_PAGING_LOCKED_VBASE
:
These may be defined to determine the base address of the locked page regions.
- If neither are defined, the logic will be set the bases to CONFIG_DRAM_START
- and CONFIG_DRAM_VSTART
(i.e., it assumes that the base address of the locked
+ If neither are defined, the logic will be set the bases to CONFIG_RAM_START
+ and CONFIG_RAM_VSTART
(i.e., it assumes that the base address of the locked
region is at the beginning of RAM).
NOTE:
In some architectures, it may be necessary to take some memory from the beginning