I just build vanilla v4.4 with arm64 defconfig and it doesn't boot on hikey. What patch set and config do I need?
I need a minimal set of patches to add to an existing project.
-Geoff
Hi, Geoff
You can find the patches you need here: https://github.com/96boards/linux/commits/hikey-mainline-rebase
If you can check it in 'git log', you can easily track down to these basic topic branches. Each of them is on pure v4.4. And for a minimum system, you need: working-hikey-tracking-dts-v4.4 working-hikey-tracking-config-v4.4 (, from it, pick those relate to you). working-hikey-tracking-pmic-v4.4 (could be optional too. since by default bootloader already enables regulators for you)
BTW, I bet you know where to download UEFI for hikey.
== FYI,: $ git log --oneline github-kernel/hikey-mainline-rebase 9fa9359 Merge branch 'working-hikey-tracking-config-v4.4' into working-hikey-mainline-rebase-v4.4-c0 6da55d0 Merge branch 'working-hikey-tracking-pm-v4.4' into working-hikey-mainline-rebase-v4.4-c0 e22dea1 Merge branch 'working-hikey-tracking-drm-v4.4' into working-hikey-mainline-rebase-v4.4-c0 48de7d4 Merge branch 'working-hikey-tracking-adv7511-v4.4' into working-hikey-mainline-rebase-v4.4-c0 60c3756 Merge branch 'working-hikey-tracking-usb-v4.4' into working-hikey-mainline-rebase-v4.4-c0 78b4edb Merge branch 'working-hikey-tracking-wifi-v4.4' into working-hikey-mainline-rebase-v4.4-c0 bced7d6 Merge branch 'working-hikey-tracking-mmc-v4.4' into working-hikey-mainline-rebase-v4.4-c0 ee8c6fe Merge branch 'working-hikey-tracking-pmic-v4.4' into working-hikey-mainline-rebase-v4.4-c0 b13d5dd Merge branch 'working-hikey-tracking-dts-v4.4' into working-hikey-mainline-rebase-v4.4-c0
-Guodong
On 16 January 2016 at 04:27, Geoff Levand geoff@infradead.org wrote:
I just build vanilla v4.4 with arm64 defconfig and it doesn't boot on hikey. What patch set and config do I need?
I need a minimal set of patches to add to an existing project.
-Geoff
Dev mailing list Dev@lists.96boards.org https://lists.96boards.org/mailman/listinfo/dev
On Sat, Jan 16, 2016 at 12:25 PM, Guodong Xu guodong.xu@linaro.org wrote:
Hi, Geoff
You can find the patches you need here: https://github.com/96boards/linux/commits/hikey-mainline-rebase
If you can check it in 'git log', you can easily track down to these basic topic branches. Each of them is on pure v4.4. And for a minimum system, you need: working-hikey-tracking-dts-v4.4 working-hikey-tracking-config-v4.4 (, from it, pick those relate to you). working-hikey-tracking-pmic-v4.4 (could be optional too. since by default bootloader already enables regulators for you)
Hi Guodong,
Have the necessary DTS entries been merged for 4.5?
We should really get Hikey working with ARM64 defconfig in "mainline" - that is, no additional patches should be required.
Regards, Amit
On Mon, Jan 18, 2016 at 7:01 AM, Amit Kucheria amit.kucheria@linaro.org wrote:
On Sat, Jan 16, 2016 at 12:25 PM, Guodong Xu guodong.xu@linaro.org wrote:
Hi, Geoff
You can find the patches you need here: https://github.com/96boards/linux/commits/hikey-mainline-rebase
If you can check it in 'git log', you can easily track down to these
basic
topic branches. Each of them is on pure v4.4. And for a minimum system,
you
need: working-hikey-tracking-dts-v4.4 working-hikey-tracking-config-v4.4 (, from it, pick those relate to you). working-hikey-tracking-pmic-v4.4 (could be optional too. since by default bootloader already enables regulators for you)
Hi Guodong,
Have the necessary DTS entries been merged for 4.5?
We should really get Hikey working with ARM64 defconfig in "mainline"
- that is, no additional patches should be required.
I don't know what specific issue the OP is experiencing, but FWIW I _can_ boot vanilla 4.4 on my board with the default config:
root@HiKey:/ uname -a Linux HiKey 4.4.0 #142 SMP PREEMPT Mon Jan 18 09:07:06 CET 2016 aarch64 GNU/Linux root@HiKey:/ gunzip -c /proc/config.gz | md5sum dc59a664c9e9f4fb9078cf9ccf127271 -
$ make -C linux ARCH=arm64 defconfig $ md5sum linux/.config dc59a664c9e9f4fb9078cf9ccf127271 linux/.config
Regards,
On Sat, 2016-01-16 at 14:55 +0800, Guodong Xu wrote:
Hi, Geoff
You can find the patches you need here: https://github.com/96boards/linux/commits/hikey-mainline-rebase
If you can check it in 'git log', you can easily track down to these basic topic branches. Each of them is on pure v4.4. And for a minimum system, you need: working-hikey-tracking-dts-v4.4 working-hikey-tracking-config-v4.4 (, from it, pick those relate to you). working-hikey-tracking-pmic-v4.4 (could be optional too. since by default bootloader already enables regulators for you)
This is a big PITA. I'm tired of f---ing with this for every kernel release. I have DROPPED hikey support from CoreOS.
-Geoff
Hi Geoff,
I realize you had been removed from the recipient list when I replied the below, so I'm not sure you got my message. What do you mean by "it doesn't boot"? I certainly would like to understand why it works for me and not for you.
On Mon, Jan 18, 2016 at 6:10 AM, Jerome Forissier jerome.forissier@linaro.org wrote:
On Mon, Jan 18, 2016 at 7:01 AM, Amit Kucheria amit.kucheria@linaro.org wrote:
On Sat, Jan 16, 2016 at 12:25 PM, Guodong Xu guodong.xu@linaro.org wrote:
Hi, Geoff
You can find the patches you need here: https://github.com/96boards/linux/commits/hikey-mainline-rebase
If you can check it in 'git log', you can easily track down to these basic topic branches. Each of them is on pure v4.4. And for a minimum system, you need: working-hikey-tracking-dts-v4.4 working-hikey-tracking-config-v4.4 (, from it, pick those relate to you). working-hikey-tracking-pmic-v4.4 (could be optional too. since by default bootloader already enables regulators for you)
Hi Guodong,
Have the necessary DTS entries been merged for 4.5?
We should really get Hikey working with ARM64 defconfig in "mainline"
- that is, no additional patches should be required.
I don't know what specific issue the OP is experiencing, but FWIW I _can_ boot vanilla 4.4 on my board with the default config:
root@HiKey:/ uname -a Linux HiKey 4.4.0 #142 SMP PREEMPT Mon Jan 18 09:07:06 CET 2016 aarch64 GNU/Linux root@HiKey:/ gunzip -c /proc/config.gz | md5sum dc59a664c9e9f4fb9078cf9ccf127271 -
$ make -C linux ARCH=arm64 defconfig $ md5sum linux/.config dc59a664c9e9f4fb9078cf9ccf127271 linux/.config
From kernelci.org it seems that it was booting fine with 4.4:
http://kernelci.org/boot/hi6220-hikey/job/mainline/kernel/v4.4-10019-g963868...
Boot log http://storage.kernelci.org/mainline/v4.4-10019-g9638685e32af/arm64-defconfi...
Or is there any feature in particular that you want to use which is not yet supported?
Thanks,
On Thu, Jan 21, 2016 at 10:47 AM, Ricardo Salveti ricardo.salveti@linaro.org wrote:
On Mon, Jan 18, 2016 at 6:10 AM, Jerome Forissier jerome.forissier@linaro.org wrote:
On Mon, Jan 18, 2016 at 7:01 AM, Amit Kucheria amit.kucheria@linaro.org wrote:
On Sat, Jan 16, 2016 at 12:25 PM, Guodong Xu guodong.xu@linaro.org wrote:
Hi, Geoff
You can find the patches you need here: https://github.com/96boards/linux/commits/hikey-mainline-rebase
If you can check it in 'git log', you can easily track down to these basic topic branches. Each of them is on pure v4.4. And for a minimum system, you need: working-hikey-tracking-dts-v4.4 working-hikey-tracking-config-v4.4 (, from it, pick those relate to you). working-hikey-tracking-pmic-v4.4 (could be optional too. since by default bootloader already enables regulators for you)
Hi Guodong,
Have the necessary DTS entries been merged for 4.5?
We should really get Hikey working with ARM64 defconfig in "mainline"
- that is, no additional patches should be required.
I don't know what specific issue the OP is experiencing, but FWIW I _can_ boot vanilla 4.4 on my board with the default config:
root@HiKey:/ uname -a Linux HiKey 4.4.0 #142 SMP PREEMPT Mon Jan 18 09:07:06 CET 2016 aarch64 GNU/Linux root@HiKey:/ gunzip -c /proc/config.gz | md5sum dc59a664c9e9f4fb9078cf9ccf127271 -
$ make -C linux ARCH=arm64 defconfig $ md5sum linux/.config dc59a664c9e9f4fb9078cf9ccf127271 linux/.config
From kernelci.org it seems that it was booting fine with 4.4: http://kernelci.org/boot/hi6220-hikey/job/mainline/kernel/v4.4-10019-g963868...
Sorry, this is actually the current development tree.
For the 4.4 release: http://kernelci.org/boot/hi6220-hikey/job/mainline/kernel/v4.4/defconfig/def...
And for all the mainline kernel builds for hikey: http://kernelci.org/boot/hi6220-hikey/job/mainline/
Cheers,
Hi,
On Thu, 2016-01-21 at 09:55 +0100, Jerome Forissier wrote:
$ md5sum linux/.config dc59a664c9e9f4fb9078cf9ccf127271 linux/.config
I get the same md5sum.
Here is what I see:
EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... dmi: Firmware registration failed.
I put my Image and dtb here:
https://www.kernel.org/pub/linux/kernel/people/geoff/coreos/
-Geoff
On 22 January 2016 at 03:31, Geoff Levand geoff@infradead.org wrote:
Hi,
On Thu, 2016-01-21 at 09:55 +0100, Jerome Forissier wrote:
$ md5sum linux/.config dc59a664c9e9f4fb9078cf9ccf127271 linux/.config
I get the same md5sum.
The same to me too. This is from vanilla v4.4 arch/arm64/defconfig, by running: make distclean; make ARCH=arm64 defconfig;
Here is what I see:
EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... dmi: Firmware registration failed.
I put my Image and dtb here:
https://www..org/pub/linux/kernel/people/geoff/coreos/ https://www.kernel.org/pub/linux/kernel/people/geoff/coreos/
I downloaded your Image.gz and hi6220-hikey.dtb (from the above location). It boots __well__ on HiKey. Log is post here: https://pastebin.linaro.org/view/bf165a36 (Note: I hacked boot-fat.uefi.img http://boot.imghttps://builds.96boards.org/snapshots/hikey/community/hikey-mainline-rebase/16/boot-fat.uefi.img.gz to place your images in, and added a boot item for them in grub.cfg (@ /EFI/BOOT/).
So, now, let's take one step back: which version of ATF/UEFI are you using on HiKey? as of now, we recommends official released UEFI, downloadable here: https://builds.96boards.org/releases/hikey/linaro/binaries/15.11/ (please use ptable-linux-4g.img https://builds.96boards.org/releases/hikey/linaro/binaries/15.11/ptable-linux-4g.img if your board comes with 4GB eMMC).
PS: Documentations of HiKey 15.11 release are here: https://github.com/96boards/documentation/wiki/HiKeyGettingStarted
-Guodong
-Geoff
On 21/01/16 19:31, Geoff Levand wrote:
Hi,
On Thu, 2016-01-21 at 09:55 +0100, Jerome Forissier wrote:
$ md5sum linux/.config dc59a664c9e9f4fb9078cf9ccf127271 linux/.config
I get the same md5sum.
Here is what I see:
EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... dmi: Firmware registration failed.
There's been a lot of confusion on this board about which serial port logs for different components emerge from.
This was caused by a migration from using the (unpopulated) 4 pin UART header to LS-UART1 on the low speed mezzanine connector. Over time the firmware, bootloader, vendor kernel and upstream kernel have all switched their defaults to LS-UART1.
In fact I believe v4.4 is the first upstream release to support, and have DTS defaults pointed at, LS-UART1 (ttyAMA3). Would this have affected you?
Daniel.
On Fri, 2016-01-22 at 10:12 +0800, Guodong Xu wrote: So, now, let's take one step back: which version of ATF/UEFI are you
using on HiKey? as of now, we recommends official released UEFI, downloadable here: https://builds.96boards.org/releases/hikey/linaro/binaries/15.11/ (please use ptable-linux-4g.img if your board comes with 4GB eMMC).
uefi_path="${builds_root}/builds.96boards.org/releases/hikey/linaro/binaries/15.11" debian_path="${builds_root}/builds.96boards.org/releases/hikey/linaro/debian/15.11"
boot_image="${debian_path}/boot-fat.uefi.img"
sudo fastboot flash ptable "${uefi_path}/ptable-linux-4g.img" sudo fastboot flash fastboot "${uefi_path}/fip.bin" sudo fastboot flash nvme "${uefi_path}/nvme.img" sudo fastboot flash boot ${boot_image}
On 23 January 2016 at 01:48, Geoff Levand geoff@infradead.org wrote:
On Fri, 2016-01-22 at 10:12 +0800, Guodong Xu wrote: So, now, let's take one step back: which version of ATF/UEFI are you
using on HiKey? as of now, we recommends official released UEFI,
downloadable here: https://builds.96boards.org/releases/hikey/linaro/binaries/15.11/
(please use ptable-linux-4g.img if your board comes with 4GB eMMC).
uefi_path="${builds_root}/ builds.96boards.org/releases/hikey/linaro/binaries/15.11" debian_path="${builds_root}/ builds.96boards.org/releases/hikey/linaro/debian/15.11"
boot_image="${debian_path}/boot-fat.uefi.img"
sudo fastboot flash ptable "${uefi_path}/ptable-linux-4g.img" sudo fastboot flash fastboot "${uefi_path}/fip.bin" sudo fastboot flash nvme "${uefi_path}/nvme.img" sudo fastboot flash boot ${boot_image}
For 15.11 release (with v3.18 kernel), these steps are correct. I confirm.
But Geoff, I am not clear what's the purpose you post these. It looks off the topic to me.
Can you now boot your v4.4 vanilla image on HiKey or you want clarity other things?
-Guodong
Hi Geoff, Guodong,
On Sat, Jan 23, 2016 at 08:15:42AM +0800, Guodong Xu wrote:
On 23 January 2016 at 01:48, Geoff Levand geoff@infradead.org wrote:
On Fri, 2016-01-22 at 10:12 +0800, Guodong Xu wrote: So, now, let's take one step back: which version of ATF/UEFI are you
using on HiKey? as of now, we recommends official released UEFI,
downloadable here: https://builds.96boards.org/releases/hikey/linaro/binaries/15.11/
(please use ptable-linux-4g.img if your board comes with 4GB eMMC).
uefi_path="${builds_root}/ builds.96boards.org/releases/hikey/linaro/binaries/15.11" debian_path="${builds_root}/ builds.96boards.org/releases/hikey/linaro/debian/15.11"
boot_image="${debian_path}/boot-fat.uefi.img"
sudo fastboot flash ptable "${uefi_path}/ptable-linux-4g.img" sudo fastboot flash fastboot "${uefi_path}/fip.bin" sudo fastboot flash nvme "${uefi_path}/nvme.img" sudo fastboot flash boot ${boot_image}
For 15.11 release (with v3.18 kernel), these steps are correct. I confirm.
But Geoff, I am not clear what's the purpose you post these. It looks off the topic to me.
Can you now boot your v4.4 vanilla image on HiKey or you want clarity other things?
Remind one thing which just several days before I encountered. Now Hikey has moved Image and dtb files into rootfs but not in boot_image anymore. So if only burn boot_image, then definitely cannot boot up successfully.
If you want to boot your own images, you can manually add grub boot entry like below [1]:
menuentry 'Custom Kernel' { search.fs_label rootfs root search.fs_label boot esp linux ($esp)/Image console=tty0 console=ttyAMA3,115200 root=/dev/disk/by-partlabel/system rootwait rw efi=noruntime initrd ($esp)/initrd.img devicetree ($esp)/hi6220-hikey.dtb }
Not sure if this is your case, hope this info will be helpful.
[1] https://github.com/96boards/documentation/wiki/HiKeyUEFI
Thanks, Leo Yan
-
Amit Kucheria -
Daniel Thompson -
Geoff Levand -
Guodong Xu -
Jerome Forissier -
Leo Yan -
Ricardo Salveti