invalid ram hack

[wkpark]

Ive seen the following recent changes in the BoardConfig.mk and "recovery" changes in overlay/*

---

BOARD_KERNEL_CMDLINE := mem=447M@0M nvmem=64M@448M loglevel=0 muic_state=1 lpj=9994240 CRC=3010002a8e458d7 vmalloc=256M brdrev=1.0 video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=recovery:35e00:2800:800,linux:34700:1000:800,mbr:400:200:800,system:600:2bc00:800,cache:2c200:8000:800,misc:34200:400:800,userdata:38700:c0000:800 androidboot.hardware=p990

---

but mem=447M@0M nvmem=64M@448M is incorrect.
It is well known issue in the Op2x forum in Korea. (http://cafe.naver.com/op2x )

you have to reserve 1M@383M. this region is reserved for ram_console and some other warmboot stuff.
if you include this 1M@383M region in the mem area then p990/su660 will break with some warmboot stuff/ram_console related functionality.

---

so.. I think.. by the following ramhack you can use both recovery function and ramhack correctly ..

you can use nvmem=64M like as following

1. 64M@ : mem=383M@0M mem=64M@384M nvmem=64M@448M

and other ramhack examples tested on the SU660 are...

1. 101M@ nvmem : mem=383M@0M mem=27M@384M nvmem=101M@411M
2. 120M@ nvmem : mem=383M@0M mem=8M@384M nvmem=120M@392M
   etc...

See also

1. https://github.com/CyanogenMod/lge-kernel-star/blob/android-tegra-2.6.32/drivers/staging/android/ram_console.c#L352
2. https://github.com/CyanogenMod/lge-kernel-star/blob/android-tegra-2.6.32/arch/arm/mach-tegra/board-nvodm.c#L1652

[vork]

Interesting find. Will definitely check it out.