[fedora-arm] Docs on using Fedora-Everything-netinst-aarch64-27-20170912.n.0.iso with HiKey960?

On Mon, Sep 18, 2017 at 8:18 PM, Konrad Rzeszutek Wilk

Post by Konrad Rzeszutek Wilk
Hey,
The HiKey960 is one of the supported list of devices per (https://fedoraproject.org/wiki/Architectures/ARM?rd=Architectures/AArch64) where it mentions that the 96Boards.

I don't see Hikey 960 anywhere there as supported. It's not currently
supported. We'll be supporting Hikey620 (original or what ever you
wish to call it) and Dragoonboard 410c in Fedora 27.

The 960 support should hopefully come with Fedora 28 but until I get
hardware (which might be RSN) I have no idea. Upstream kernels look to
be supportable with 4.14 so bootloader depending it should be OK for
F-28

Post by Konrad Rzeszutek Wilk
But I am not finding any docs on how to install?
The Linaro images are rootfs ones that would be loaded using fastboot (after a lot of pain of changing the boot to UEFI) and loading the right Android type images on the box.
_______________________________________________

_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe s

Konrad Rzeszutek Wilk

2017-09-20 15:07:37 UTC

Post by Peter Robinson
I don't see Hikey 960 anywhere there as supported. It's not currently
supported. We'll be supporting Hikey620 (original or what ever you
wish to call it) and Dragoonboard 410c in Fedora 27.

https://fedoraproject.org/wiki/Architecture/ARM/HiKey

is pretty funny on explaining how to do it: "Uses U-Boot to boot EXTLinux to boot GRUB to boot LILO... or something like that."

And https://fedoraproject.org/w/index.php?title=Architecture/ARM/Dragonboard_410

does not even exist.

Post by Peter Robinson
The 960 support should hopefully come with Fedora 28 but until I get
hardware (which might be RSN) I have no idea. Upstream kernels look to
be supportable with 4.14 so bootloader depending it should be OK for
F-28

Are there any bugs created for it? Or for the HiKey or Dragoboard 410c? How do you guys track them?

Post by Konrad Rzeszutek Wilk
But I am not finding any docs on how to install?
The Linaro images are rootfs ones that would be loaded using fastboot (after a lot of

pain of changing the boot to UEFI) and loading the right Android type images on the box.

_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.fe

Peter Robinson

2017-09-20 15:14:04 UTC

On Wed, Sep 20, 2017 at 4:07 PM, Konrad Rzeszutek Wilk

https://fedoraproject.org/wiki/Architecture/ARM/HiKey

There's no mention of the 960 on that page

Post by Konrad Rzeszutek Wilk
is pretty funny on explaining how to do it: "Uses U-Boot to boot EXTLinux to boot GRUB to boot LILO... or something like that."

And version 99, it was a test against the docs template

Post by Konrad Rzeszutek Wilk
And https://fedoraproject.org/w/index.php?title=Architecture/ARM/Dragonboard_410
does not even exist.

Sure, we're still working on the vendor/device templates.

Are there any bugs created for it? Or for the HiKey or Dragoboard 410c? How do you guys track them?

To date mostly in my head because I end up doing most of the work.....

Post by Konrad Rzeszutek Wilk
But I am not finding any docs on how to install?
The Linaro images are rootfs ones that would be loaded using fastboot (after a lot of

pain of changing the boot to UEFI) and loading the right Android type images on the box.

_______________________________________________

_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@list

Konrad Rzeszutek Wilk

2017-09-20 15:27:27 UTC

Post by Peter Robinson
On Wed, Sep 20, 2017 at 4:07 PM, Konrad Rzeszutek Wilk

https://fedoraproject.org/wiki/Architecture/ARM/HiKey

There's no mention of the 960 on that page

Correct. I was more of asking this as I am curious how to translate
the ISO which has an EFI grub and install.img to this weird fastboot
loading mechanism - where you can tweak the partition sizes, etc, via
the fastboot mechanism.

Post by Konrad Rzeszutek Wilk
is pretty funny on explaining how to do it: "Uses U-Boot to boot EXTLinux to boot GRUB to boot LILO... or something like that."

And version 99, it was a test against the docs template

Post by Konrad Rzeszutek Wilk
And https://fedoraproject.org/w/index.php?title=Architecture/ARM/Dragonboard_410
does not even exist.

Sure, we're still working on the vendor/device templates.

Ahhh!

Are there any bugs created for it? Or for the HiKey or Dragoboard 410c? How do you guys track them?

To date mostly in my head because I end up doing most of the work.....

Oh my. If you want somebody to help with the testing, I can try doing
the HiKey 620 tests on the HiKey 960 as well.
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send a

Konrad Rzeszutek Wilk

2017-09-22 12:41:25 UTC

Hi,

I don't have a 960, but I've been running fedora on the older hikey. My
suggestion is to use the prebuilt binaries install process to get a valid
uefi image running on the machine.
http://snapshots.linaro.org/reference-platform/embedded/morty/hikey960/latest/rpb/bootloader/
Really, you should only need to flash the ptable (emmc partition table),
xloader/iloader, and fip.bin (uefi/armtf image). Then from that you _SHOULD_
be able to download one of the fedora server/netboot images boot it and
install fedora like you would on any generic PC with uefi.

OK, so I think you are saying extract:
Fedora-Everything-netinst-aarch64-27-20170912.n.0.iso:
/TRANS.TBL
./Fedora-Legal-README.txt
./boot.catalog
./LICENSE
./EFI
./EFI/BOOT
./EFI/BOOT/BOOTAA64.EFI
./EFI/BOOT/grub.cfg
./EFI/BOOT/TRANS.TBL
./EFI/BOOT/mmaa64.efi
./EFI/BOOT/fonts
./EFI/BOOT/fonts/TRANS.TBL
./EFI/BOOT/fonts/unicode.pf2
./EFI/BOOT/grubaa64.efi
./images
./images/TRANS.TBL
./images/efiboot.img
./images/pxeboot
./images/pxeboot/TRANS.TBL
./images/pxeboot/initrd.img
./images/pxeboot/vmlinuz
./images/install.img

from https://fedoraproject.org/wiki/Test_Results:Fedora_27_Branched_20170912.n.0_Installation?rd=Test_Results:Current_Installation_Test

, then create an DOS partition image, put in the contents of that whole
thing in there (456M), modify the grub.cfg to use the serial console
(and VNC?), and then kick it off.

.. But that seems a bit silly - why not just have pre-created images
(boot and system.img) that could be loaded directly and have a basic
install?

The remainder of the images (boot/system/etc) would just be overwritten by
the fedora install anyway.
Will it work? No idea! The aarch64 fedora installers use basically upstream
grub/kernel/etc trees so linaro "workarounds" for machine/firmware problems
may not be in fedora. I intend to encourage more "standards" compliance with
regard to the UEFI images linaro ships when i'm at connect next week.
Sorry, not be be more helpful.

Post by Konrad Rzeszutek Wilk
The Linaro images are rootfs ones that would be loaded using fastboot (after a lot of pain of changing the boot to UEFI) and loading the right Android type images on the box.
_______________________________________________

_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email t

Peter Robinson

2017-09-22 15:02:47 UTC