Khasim, As far as I understand there are two options: 1. memmap I had intially tried memmap=xxM$yyM to reserve xxM at yyM This has some issue with 2.6.27 and fixed in later versions(not sure of exact version) and I have not tried it. As Russell has mentioned the new option ARCH_HAS_HOLES_MEMORYMODEL is the part of that fix I believe. The bug was particular to few architecture including ARM(details at http://lkml.org/lkml/2009/5/5/64) With this option its only resevered and you can still mmap that memory. 2. mem As an alternate, I tried spliting the memory to the kernel similar to what you have tried. mem=88M@0x80000000 mem=128M@0x88000000 But if you see how this is parsed by the kernel, you will see that the kernel doesnot create any virtual address space for the hole you have created. In otherwords the kernel is totally unware of that memory. So you cannot mmap that hole. This is my understanding and please correct if I am wrong. -- Regards, Sudeep -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
