[opensuse-arm] About the image for DragonBoard 410C
Hi I bought DragonBoard 410C. And I have been looking for the installation image for this board. I could find the HCL list on the below URL. https://en.opensuse.org/HCL:DragonBoard410c But I can¹t find the image. So could you tell me the link and how to install it on this? Best Regards. Ryo -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Ryo-san, Am 15.01.2016 um 03:08 schrieb Murakawa Ryo:
I bought DragonBoard 410C. And I have been looking for the installation image for this board. I could find the HCL list on the below URL. https://en.opensuse.org/HCL:DragonBoard410c
But I can¹t find the image. So could you tell me the link and how to install it on this?
There is no openSUSE image for the DragonBoard 410c, that's why it says "Manual installation" on that Wiki page. ;) Apart from the kernel upstreaming by Qualcomm/Linaro taking some time, Qualcomm uses a very complicated partitioning scheme that Kiwi does not know about yet. Someone needs to figure out what exactly the GPT needs to look like and then how to implement that in Kiwi. https://github.com/openSUSE/kiwi/ Further, an SD card image would require to recompile Android LK with different settings, which Linaro hadn't documented yet when I inquired. Linaro's Nicolas Duchesne is the person to bug about that if you don't yet find info on this. Someone (you?) needs to package LK in OBS, then we can more easily add any necessary patches on top. Also, various other firmware blobs for the various partitions need to be packaged in a dragonboard410c-firmware package or so. I do have openSUSE running on a DragonBoard 410c, using a kernel flashed via fastboot and a JeOS rootfs on SD card, but the Linaro integration kernel has been unstable for me, with the kernel getting stuck in unbalanced locking, resulting in occasional filesystem damage. It's some two months old, so maybe this has been fixed in mainline already by now... Their use of LK means that up until recently you could merely load an Android-style kernel image. Only recently were patches submitted for U-Boot (to be chain-loaded from LK), and I don't think they are in our 2016.01 u-boot package yet, nor have I found time to test them yet. They should make it easier to use our updated Tumbleweed, Kernel:HEAD or Kernel:linux-next kernels, but it still won't solve the other issues surrounding image creation outlined above. So for now the steps still roughly are: 1) Compile an upstream or Linaro kernel, e.g. via cross-aarch64-gcc5. 2) Create an empty initrd via cpio and gzip. 3) Create an Android boot image from kernel, initrd, fdt and cmdline. 4) Download and extract to an SD card partition the JeOS rootfs tarball. 5) Boot the board into fastboot mode by pressing Vol- on power-on. 6) Boot or flash your kernel image via fastboot. Best regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (2)
-
Andreas Färber
-
Murakawa Ryo