31 Jul
2012
31 Jul
'12
8:50 p.m.
On Tuesday 31 July 2012, Russell King - ARM Linux wrote:
I still fail to see how not having highmem enabled would ever cause memory corruption errors (unless something dealing with memory in a very very wrong way - iow, not using one of the reservation or memory allocation methods provided by the kernel.)
The problem is that all users of ux500 systems pass a command line like
vmalloc=256M mem=128M@0 mali.mali_mem=32M@128M hwmem=168M@160M mem=48M@328M mem_issw=1M@383M mem=640M@384M
This is of course totally bogus and should not be done. If I understand Lee correctly, one of the issues resulting from passing a command line like this without enabling highmem is memory corruption.
"Doctor it hurts when I do this ..."
Arnd