Lines Matching refs:payload

63 More usefully, U-Boot supports building itself as a payload for either 32-bit
82 To build U-Boot as an EFI payload (32-bit or 64-bit EFI can be used), adjust an
93    u-boot-payload.efi  - U-Boot EFI payload application
99 QEMU version is 2.3.0 or above to test this. You can run the payload with
107 type 'fs0:u-boot-payload.efi' to run the payload or 'fs0:u-boot-app.efi' to
114    fs0:u-boot-payload.efi
118 This will start the payload, copy U-Boot into RAM and start U-Boot. Note
129 The application and payload approaches sound similar but are in fact
165 The payload approach is a different kettle of fish. It works by building
180 used by U-Boot (the payload). In fact when U-Boot starts it has all of the
186 The payload can pass information to U-Boot in the form of EFI tables. At
204 seems to cause problems. For this reason the U-Boot payload runs with
213 The payload stub can be build as either 32- or 64-bits. Only a small amount
222 - Add a generic x86 EFI payload configuration. At present you need to modify
244 	payload stub, application, support code. Mostly arch-neutral
248 	any board that runs as a payload.
279 With this support in place, you can run any UEFI payload (such as the Linux
306 All storage devices are directly accessible from the uEFI payload
338    - Support for payload exit