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