Raspberry Pi 3 support

[Ross Alexander]

On Fri Oct 14 22:10:56 UTC 2016, Shawn Webb wrote:

> I've documented the steps I took to install FreeBSD on my RPI3:
>      https://wiki.freebsd.org/arm64
> I hope I didn't miss anything. It's a wiki, so if I did, feel free to
> correct it (or let me know and I can correct it, too).

I'm referencing https://wiki.freebsd.org/arm64/rpi3 as it seems
to be "the one".  The following notes are meant to be clarifications
for people as clueless as myself -

You say: "Download all the files from the boot directory in the
official Raspberry Pi firmware repository on GitHub."  I read that as

     newfs_msdos -F 16 /dev/da0s1
     mount -t msdosfs /dev/da0s1 /mnt0
     cd /mnt0
     svn checkout https://github.com/raspberrypi/firmware/trunk/boot/
     mv boot/* .
     rm -R boot

You say: "Copy $MAKEOBJDIRPREFIX/arm64.aarch64/<svn-checkout-path**>/sys/boot/efi/boot1/boot1.efi
to /mnt/EFI/BOOT/bootaa64.efi".  I read that as

     mount -t ufs /dev/da0s2a /mnt1
     mkdir -p /mnt0/EFI/BOOT
     cp /mnt1/boot/boot1.efi /mnt0/EFI/BOOT/bootaa64.efi

given that /dev/da0s2a is all the stuff from "Building", "World", and
"Kernel" sections and a "make -s installworld installkernel distribution
KERNCONF=RPI3 DESTDIR=/mnt1 TARGET=arm64 TARGET_ARCH=aarch64".

And hey, guess what: it boots fine :).  No hints as to how many times
I got it wrong, though.

regards,
Ross
--
Ross Alexander, (780) 675-6823 desk / (780) 689-0749 cell, rwa at athabascau.ca

    "Plato's scheme of folly, which would have the philosophers take
     over the management of affairs, has been turned on its head; the
     men of affairs have taken over the direction and pursuit of
     knowledge."
                 -- Thorstein Veblen, _The Higher Learning in America_

-- 
    This communication is intended for the use of the recipient to whom it
    is addressed, and may contain confidential, personal, and or privileged
    information. Please contact us immediately if you are not the intended
    recipient of this communication, and do not copy, distribute, or take
    action relying on it. Any communications received in error, or
    subsequent reply, should be deleted or destroyed.
---