Re: Docs on using Fedora-Everything-netinst-aarch64-27-20170912.n.0.iso with HiKey960?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 09/20/2017 10:27 AM, Konrad Rzeszutek Wilk wrote:
On Wed, Sep 20, 2017 at 04:14:04PM +0100, Peter Robinson wrote:
On Wed, Sep 20, 2017 at 4:07 PM, Konrad Rzeszutek Wilk
<konrad@xxxxxxxxxx> wrote:
On Mon, Sep 18, 2017 at 8:18 PM, Konrad Rzeszutek Wilk
<konrad(a)kernel.org&gt; wrote:

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

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.

I guess my mailer is running behind a bit I now see the rest of this thread. Anyway, the ptable images are the emmc partition tables, they can (generally) be mounted in loopback mode and edited with your favorite partitioning utility. Removing the EFI system partition and root/boot and letting fedora create its own during the install process should work if the firmware is mostly functional. I've had problems with the original hikey images having duplicate GUID's on differing partitions (which is another reason for removing all but the firmware related partitions).

But fastboot is as you say "weird" hence my earlier comment about trying to run the fedora installer, which will let you modify the partition table of the install destination. The gocha with these combined firmware/flash/EFI system partition/boot/root/etc images is that they are susceptible to accidentally erasing/modifying a critical partition that yields a machine that needs to be re-flashed.



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

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!

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?

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 -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux ARM (Vger)]     [Linux ARM]     [ARM Kernel]     [Fedora User Discussion]     [Older Fedora Users Discussion]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

Powered by Linux