File tree 1 file changed +13
-3
lines changed
1 file changed +13
-3
lines changed Original file line number Diff line number Diff line change 20
20
//! _Note that for producing EFI images, you also need to use a corresponding
21
21
//! `uefi` compiler target of Rust, such as `x86_64-unknown-uefi`._
22
22
//!
23
- //! # Interaction with uefi services
23
+ //! ## Example Use Cases
24
24
//!
25
25
//! With this crate you can write code for the pre- and post-exit boot services
26
- //! epochs. However, the `uefi` crate unfolds its true potential when
27
- //! interacting with UEFI boot services.
26
+ //! epochs. However, the `uefi` crate unfolds its true potential when crafting
27
+ //! EFI images interacting with UEFI boot services and eventually exiting them.
28
+ //!
29
+ //! By EFI images (`image.efi`), we are referring to EFI applications, EFI
30
+ //! boot service drivers, and EFI runtime service drivers. An EFI application
31
+ //! might be your OS-specific loader technically similar to _GRUB_ or _Limine_.
32
+ //!
33
+ //! You can also use this crate to parse the UEFI memory map when a bootloader,
34
+ //! such as _GRUB_ or _Limine_, passed the UEFI memory map as part of the
35
+ //! corresponding boot information to your kernel, or to access runtime services
36
+ //! from your kernel. Hence, when you also use utilize `uefi` also in ELF
37
+ //! binaries and are not limited to EFI images.
28
38
//!
29
39
//! # Crate organisation
30
40
//!
You can’t perform that action at this time.
0 commit comments