Hi Simon,
On 2016-1-12 0:58, Simon Glass wrote:
Hi Jeffy,
On 8 January 2016 at 03:51, Jeffy Chen jeffy.chen@rock-chips.com wrote:
Hi Simon,
On 2016-1-8 11:34, Simon Glass wrote:
Hi Jeffy,
On 4 January 2016 at 00:50, Jeffy Chen jeffy.chen@rock-chips.com wrote:
The android kernel is using appended dtb by default, and store ramdisk right after kernel & dtb. So we needs to relocate ramdisk, and use atags to pass params.
Signed-off-by: Jeffy Chen jeffy.chen@rock-chips.com
include/configs/kylin_rk3036.h | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+)
Acked-by: Simon Glass sjg@chromium.org
What kernel version are you using?
It's kernel v4.1 for android project: git fetch https://android.googlesource.com/platform/hardware/bsp/kernel/common/v4.1 refs/changes/03/188603/5 && git checkout FETCH_HEAD :)
OK - just wondered why it needs ATAGs (CONFIG_SETUP_MEMORY_TAGS) - are there things that device tree does not support?
I saw our guys used to detect ddr params in the loader, and pass memory areas and reserved areas to kernel... and kernel's device tree would only define a common memory node in the dtsi, which is not match the actually memory.
used to
Regards, Simon
On 2016-1-8 11:34, Simon Glass wrote:
Hi Jeffy,
On 4 January 2016 at 00:50, Jeffy Chen jeffy.chen@rock-chips.com wrote:
The android kernel is using appended dtb by default, and store ramdisk right after kernel & dtb. So we needs to relocate ramdisk, and use atags to pass params.
Signed-off-by: Jeffy Chen jeffy.chen@rock-chips.com
include/configs/kylin_rk3036.h | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+)
Acked-by: Simon Glass sjg@chromium.org
What kernel version are you using?
Regards, Simon
Regards, Simon