diff options
| -rw-r--r-- | build/entities/tftp-images.ent | 4 | ||||
| -rw-r--r-- | debian/changelog | 2 | ||||
| -rw-r--r-- | en/boot-installer/arm.xml | 33 |
3 files changed, 39 insertions, 0 deletions
diff --git a/build/entities/tftp-images.ent b/build/entities/tftp-images.ent index 11754a856..c1ae58a32 100644 --- a/build/entities/tftp-images.ent +++ b/build/entities/tftp-images.ent @@ -60,6 +60,10 @@ <ulink url="&downloadable-file;images/hd-media/">.../images/hd-media/</ulink> '> + <!ENTITY armmp-netboot-tarball ' +<ulink url="&downloadable-file;images/netboot/netboot.tar.gz">.../images/netboot/netboot.tar.gz</ulink> + '> + <!ENTITY armmp-uboot-img ' <ulink url="&downloadable-file;images/u-boot/">.../images/u-boot/</ulink> '> diff --git a/debian/changelog b/debian/changelog index 8ef54f946..1f8b8bcd1 100644 --- a/debian/changelog +++ b/debian/changelog @@ -12,6 +12,8 @@ installation-guide (20150324) UNRELEASED; urgency=medium in the "Booting the Installer on ARM" section. * Correct the number of supported architectures (arm64 and ppc64el are release architectures now). + * Add a "Pre-built netboot tarball" subsection for armhf in the + "Booting by TFTP" section. -- Samuel Thibault <sthibault@debian.org> Sat, 28 Mar 2015 10:10:34 +0100 diff --git a/en/boot-installer/arm.xml b/en/boot-installer/arm.xml index 095638a47..dd3a1515b 100644 --- a/en/boot-installer/arm.xml +++ b/en/boot-installer/arm.xml @@ -126,6 +126,39 @@ bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r} kernel without device-tree, simply omit the ${fdt_addr_r} parameter. </para> </sect3> + + <sect3 arch="armhf" id="boot-armhf-netboot.tar.gz"> + <title>Pre-built netboot tarball</title> + <para> + &debian; provides a pre-built tarball (&armmp-netboot-tarball;) + that can simply be unpacked on your tftp server and contains + all files necessary for netbooting. It also includes a boot + script that automates all steps to load the installer. Modern + u-boot versions contain a tftp autoboot feature that becomes + active if there is no bootable local storage device (MMC/SD, + USB, IDE/SATA/SCSI) and then loads this boot script from the + tftp server. Prerequisite for using this feature is that you + have a dhcp server in your network which provides the client + with the address of the tftp server. + </para> + <para> + If you would like to trigger the tftp autoboot feature from the + u-boot commandline, you can use the follwing command: + <informalexample><screen>run bootcmd_dhcp</screen></informalexample> + </para> + <para> + To manually load the bootscript provided by the tarball, you can + alternatively issue the following commands at the u-boot prompt: + +<informalexample><screen> +setenv autoload no +dhcp +tftpboot ${scriptaddr} /debian-installer/armhf/tftpboot.scr +source ${scriptaddr} +</screen></informalexample> + + </para> + </sect3> </sect2> |