acpi: rewrite most of the library

- Correct a number of bugs in how we handle mapped regions of SDTs
- Simplify API on `AcpiTables`
- Move all `alloc`-usage into `platform`
- Move all SDT types under new `sdt` module
- Move from `ManagedSlice` back to just using `Vec`
- Improve documentation throughout the library
- Remove `AcpiResult` type in preference of normal `Result`

Author: IsaacWoods

acpi/Cargo.toml

@@ -3,11 +3,11 @@ name = "acpi"
 version = "5.2.0"
 authors = ["Isaac Woods"]
 repository = "https://github.com/rust-osdev/acpi"
-description = "A pure-Rust library for parsing ACPI tables"
+description = "A pure-Rust library for interacting with ACPI"
 categories = ["hardware-support", "no-std"]
 readme = "../README.md"
 license = "MIT/Apache-2.0"
-edition = "2021"
+edition = "2024"
 
 [dependencies]
 bit_field = "0.10.2"

acpi/src/address.rs

@@ -1,7 +1,7 @@
 //! ACPI defines a Generic Address Structure (GAS), which provides a versatile way to describe register locations
 //! in a wide range of address spaces.
 
-use crate::{AcpiError, AcpiResult};
+use crate::AcpiError;
 
 /// This is the raw form of a Generic Address Structure, and follows the layout found in the ACPI tables.
 #[derive(Clone, Copy, Debug)]
@@ -83,7 +83,7 @@ pub struct GenericAddress {
 }
 
 impl GenericAddress {
-    pub fn from_raw(raw: RawGenericAddress) -> AcpiResult<GenericAddress> {
+    pub fn from_raw(raw: RawGenericAddress) -> Result<GenericAddress, AcpiError> {
         let address_space = match raw.address_space {
             0x00 => AddressSpace::SystemMemory,
             0x01 => AddressSpace::SystemIo,

acpi/src/handler.rs

@@ -54,7 +54,6 @@ where
     ///   dropped, it will be used to unmap the structure.
     ///
     /// ### Safety
-    ///
     /// The caller must ensure that the physical memory can be safely mapped.
     pub unsafe fn new(
         physical_start: usize,
@@ -128,7 +127,7 @@ where
 /// functionality, such as mapping regions of physical memory. You are free to implement these
 /// however you please, as long as they conform to the documentation of each function. The handler is stored in
 /// every `PhysicalMapping` so it's able to unmap itself when dropped, so this type needs to be something you can
-/// clone/move about freely (e.g. a reference, wrapper over `Rc`, marker struct, etc.).
+/// clone/move about freely (e.g. a reference, wrapper over `Arc`, marker struct, etc.).
 pub trait AcpiHandler: Clone {
     /// Given a physical address and a size, map a region of physical memory that contains `T` (note: the passed
     /// size may be larger than `size_of::<T>()`). The address is not neccessarily page-aligned, so the