Work of samueldr to run NixOS on the Pine64 Pinebook Pro
Go to file
Samuel Dionne-Riel b5e85308ee Prefer tty0 console 2020-01-06 20:28:54 -05:00
kernel Add kernel build 2020-01-06 15:21:57 -05:00
nixos Prefer tty0 console 2020-01-06 20:28:54 -05:00
u-boot u-boot: Add patch for chonky kernels 2020-01-06 15:03:26 -05:00
.gitignore initial commit 2019-11-14 17:40:51 -05:00
README.md Add note about modules and stage-1 2020-01-06 20:28:37 -05:00
build.sh Adds (incomplete) system image build 2020-01-06 15:22:39 -05:00
configuration.nix Add modules for stage-1 display init 2020-01-06 19:50:35 -05:00
cross-hacks.nix Adds (incomplete) system image build 2020-01-06 15:22:39 -05:00
default.nix Set this up using a proper overlay 2020-01-06 15:21:02 -05:00
overlay.nix Normalize names 2020-01-06 16:03:48 -05:00
system.nix Adds (incomplete) system image build 2020-01-06 15:22:39 -05:00
with-cross.nix Adds (incomplete) system image build 2020-01-06 15:22:39 -05:00

README.md

WIP stuff to get started on the pinebook pro.

u-boot

Assuming /dev/mmcblk0 is an SD card.

$ nix-build -A pkgs.uBootPinebookPro
$ lsblk /dev/mmcblk0 && sudo dd if=result/idbloader.img of=/dev/mmcblk0 bs=512 seek=64 oflag=direct,sync && sudo dd if=result/u-boot.itb of=/dev/mmcblk0 bs=512 seek=16384 oflag=direct,sync

The eMMC has to be zeroed (in the relevant sectors) or else the RK3399 will use the eMMC as a boot device first.

Alternatively, this u-boot can be installed to the eMMC.

Installing to SPI has yet to be investigated.

Image build

$ ./build.sh
$ lsblk /dev/mmcblk0 && sudo dd if=$(echo result/sd-image/*.img) of=/dev/mmcblk0 bs=8M oflag=direct status=progress

The build.sh script transmits parameters to nix-build, so e.g. -j0 can be used.

Once built, this image is self-sufficient, meaning that it should already be booting, no need burn u-boot to it.

The required modules (and maybe a bit more) are present in stage-1 so the display should start early enough in the boot process.

Note about cross-compilation

This will automatically detect the need for cross-compiling or not.

When cross-compiled, all caveats apply. Here this mainly means that the kernel will need to be re-compiled on the device on the first nixos-rebuild switch, while most other packages can be fetched from the cache.