Lines Matching full:application

8 as an application or just as a means of getting U-Boot onto a new platform.
18 EFI Application
51 U-Boot supports running as an EFI application for 32-bit EFI only. This is
67 To build U-Boot as an EFI application (32-bit EFI required), enable CONFIG_EFI
85    u-boot-app.efi      - U-Boot EFI application
86    u-boot-payload.efi  - U-Boot EFI payload application
101 run the application. 'bios.bin' is the EFI 'BIOS'. Check [2] to obtain a
109 (or fs0:u-boot-app.efi for the application)
112 that EFI does not support booting a 64-bit application from a 32-bit
122 The application and payload approaches sound similar but are in fact
125 EFI Application
127 For the application the whole of U-Boot is built as a shared library. The
147 Very little code is involved in implementing the EFI application feature.
160 image (including device tree) into a small EFI stub application responsible
161 for booting it. The stub application is built as a normal EFI application
164 The stub application is implemented in lib/efi/efi_stub.c. The efi_main()
169 The stub application is architecture-dependent. At present it has some
172 While the stub application does allocate some memory from EFI this is not
202 While the EFI application can in principle be built as either 32- or 64-bit,
203 only 32-bit is currently supported. This means that the application can only
217 - Add 64-bit application support
221 - Add more drivers to the application side (e.g. video, block devices, USB,
232 	payload stub, application, support code. Mostly arch-neutral
235 	x86 support code for running as an EFI application and payload
238 	x86 board code for running as an EFI application