View Single Post
  #5 (permalink)  
Old 02-27-2008, 12:08 PM
willysp's Avatar
willysp
A Geek For Eons
Offline
Location: Central Indiana
 
Join Date: Dec 2006
Posts: 1,576
Reputation: 1015
willysp is halfway to VIP status based on repwillysp is halfway to VIP status based on repwillysp is halfway to VIP status based on repwillysp is halfway to VIP status based on repwillysp is halfway to VIP status based on repwillysp is halfway to VIP status based on repwillysp is halfway to VIP status based on repwillysp is halfway to VIP status based on rep
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Challange to all the rom chefs

FWIW - a good explanation of XIP and Page Pool

The Page Pool
Applications use RAM in two ways. There is code that runs, and there is data that is created while it is running. On a NOR device, the code can run directly from the ROM and not be loaded into RAM first. This process is called XIP (eXecute In Place). NAND devices can't XIP, so their code is loaded into RAM and executed from there. If you don't have a Page Pool, this code is loaded into normal RAM. The Page Pool is a mechanism to limit how much code is loaded into normal RAM. With a Page Pool, we can unload code that hasn't been used in a while and reload it later if we need to. We can't do that without a Page Pool.


http://blogs.msdn.com/windowsmobile/...17/494177.aspx