d76b303061
Per spec, the EFI_BLOCK_IO_MEDIA members LowestAlignedLba and LogicalBlocksPerPhysicalBlock are only present if the protocol revision is at least 2, and OptimalTransferLengthGranularity only with revision 3. The BlockIOMedia accessors read these fields unconditionally, i.e. past the firmware-defined structure on revision-1 implementations. Since the media struct itself does not carry the revision, move the three accessors to BlockIO (which does) and return None on old revisions. They are intentionally not offered on BlockIO2: that protocol has no revision field of its own, and the spec ties the fields' presence to the Block I/O protocol revision. |
||
|---|---|---|
| .. | ||
| 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.