View Single Post
  #5533 (permalink)  
Old 06-29-2009, 03:59 PM
joojoobee666's Avatar
joojoobee666
PPCKitchen Crew
Offline
Location: Ohio
 
Join Date: Jul 2008
Posts: 1,442
Reputation: 10635
joojoobee666 can't get a higher reputation leveljoojoobee666 can't get a higher reputation leveljoojoobee666 can't get a higher reputation leveljoojoobee666 can't get a higher reputation leveljoojoobee666 can't get a higher reputation leveljoojoobee666 can't get a higher reputation leveljoojoobee666 can't get a higher reputation leveljoojoobee666 can't get a higher reputation leveljoojoobee666 can't get a higher reputation leveljoojoobee666 can't get a higher reputation leveljoojoobee666 can't get a higher reputation level
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Re: WM 6.5 Kitchen QVGA and VGA Developer Edition

Quote:
Originally Posted by Da_G View Post
Re: Virtual Memory slots, it's actually 2 new slots, slot 60 (0x78000000-0x79FFFFFF) and slot 61 (0x7A000000 – 0x7BFFFFFF).

You are correct about 4kb block size, each new slot is 32mb, for a total of 64mb gained virtual memory
Not to bring back some old stuff, but I had a question on this. According to CMonex, Slot 0 and Slot 1 are defined by the .VM folder (specifically the imageinfo.bin) and this is what G'Reloc/WMReloc use to allocate. For example, my imageinfo.bin defines Slot 0 as 0x01F80000 to 0x00000000 and Slot 1 as 03D70000 to 0x02000000. This is for the 6.1 Kernel. Apparently, G'Reloc will then allocate SYS modules ONLY to these two slots when allocating.

Are you saying that WMReloc will also assign SYS modules to the 60 and 61 Slots as well now? After some further reading, slot 60 and 61 are not new to 6.5 as 6.1 and 6.5 use them for DLL's and EXE's that are larger than 64KB to free up Slot 0 to reduce the DLL crunch and VM memory pressure. So is the only difference that the 6.5 kernel allows you to allocate into those slots as well since they are not new? Anyone that knows my chime in


Reply With Quote