summaryrefslogtreecommitdiffhomepage
path: root/blog/entry/pinebookpro.mdwn
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2021-05-14 17:25:11 -0700
committerSean Whitton <spwhitton@spwhitton.name>2021-05-14 17:25:11 -0700
commitc75c8000a0ae992cbf831edd08e59e81a2198dc4 (patch)
treeee7fcc7978d01b17476b94dacfd4633b5effa6ec /blog/entry/pinebookpro.mdwn
parent52a5b15c0e2258b0cab48841baabb502163b0013 (diff)
downloadwiki-c75c8000a0ae992cbf831edd08e59e81a2198dc4.tar.gz
fix link
Diffstat (limited to 'blog/entry/pinebookpro.mdwn')
-rw-r--r--blog/entry/pinebookpro.mdwn8
1 files changed, 4 insertions, 4 deletions
diff --git a/blog/entry/pinebookpro.mdwn b/blog/entry/pinebookpro.mdwn
index ad0b6ac..65c2619 100644
--- a/blog/entry/pinebookpro.mdwn
+++ b/blog/entry/pinebookpro.mdwn
@@ -8,10 +8,10 @@ not to have it. So, good to have a spare.
I decided to get the machine running the hard way, and have been working to
add a facility to install the device-specific bootloader to
-[Consfigurator](tech/code/consfigurator). It has been good to learn about how
-ARM machines boot. The only really hard part turned out to be coming up with
-the right abstractions within Consfigurator, thanks to the hard work of the
-Debian U-Boot maintainers. This left me with a chroot and a corresponding
+[Consfigurator](/tech/code/consfigurator). It has been good to learn about
+how ARM machines boot. The only really hard part turned out to be coming up
+with the right abstractions within Consfigurator, thanks to the hard work of
+the Debian U-Boot maintainers. This left me with a chroot and a corresponding
disk image, properly partitioned and with the bootloader installed. It was
only then that the difficulties began: getting a kernel and initrd combination
which can output to the Pinebook Pro's screen and take input from its keyboard