> Month ago I've been able successfully boot my pine64 on top of almost > regular fedora resources: > https://kloczek.wordpress.com/2017/04/04/work-in-progress-fedora-rawhide-on-pine64/ > > All what is really needed to add ATF patches to u-boot. > As I've been a bit busy in last month I was not able to finish my > uboot-tools.spec aftr it was updated to 2017.05 to propose necessary > changes (will try to do this in next two weeks). We now have a u-boot with the Pine64 ATF stuff as of build uboot-tools-2017.05-0.6.rc2.fc27 > Only other issue which I found are: > 1) u-boot cannot boot out of regular vmlinuz and before reboot is > necessary unpack it to uImage file and change entry in > /boot/extlinux/extlinux.conf. If someone can provide some other way > how to boot from vmlinuz I would be happy to see it We're using u-boot and bootefi. There's a few things I need to cleanup to make it more consumable for end users. > 2) during boot is reported OOPS and I've reported it in > https://bugzilla.redhat.com/show_bug.cgi?id=1440419 You need to add ARMTracker as blocker for arm bugs so we find out about them > 3) rtl8192cu eth driver seems has no possibility to pass in params MAC > address and after each reboot and as long as someone will be using > DHCP with dynamic IP assignment after each reboot pine will be with > new IP. Yes, that needs upstream eFUSE support and likely u-boot patches, this is not a Fedora issue and will need to be fixed upstream. I've not yet seen patches for that. > Nevertheless in last +week I was not able regularly update my pine64 > and when I've done update yesterday I found that kernel > 4.11.0-0.rc8.git4.1.fc27 and 4.11.0-1.fc27 no longer boots and last > kernel which I have which is booting is 4.11.0-0.rc6.git3.1.fc27. > Something introduced after 4.11.0-0.rc6.git3.1.fc27 now is causing > that Fedora kernel no longer boots on pine64. Simple after loading > kernel there is no even single line of kernel messages. It's actually a gcc regression, there's a new gcc build building so it should be fixed soon. _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
