|
97 | 97 | //! only unfold their potential when you invoke `uefi::helpers::init` as soon
|
98 | 98 | //! as possible in your application.
|
99 | 99 | //!
|
| 100 | +//! # Trivia and Background |
| 101 | +//! |
| 102 | +//! [UEFI] started as the successor firmware to the BIOS in x86 space and |
| 103 | +//! developed to a universal firmware specification for various platforms, such |
| 104 | +//! as ARM. It provides an early boot environment with a variety of |
| 105 | +//! [specified][spec] ready-to-use "high-level" functionality, such as accessing |
| 106 | +//! disks or the network. EFI images, the files that can be loaded by an UEFI |
| 107 | +//! environment, can leverage these abstractions to extend the functionality in |
| 108 | +//! form of additional drivers, OS-specific bootloaders, or any different kind |
| 109 | +//! of low-level applications. |
| 110 | +//! |
| 111 | +//! Even joke projects such as an [IRC client][uefirc] leveraging only existing |
| 112 | +//! UEFI boot services are possible! 😉 |
| 113 | +//! |
100 | 114 | //! [Rust UEFI Book]: https://rust-osdev.github.io/uefi-rs/HEAD/
|
101 | 115 | //! [UEFI]: https://uefi.org/
|
102 | 116 | //! [`BootServices`]: table::boot::BootServices
|
|
107 | 121 | //! [issue tracker]: https://github.com/rust-osdev/uefi-rs/issues
|
108 | 122 | //! [spec]: https://uefi.org/specifications
|
109 | 123 | //! [unstable features]: https://doc.rust-lang.org/unstable-book/
|
| 124 | +//! [uefirc]: https://github.com/codyd51/uefirc |
110 | 125 |
|
111 | 126 | #![cfg_attr(all(feature = "unstable", feature = "alloc"), feature(allocator_api))]
|
112 | 127 | #![cfg_attr(docsrs, feature(doc_auto_cfg))]
|
|
0 commit comments