Lines Matching full:it

16 Trying it out
31 - You have EFI running on a board but U-Boot does not natively support it
36 requires it in order to provide support
53 memory and type 'help' but that is about it.
64 for that board. It will be either 32-bit or 64-bit. Alternatively, you can
89 Trying it out
91 QEMU is an emulator and it can emulate an x86 machine. Please make sure your
99 Add -nographic if you want to use the terminal for output. Once it starts
104 To try it on real hardware, put u-boot-app.efi on a suitable boot medium,
105 such as a USB stick. Then you can type something like this to start it:
113 EFI (or vice versa). Also it will often fail to print an error message if
128 efi_main() function is in lib/efi/efi_app.c. It sets up some basic EFI
139 'boot services' to send and receive characters. Although it is implemented
150 little x86-specific code involved - you can find most of it in
158 The payload approach is a different kettle of fish. It works by building
161 for booting it. The stub application is built as a normal EFI application
162 except that it has a lot of data attached to it.
165 function is called by EFI. It is responsible for copying U-Boot from its
169 The stub application is architecture-dependent. At present it has some
173 used by U-Boot (the payload). In fact when U-Boot starts it has all of the
174 memory available to it and can operate as it pleases (but see the next
185 Although U-Boot can use any memory it likes, EFI marks some memory as used
189 fan speed. U-Boot uses only 'conventional' memory, in EFI terminology. It
190 will relocate itself to the top of the largest block of memory it can find
196 it is possible that an interrupt will fire that U-Boot cannot handle. This
223 use case is not readily apparent, but it might be fun.
226 use of boot services in case it wants to. It is unclear what it might want