Memory layout: Difference between revisions
m This is explained on the SVC page now. |
No edit summary |
||
| Line 797: | Line 797: | ||
For NATIVE_FIRM the memory pages for this region are located in FCRAM, however for TWL_FIRM these are located in AXI WRAM. For TWL_FIRM v6704 the first thread's page for this region is located at physical address 0x1FF93000, the next one at 0x1FF92000, etc. | For NATIVE_FIRM the memory pages for this region are located in FCRAM, however for TWL_FIRM these are located in AXI WRAM. For TWL_FIRM v6704 the first thread's page for this region is located at physical address 0x1FF93000, the next one at 0x1FF92000, etc. | ||
== IO Process/Kernel virtual addressing equivalence == | |||
It seems an IO register's process virtual address can be calculated by adding 0xEB00000 to its physical address. | |||
=ARM11 User-land memory regions= | =ARM11 User-land memory regions= | ||
| Line 996: | Line 999: | ||
0x8000044 Pointer to the current KProcess instance on the ARM9 | 0x8000044 Pointer to the current KProcess instance on the ARM9 | ||
0x8000048 Pointer to the current KScheduler instance on the ARM9 | 0x8000048 Pointer to the current KScheduler instance on the ARM9 | ||
= VRAM Map While Running System Applets = | = VRAM Map While Running System Applets = | ||