![]() | ||||||||||
Messages in this thread |
>>>>> On Fri, 03 Feb 2006, Mark Lord wrote: >>> Hm, I wonder if we could have a more fine-grained choice of the >>> boundary? There are also systems around with e.g. 1.25G or 1.5G of >>> main memory. >> Maybe something like: >> config VMSPLIT_1G >> bool "1G/3G user/kernel split" >> config VMSPLIT_X >> bool "Manual split" >> endchoice > ... > Yes, that looks like a good idea. Couldn't this still be implemented entirely in Kconfig, without modifying page.h? Like in the following example: [...] config VMSPLIT_1G bool "1G/3G user/kernel split" config VMSPLIT_X bool "Manual split" endchoice config PAGE_OFFSET hex range 0x40000000 0xC0000000 prompt "Memory split address (must be aligned to 4096)" if VMSPLIT_X [...] default 0x40000000 if VMSPLIT_1G default 0xC0000000 Cheers Uli - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2006-02-04 10:26 [from the cache] ©2003-2008 | ||||||||||