summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorDanny Milosavljevic <dannym@scratchpost.org>2018-06-15 09:52:42 +0200
committerDanny Milosavljevic <dannym@scratchpost.org>2018-06-15 14:16:37 +0200
commit4ce4fc501035a8ef461e10d5f3df6ea3a63c7572 (patch)
tree1cfa6216bff505a57129d703428fdfcf284f65a6 /doc
parent0017e55f892828f7a4d29a50f06e5146270ab8cb (diff)
system: Add os-with-u-boot.
* gnu/system/install.scm (os-with-u-boot): New procedure. * gnu/packages/bootloaders.scm (make-u-boot-package): Export. * doc/guix.texi (Building the Installation Image for ARM Boards): New subsection.
Diffstat (limited to 'doc')
-rw-r--r--doc/guix.texi16
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/guix.texi b/doc/guix.texi
index d86ac5044f..a90af34f80 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -8881,6 +8881,22 @@ Have a look at @file{gnu/system/install.scm} in the source tree,
and see also @ref{Invoking guix system} for more information
about the installation image.
+@subsection Building the Installation Image for ARM Boards
+
+Many ARM boards require a specific variant of the
+@uref{http://www.denx.de/wiki/U-Boot/, U-Boot} bootloader.
+
+If you build a disk image and the bootloader is not available otherwise
+(on another boot drive etc), it's advisable to build an image that
+includes the bootloader, specifically:
+
+@example
+guix system disk-image --system=armhf-linux -e '((@@ (gnu system install) os-with-u-boot) (@@ (gnu system install) installation-os) "A20-OLinuXino-Lime2")'
+@end example
+
+@code{A20-OLinuXino-Lime2} is the name of the board. If you specify an invalid
+board, a list of possible boards will be printed.
+
@node System Configuration
@section System Configuration