Why is the CMEM heap buffer address not within my specified range of CMEM physical addresses?
The CMEM kernel module cmemk.ko prints a banner upon being inserted into the kernel, and within that banner is a line of the form “allocated heap buffer 0xc7000000 of size 0x8ac000”. The heap buffer address printed here is not the physical address – it is the kernel’s assigned virtual address, and this kernel virtual address can just happen to coincide with the physical address range specified by phys_start/phys_end parameters for the cmemk.ko ‘insmod’ command. In fact, the virtual address suggested above (0xc7000000) lies within the available physical address range of the DDR2 memory on the OMAP-L138 EVM.
Related Questions
- The Address Range relationship file often lists several address ranges for each edge. Which address ranges should I use to geocode addresses?
- Where multiple addresses are provided on a content entry screen, what is the standard of usage eg: physical address first then postal?
- When I look up addresses in StreetFinder for the Palm OS, it only shows an address range, not a specific address. Why?
