Merge #54

54: Rename aml_parser to aml r=IsaacWoods a=64

Progress on #48

Co-authored-by: Matt Taylor <mstaveleytaylor@gmail.com>

Cargo.toml

@@ -1,2 +1,2 @@
 [workspace]
-members = ["acpi", "aml_parser"]
+members = ["acpi", "aml"]

README.md

@@ -3,11 +3,11 @@
 [![Version](https://img.shields.io/crates/v/acpi.svg?style=rounded-square)](https://crates.io/crates/acpi/)
 
 ### [Documentation (`acpi`)](https://docs.rs/acpi)
-### [Documentation (`aml_parser`)](https://docs.rs/aml_parser)
+### [Documentation (`aml`)](https://docs.rs/aml)
 
 A library to parse ACPI tables and AML, written in pure Rust. Designed to be easy to use from Rust bootloaders and kernels. The library is split into two crates:
 - `acpi` parses the static tables (useful but not feature-complete)
-- `aml_parser` parses the AML tables (can parse some namespaces, cannot yet execute methods)
+- `aml` parses the AML tables (can parse some namespaces, cannot yet execute methods)
 
 ## Contributing
 Contributions are more than welcome! You can:

acpi/src/lib.rs

@@ -3,7 +3,7 @@
 //! for finding and parsing the static tables, which is enough to set up hardware such as the APIC
 //! and HPET on x86_64.
 //!
-//! The crate is designed for use in conjunction with the `aml_parser` crate, which is the (much
+//! The crate is designed for use in conjunction with the `aml` crate, which is the (much
 //! less complete) AML parser used to parse the DSDT and SSDTs. These crates are separate because
 //! some kernels may want to detect the static tables, but delay AML parsing to a later stage.
 //!

aml_parser/Cargo.toml → aml/Cargo.toml

@@ -1,5 +1,5 @@
 [package]
-name = "aml_parser"
+name = "aml"
 version = "0.3.0"
 authors = ["Isaac Woods"]
 repository = "https://github.com/rust-osdev/acpi"

aml_parser/src/lib.rs → aml/src/lib.rs

@@ -1,4 +1,4 @@
-//! `aml_parser` is a pure-Rust AML (ACPI Machine Language) parser, used for parsing the DSDT and
+//! `aml` is a pure-Rust AML (ACPI Machine Language) parser, used for parsing the DSDT and
 //! SSDT tables from ACPI. This crate can be used by kernels to gather information about the
 //! hardware, and invoke control methods (this is not yet supported) to query and change the state
 //! of devices in a hardware-independent way.