<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">Thanks for your responses; they do answer my question.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">Chris</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 4, 2018 at 5:30 PM, Gordan Bobic <span dir="ltr"><<a href="mailto:gordan@redsleeve.org" target="_blank">gordan@redsleeve.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Things required to "support" Pi3 aarch64 that aren't already in place in core CentOS (or at least I haven't managed to find them):<div><br></div><div>1) Pi3 firmware blobs</div><div>Trivially downloadable from</div><div><a href="https://github.com/raspberrypi/firmware/tree/master/boot" target="_blank">https://github.com/<wbr>raspberrypi/firmware/tree/<wbr>master/boot</a><br></div><div><br></div><div>2) UEFI bootloader</div><div>There are two options, u-boot and Tianocore.</div><div>My current Pi3 aarch64 image works with u-boot that I grabbed from the Fedora 26 image. </div><div>I'm currently trying to get it working with Tianocore from here:</div><div><a href="https://github.com/andreiw/RaspberryPiPkg" target="_blank">https://github.com/andreiw/<wbr>RaspberryPiPkg</a><br></div><div>I _almost_ have it working (gets as far as booting grub, but grub then doesn't manage to boot up the kernel, almost certainly a dtb issue somewhere).</div><div><br></div><div>3) Kernel</div><div>I keep my own mainline kernel build for aarch64, loosely based on, IIRC, 4.5.x that shipped with CentOS aarch64, but with some modifications. I have a build that works on both my X-Gene and the Pi3. You can find it here:</div><div><a href="http://ftp.redsleeve.org/pub/misc/kernel/aarch64/RPMS/" target="_blank">http://ftp.redsleeve.org/pub/<wbr>misc/kernel/aarch64/RPMS/</a><br></div><div>(Note: I only included Pi 3 SoC configuration as of 4.9.73).</div><div><br></div><div>So it's not exactly an insurmountable problem, it's just a case off dropping a tarball of 5-6 files onto the /boot/efi FAT partition, having the appropriate kernel installed in the image, and it should "just work".</div><div>I can have a working image with u-boot EFI as soon as I find half an hour to spare.</div><div>The one with Tianocore EFI will take a little longer.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 4, 2018 at 9:55 PM, Fabian Arrotin <span dir="ltr"><<a href="mailto:arrfab@centos.org" target="_blank">arrfab@centos.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 04/01/18 19:26, Christopher Ursich wrote:<br>
> Hi, all. First-timer here.<br>
><br>
> I am setting up a new Raspberry Pi 3. When I review the AltArch pages,<br>
> I see that most of the RPi3 coverage is categorized under Arm32, including<br>
><br>
> <a href="https://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32/RaspberryPi3" rel="noreferrer" target="_blank">https://wiki.centos.org/Spec<wbr>ialInterestGroup/AltArch/Arm32<wbr>/RaspberryPi3</a><br>
<br>
Because we targeted armhfp even for the Pi3 initially, as even the Pi<br>
Foundation had no plan to provide/build at the beginning aarch64<br>
kernel/code for the pi3<br>
TBH (my own opinion) it doesn't even really make sense to use aarch64<br>
code on the pi3 itself with such low specs .. only benefit is probably<br>
that epel exists for aarch64 vs armhfp and also same tree if you want to<br>
deploy to "real" aarch64 nodes in Datacenter ...<br>
<br>
Now, I'll let Jim (the aarch64 maintainer) explain his plans for aarch64<br>
tree for pi3, but at this stage of meltdown and spectre, I guess we all<br>
have other urgent things to do too :-)<span class="HOEnZb"><font color="#888888"><br>
<span class="m_-1735761503624291250HOEnZb"><font color="#888888"><br>
--<br>
Fabian Arrotin<br>
The CentOS Project | <a href="https://www.centos.org" rel="noreferrer" target="_blank">https://www.centos.org</a><br>
gpg key: 56BEC54E | twitter: @arrfab<br>
<br>
</font></span><br>______________________________<wbr>_________________<br>
Arm-dev mailing list<br>
<a href="mailto:Arm-dev@centos.org" target="_blank">Arm-dev@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/arm-dev" rel="noreferrer" target="_blank">https://lists.centos.org/mailm<wbr>an/listinfo/arm-dev</a><br>
<br></font></span></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
Arm-dev mailing list<br>
<a href="mailto:Arm-dev@centos.org">Arm-dev@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/arm-dev" rel="noreferrer" target="_blank">https://lists.centos.org/<wbr>mailman/listinfo/arm-dev</a><br>
<br></blockquote></div><br></div>