Hi Matthias and Oleg, Am 15.05.2017 um 11:38 schrieb Matthias Brugger:
On 14/05/17 13:22, Oleg wrote:
I'm trying to run openSUSE on Khadas VIM.
Which settings\variables u-boot you need to install to transfer
control after the start of u-boot to openSUSE ?
An empty Wiki page usually hints that either time for investigations or essential software pieces are missing: https://en.opensuse.org/HCL:Khadas_Vim
As far as I know, there are no working images for the Khadas VIM.
Does mainline u-boot support your device?
Unfortunately not. I barely just sent a patch for a second S905 device, no signs of S905X or S912 yet. The biggest question I am unclear about (and which needs testing/review) is whether new pinctrl drivers will be needed, or whether we might just ignore those drivers initially for at least serial. The second issue is that my amlbootsig tool does not support S905X yet, so we couldn't build images in OBS, even if there were a U-Boot package. Both S905X and S912 seem to use aml_encrypt_gxl (haven't seen any _gxm), whereas the current state is based on aml_encrypt_gxb, and there was at least an initial @AML header not present on S905X. Even for S905 there's input differences between Hardkernel and FriendlyARM. amlbootsig does not block local testing with aml_encrypt_gxl of course. Oleg, you can download a JeOS-rootfs tarball from http://download.opensuse.org/ports/aarch64/tumbleweed/images/ but it doesn't contain an initrd for its kernel; other images such as JeOS-efi or JeOS-odroidc2 do contain both. If you use your own e.g. linux-next kernel with built-in drivers you can circumvent the initrd. 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