|
74 | 74 | //! only unfold their potential when you invoke `uefi::helpers::init` as soon
|
75 | 75 | //! as possible in your application.
|
76 | 76 | //!
|
| 77 | +//! # Trivia and Background |
| 78 | +//! |
| 79 | +//! [UEFI] started as the successor firmware to the BIOS in x86 space and |
| 80 | +//! developed to a universal firmware specification for various platforms, such |
| 81 | +//! as ARM. It provides an early boot environment with a variety of |
| 82 | +//! [specified][spec] ready-to-use "high-level" functionality, such as accessing |
| 83 | +//! disks or the network. EFI images, the files that can be loaded by an UEFI |
| 84 | +//! environment, can leverage these abstractions to extend the functionality in |
| 85 | +//! form of additional drivers, OS-specific bootloaders, or any different kind |
| 86 | +//! of low-level applications. |
| 87 | +//! |
| 88 | +//! Even joke projects such as an [IRC client][uefirc] leveraging only existing |
| 89 | +//! UEFI boot services are possible! 😉 |
| 90 | +//! |
77 | 91 | //! [Rust UEFI Book]: https://rust-osdev.github.io/uefi-rs/HEAD/
|
78 | 92 | //! [UEFI]: https://uefi.org/
|
79 | 93 | //! [`BootServices`]: table::boot::BootServices
|
|
84 | 98 | //! [issue tracker]: https://github.com/rust-osdev/uefi-rs/issues
|
85 | 99 | //! [spec]: https://uefi.org/specifications
|
86 | 100 | //! [unstable features]: https://doc.rust-lang.org/unstable-book/
|
| 101 | +//! [uefirc]: https://github.com/codyd51/uefirc |
87 | 102 |
|
88 | 103 | #![cfg_attr(all(feature = "unstable", feature = "alloc"), feature(allocator_api))]
|
89 | 104 | #![cfg_attr(docsrs, feature(doc_auto_cfg))]
|
|
0 commit comments