Lines Matching refs:it
38 'pxe get' uses it to look for a configuration file specific to a system's
43 it to look for a configuration file based on the system's UUID.
47 'pxe get' repeatedly tries to download config files until it either
49 contents of paths it tries mirrors exactly that of PXELINUX - you can
50 read in more detail about it at:
81 store the kernel(or FIT image) and initrd it retrieves from tftp. These
85 fdt_addr_r - location in RAM at which 'pxe boot' will store the fdt blob it
91 command if it is set and 'fdt_addr_r' is not passed to bootm command.
105 not aware of the size of the pxefile memory and will outgrow it if pxe files
141 (or FIT image) at <path>. it will be stored at the address
149 at <path>. it will be stored at the address indicated in
154 at <path>. it will be stored at the address indicated in
210 U-Boot's pxe support is written entirely in C, it can run on any platform
217 - when U-Boot's pxe fails to boot, it will return control to U-Boot,
221 - U-Boot's pxe doesn't rely on or provide an UNDI/PXE stack in memory, it
226 this README. With PXELINUX, it's possible to have a graphical boot
237 disk boot - it will do whatever is defined in the 'localcmd' env
238 variable. And since it doesn't support a full UNDI/PXE stack, the
243 out of 'pxe boot' and use existing U-Boot commands to accomplish it.