> Date: Sun, 30 Jun 2019 14:32:40 +0000 > From: Joseph Mayer <joseph.ma...@protonmail.com> > > Hi Mark and Markus, > > On Saturday, 22 June 2019 04:24, Mark Kettenis <mark.kette...@xs4all.nl> > wrote: > > I've finally managed to build a properly working (and fully open > > source) firmware for the ROCKPro64. The firmware consists of two > > files, which can be downloaded from: > > Wait the default one is a proprietary closed-source fork of uboot?
The "ayufan" builds that most people seem to use include binary blobs for the primary bootloader (that initializes DRAM) and ATF. U-Boot itself is open-source but based on a vendor fork of U-Boot. > On Sunday, 30 June 2019 20:13, Markus Hennecke > <markus-henne...@markus-hennecke.de> wrote: > .. > > Thanks, I was unable to boot bsd.rd, but setting up a system on a SD card > > and copying the dtb to the efi partition worked out and gave me a booting > > system. Well, most of the time it is booting. Sometimes the boot ends in > > input/output errors. Is there any smart way to put the system on NVMe > > while u-boot can't boot from it yet without having the root partition on > > SD card? > > > > Just for the record, the following patch for ports sysutils/dtb will not > > change the console speed during the boot process and in addition will > > enable the pcie port: > > Wait enabling PCIe in the firmware has what effect, to enable it at all > (for use post-boot) or to make NVMe bootable? It makes rkpci(4) attach when OpenBSD boots, but anything in the PCIe slot won't be available in the bootloader.
