4f8ca7069c
`from_initialized_mem` only checked that `desc_size` was large enough, unlike the `MemoryMapRef`/`MemoryMapRefMut` constructors, which also require it to be a multiple of the descriptor alignment. With an unaligned `desc_size`, every entry but the first was accessed through a misaligned `&MemoryDescriptor`. Reuse `validate_meta` so all constructors enforce the same invariant. |
||
|---|---|---|
| .. | ||
| src | ||
| tests | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| README.md | ||
uefi
Rusty wrapper for the Unified Extensible Firmware Interface.
This crate makes it easy to develop Rust software that leverages safe, convenient, and performant abstractions for UEFI functionality.
Value-add and Use Cases
uefi supports writing code for both pre- and post-exit boot services
epochs, but its true strength shines when you create UEFI images that heavily
interact with UEFI boot services. Still, you have the flexibility to just
integrate selected types and abstractions into your project, for example to
parse the UEFI memory map.
Note that for producing UEFI images, you also need to use a corresponding
uefi compiler target of Rust, such as x86_64-unknown-uefi.
API and User Documentation
Please refer to docs.rs for comprehensive documentation
of the latest stable release. The latest not necessarily yet published
documentation can be found in src/lib.rs, which can also be
locally viewed by running $ cargo xtask doc --open.
For an introduction to the uefi-rs project and this repository, please refer
to our main README.