Lines Matching refs:firmware

23 firmware includes a boot loader. The target audience for this specification is:
28   firmware itself
43   of traditional firmware mechanisms (e.g. BIOS calls, UEFI Boot Services)
79   different levels. Some firmware implementations do not offer a boot menu at
82 * If the firmware setup is used to reset all data usually all EFI boot entries
83   are lost, making the system entirely unbootable, as the firmware setups
137 For systems where the firmware is able to read file systems directly, `$BOOT`
138 must be a file system readable by the firmware. For other systems and generic
145 text based, very simple and suitable for a variety of firmware, architecture
163 ownership of the whole file system exclusively. Boot loaders, firmware, and
296 generic kernel images that make few assumptions about the firmware they run on,
298 which are not don't make unnecessary assumption on the underlying firmware,
332 systems with EFI firmware. Ignore this section if you work on systems not
383 example a "Reboot into firmware" option. Optionally it may sort the menu based