Searched hist:b27652dd2174df1a7e0a7c5f00d1c8e3ed9287a7 (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/include/linux/ |
| H A D | of_fdt.h | diff b27652dd2174df1a7e0a7c5f00d1c8e3ed9287a7 Tue Dec 24 01:12:08 CST 2013 Kevin Hao <haokexin@gmail.com> powerpc: introduce early_get_first_memblock_info
For a relocatable kernel since it can be loaded at any place, there
is no any relation between the kernel start addr and the memstart_addr.
So we can't calculate the memstart_addr from kernel start addr. And
also we can't wait to do the relocation after we get the real
memstart_addr from device tree because it is so late. So introduce
a new function we can use to get the first memblock address and size
in a very early stage (before machine_init).
Signed-off-by: Kevin Hao <haokexin@gmail.com>
Signed-off-by: Scott Wood <scottwood@freescale.com>
|
| /openbmc/linux/arch/powerpc/kernel/ |
| H A D | prom.c | diff b27652dd2174df1a7e0a7c5f00d1c8e3ed9287a7 Tue Dec 24 01:12:08 CST 2013 Kevin Hao <haokexin@gmail.com> powerpc: introduce early_get_first_memblock_info
For a relocatable kernel since it can be loaded at any place, there
is no any relation between the kernel start addr and the memstart_addr.
So we can't calculate the memstart_addr from kernel start addr. And
also we can't wait to do the relocation after we get the real
memstart_addr from device tree because it is so late. So introduce
a new function we can use to get the first memblock address and size
in a very early stage (before machine_init).
Signed-off-by: Kevin Hao <haokexin@gmail.com>
Signed-off-by: Scott Wood <scottwood@freescale.com>
|