summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorAnton Vorontsov2012-05-12 02:17:54 +0200
committerGreg Kroah-Hartman2012-05-14 17:56:05 +0200
commit24c3d2f342edbc10fee9f8ab9e0a033393686543 (patch)
tree793b36b3249ef7d352b938163aa74d43025410e5 /scripts
parentstaging: android: persistent_ram: Introduce persistent_ram_vmap() (diff)
downloadkernel-qcow2-linux-24c3d2f342edbc10fee9f8ab9e0a033393686543.tar.gz
kernel-qcow2-linux-24c3d2f342edbc10fee9f8ab9e0a033393686543.tar.xz
kernel-qcow2-linux-24c3d2f342edbc10fee9f8ab9e0a033393686543.zip
staging: android: persistent_ram: Make it possible to use memory outside of bootmem
This includes devices' memory (e.g. framebuffers or memory mapped EEPROMs on a local bus), as well as the normal RAM that we don't use for the main memory. For the normal (but unused) ram we could use kmaps, but this assumes highmem support, so we don't bother and just use the memory via ioremap. As a side effect, the following hack is possible: when used together with pstore_ram (new ramoops) module, we can limit the normal RAM region with mem= and then point ramoops to use the rest of the memory, e.g. mem=128M ramoops.mem_address=0x8000000 Sure, we could just reserve the region with memblock_reserve() early in the arch/ code, and then register a pstore_ram platform device pointing to the reserved region. It's still a viable option if platform wants to do so. Also, we might want to use IO accessors in case of a real device, but for now we don't bother (the old ramoops wasn't using it either, so at least we don't make things worse). Signed-off-by: Anton Vorontsov <anton.vorontsov@linaro.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions