On Thu, Apr 7, 2016 at 11:02 PM, Leo Yan <leo.yan@linaro.org> wrote:

On Thu, Apr 07, 2016 at 10:48:07AM +0530, Amit Kucheria wrote:
> > On Thu, Apr 07, 2016 at 12:24:58PM +0800, Liming Wang wrote:
> >> On Thu, Apr 07, 2016 at 10:32:41AM +0800, Leo Yan wrote:
>
> >> BTW, is there plan to move 4.4 kernel?
> >
> > I think so. I'd like leave this question to John or Amit to answer.
>
> The Reference Platform is already on 4.4 with the 16.03 release. So
> now we just need to make sure it works with u-boot. It was only tested
> with UEFI for 16.03 but u-boot-support is planned for 16.06.

Some updates for uboot booting on Hikey:

- I tried below images, which can boot successfully with uboot:
ARM-TF:
https://github.com/96boards/arm-trusted-firmware.git,
branch: hikey
U-BOOT:
git://git.denx.de/u-boot.git
KERNEL:
https://github.com/96boards-hikey/linux;
branch: hikey-mainline-rebase

I also tried above combination and it can boot well. But it still has some issues:

1. multi cpus still can come online

2. The defconfig has no emmc support and doesn't detect the emmc.

Could you share me with your kernel config against this branch?

BTW: do you know what difference between branch 96b/releases/2016.03 and hikey-mainline-rebase?

I found hikey-mainline-rebase is more stable than 96b/releases/2016.03 when booting with u-boot.

For hikey-mainline-rebase, it can boot to mount initrd. And for 96b/releases/2016.03, it hangs at somewhere.

- If I change to use kernel branch 4.1 for android, then cannot boot:

ARM-TF:
https://github.com/96boards/arm-trusted-firmware.git,
branch: hikey
U-BOOT:
git://git.denx.de/u-boot.git
KERNEL:
https://github.com/96boards-hikey/linux;
branch: android-hikey-linaro-4.1

When jump from uboot to kernel, there have no output. I also checked
has enabled earlycon. So Amit, John, do you have any suggestion for
this?

- I cannot reproduce Liming's panic;

panic only happens on 3.18, just as mentioned in my first mail.

You can try “https://github.com/96boards-hikey/linux tag 96boards-hikey-15.11"

- There have one potential issue for uboot. Uboot will overwrite dtb's
memory node in the function *arch_fixup_fdt()*; so if we want to
reserve memory regions in memory node, it doesn't work after the
overwriting by uboot.

I will look into and try to fix it; If you have any suggestion let
me know.

OK, my current target is to boot 4.4 kernel with u-boot. Thank you for your great help.

BR,

Liming Wang

Thanks,
Leo Yan