Lines Matching refs:be

9 First of all, a root filesystem must be made available. This can be done in
14       A filesystem should be constructed in a directory on an NFS server that
15       the target board can reach. This directory should then be NFS exported
20       In this case, the image must be stored or built up on flash before it
21       can be used. A complete image can be built using the mkfs.jffs2 or
29 The kernel will need to be loaded into RAM by RedBoot (or by some alternative
30 boot loader) before it can be run. The kernel image (arch/frv/boot/Image) may
31 be loaded in one of three ways:
42       The image is then ready to be executed.
51       The image is then ready to be executed.
60       The serial client (such as minicom) must then be told to transmit the
63       When finished, the image will then be ready to be executed.
89       serial port <x> (which can be "0" or "1").
112       may be specified by major and minor number, device path, or even
121       Authoritative information can be found in
136       If <cfg> is "bootp" or "dhcp", then all of these parameters will be
139       For example, the following might be used:
144       (eth0) to be 192.168.73.12, and sets the board's hostname to be "frv".
152       The NFS version to use can also be specified. v2 and v3 are supported by
165       This can be used as an alternative to the "console=ttyS..." listed
175       SDRAM controller registers. That can be overridden with this
176       option. This allows the kernel to be told that it has <xxx> megabytes of