nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2025-02-16 17:03:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add crate links to unknown-uefi.md

Browse Source
This commit is contained in:
Nicholas Bishop 2024-01-13 12:59:00 -05:00
parent 1d8d7b16cb
commit 074220296d
1 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
src/doc/rustc/src/platform-support/unknown-uefi.md
View File

@ -88,7 +88,7 @@ UEFI applications can be copied into the ESP on any UEFI system and executed
via the firmware boot menu. The qemu suite allows emulating UEFI systems and via the firmware boot menu. The qemu suite allows emulating UEFI systems and
executing UEFI applications as well. See its documentation for details. executing UEFI applications as well. See its documentation for details.
The [uefi-run](https://github.com/Richard-W/uefi-run) rust tool is a simple The [uefi-run] rust tool is a simple
wrapper around `qemu` that can spawn UEFI applications in qemu. You can install wrapper around `qemu` that can spawn UEFI applications in qemu. You can install
it via `cargo install uefi-run` and execute qemu applications as it via `cargo install uefi-run` and execute qemu applications as
`uefi-run ./application.efi`. `uefi-run ./application.efi`.
@ -132,19 +132,19 @@ have been developed to provide access to UEFI protocols and make UEFI
programming more ergonomic in rust. The following list is a short overview (in programming more ergonomic in rust. The following list is a short overview (in
alphabetical ordering): alphabetical ordering):
- **efi**: *Ergonomic Rust bindings for writing UEFI applications*. Provides - **[efi][efi-crate]**: *Ergonomic Rust bindings for writing UEFI applications*. Provides
_rustified_ access to UEFI protocols, implements allocators and a safe _rustified_ access to UEFI protocols, implements allocators and a safe
environment to write UEFI applications. environment to write UEFI applications.
- **r-efi**: *UEFI Reference Specification Protocol Constants and Definitions*. - **[r-efi]**: *UEFI Reference Specification Protocol Constants and Definitions*.
A pure transpose of the UEFI specification into rust. This provides the raw A pure transpose of the UEFI specification into rust. This provides the raw
definitions from the specification, without any extended helpers or definitions from the specification, without any extended helpers or
_rustification_. It serves as baseline to implement any more elaborate rust _rustification_. It serves as baseline to implement any more elaborate rust
UEFI layers. UEFI layers.
- **uefi-rs**: *Safe and easy-to-use wrapper for building UEFI apps*. An - **[uefi-rs]**: *Safe and easy-to-use wrapper for building UEFI apps*. An
elaborate library providing safe abstractions for UEFI protocols and elaborate library providing safe abstractions for UEFI protocols and
features. It implements allocators and provides an execution environment to features. It implements allocators and provides an execution environment to
UEFI applications written in rust. UEFI applications written in rust.
- **uefi-run**: *Run UEFI applications*. A small wrapper around _qemu_ to spawn - **[uefi-run]**: *Run UEFI applications*. A small wrapper around _qemu_ to spawn
UEFI applications in an emulated `x86_64` machine. UEFI applications in an emulated `x86_64` machine.
## Example: Freestanding ## Example: Freestanding
@ -311,3 +311,8 @@ pub fn main() {
The current implementation of std makes `BootServices` unavailable once `ExitBootServices` is called. Refer to [Runtime Drivers](https://edk2-docs.gitbook.io/edk-ii-uefi-driver-writer-s-guide/7_driver_entry_point/711_runtime_drivers) for more information regarding how to handle switching from using physical addresses to using virtual addresses. The current implementation of std makes `BootServices` unavailable once `ExitBootServices` is called. Refer to [Runtime Drivers](https://edk2-docs.gitbook.io/edk-ii-uefi-driver-writer-s-guide/7_driver_entry_point/711_runtime_drivers) for more information regarding how to handle switching from using physical addresses to using virtual addresses.
Note: It should be noted that it is up to the user to drop all allocated memory before `ExitBootServices` is called. Note: It should be noted that it is up to the user to drop all allocated memory before `ExitBootServices` is called.
[efi-crate]: https://github.com/gurry/efi
[r-efi]: https://github.com/r-efi/r-efi
[uefi-rs]: https://github.com/rust-osdev/uefi-rs
[uefi-run]: https://github.com/Richard-W/uefi-run