Lines Matching refs:in

12 systems. Data is transferred between the boot loader and systemd in EFI
16 * The EFI Variable `LoaderTimeInitUSec` contains the timestamp in microseconds
17   when the loader was initialized. This value is the time spent in the firmware
19   string, in UTF-16.
21 * The EFI Variable `LoaderTimeExecUSec` contains the timestamp in microseconds
23   time spent in the loader is the difference between `LoaderTimeExecUSec` and
28   ESP the boot loader was run from formatted as NUL-terminated UTF16 string, in
32   currently in use. It may be modified both by the boot loader and by the
34   string, in UTF-16. The time is specified in µs.
37   timeout for a single following boot. It is set by the OS in order to request
48   alphanumeric string (possibly containing `-`, too). The list should be in the
56   loader entry to use for a single following boot. It is set by the OS in order
64   the OS in order to identify which entry has been used for the current boot.
75 …* `1 << 4` → The boot loader supports boot counting as described in [Automatic Boot Assessment](AU…
76 …* `1 << 5` → The boot loader supports looking for boot menu entries in the Extended Boot Loader Pa…
90   seed to store in the ESP the boot loader can protect itself from situations
93   (i.e. in physical NVRAM) of the ESP file system storage, and only the latter
100 will include them in its boot-time analysis.  If `LoaderDevicePartUUID` is set,
114 the identifiers as passed in `LoaderEntries`, `LoaderEntryDefault`,
116 names for them in UIs.
119    [Boot Loader Specification](BOOT_LOADER_SPECIFICATION.md) drop-in files
120    the identifier should be derived directly from the drop-in snippet name, but
121    with the `.conf` (or `.efi` in case of Type #2 entries) suffix removed.
124    configured in configuration files) should generally have an identifier
145    `auto-reboot-to-firmware-setup` in case it is automatically discovered).