If a CPU server is up, BOOTP/DHCP and TFTP will run from there; if not, the necessary files and services must be available on a separate machine, such as a Unix system, to use these protocols for bootstrapping.
Be sure to read boot (8) to understand what happens after the kernel is loaded.
Once the kernel is booted, it behaves like the others. See boot (8) for details.
.L /arm/9gd for the Marvell PXA168-based Guruplug Display
.L /arm/9plug for other Marvell Kirkwoods (Sheevaplug, Guruplug, Dreamplug, Openrd, etc.)
.L /arm/9beagle for TI OMAP3 boards (IGEPv2 from ISEE, Gumstix Overo)
.L /arm/9ts for Trimslice systems, which contain the Nvidia Tegra 2
.L /arm/9pi
.L /arm/9picpu for Raspberry Pis
In the following, replace MAC with your board's MAC address without colons, in lower case (the format of the .L ether ndb attribute). If loading from a non-Plan-9 TFTP server, replace .L %C with /cfg/pxe/ MAC.
First, establish a /cfg/pxe (\c plan9.ini ) file for the new CPU server. For Kirkwood plugs,
.EX cd /cfg/pxe; cp example-kw MACand edit .L /cfg/pxe/MAC to taste. For PXA plugs, replace .L kw with .LR pxa ; for OMAP boards, replace .L kw with .LR omap and be sure to edit the line for .L ether0 to set
.EX ea=MACSecond, configure U-boot to load the appropriate kernel and /cfg/pxe file at suitable addresses and start the kernel. For Sheevaplugs and Openrd boards, type this at U-boot once:
.EX setenv bootdelay 2 # type the next two lines as one setenv bootcmd 'bootp; bootp; tftp 0x1000 %C; bootp; tftp 0x800000; go 0x800000' saveenvFor Guruplugs Displays, do the same but type this after .L "setenv bootcmd" instead:
.EX 'dhcp; tftpboot; tftpboot 0x1000 %C; bootz 0x500000'For Kirkwood Guruplugs, type this after .LR "setenv bootcmd" :
.EX 'dhcp 0x800000; tftp 0x1000 %C; go 0x800000'For IGEPv2 boards, type this after .LR "setenv bootcmd" :
.EX 'tftp 0x80300000 %C; dhcp 0x80310000; go 0x80310000'For Gumstix Overo boards, type this after .LR "setenv bootcmd" :
.EX 'bootp 0x80310000; bootp 0x80300000 %C; go 0x80310000'For Trimslice systems, type this after .LR "setenv bootcmd" :
.EX 'dhcp; dhcp; tftpboot 0x410000; tftpboot 0x400000 %C; go 0x410000'For Raspberry Pis, gunzip the pi.uboot.sd.img.gz named below onto an SD card and insert that into your Pi.
Thereafter, the boards will automatically boot via BOOTP and TFTP when reset. .