Fix: Handle changes for MADT in acpi crate (#223)

- Adapted to the changes introduced in the acpi crate PR #223,
  specifically for the MADT structure.
- Updated handling of MADT entries to align with the new API.
- Used Pin<&Madt> to ensure immovable references when accessing MADT entries,
  in response to changes in the MADT structure.
- Adjusted usage of MADT pointers to accommodate the new access pattern
  introduced by the acpi crate update.

See: rust-osdev/acpi#223

Author: 5unsetpowerln

kernel/src/acpi.rs

@@ -1,4 +1,8 @@
-use core::{marker::PhantomData, ptr::read_unaligned};
+use core::{
+    marker::PhantomData,
+    pin::{Pin, pin},
+    ptr::read_unaligned,
+};
 
 use acpi::{
     AcpiError,
@@ -102,7 +106,7 @@ pub struct ApicInfo {
 }
 
 impl ApicInfo {
-    fn from_madt(madt: &Madt) -> Self {
+    fn from_madt(madt: Pin<&Madt>) -> Self {
         // Find the entry about I/O APIC from the MADT.
         let io_apic_entry = madt
             .entries()
@@ -199,11 +203,13 @@ pub unsafe fn init(rsdp_addr: PhysPtr) {
         panic!();
     }
 
+    let madt = unsafe { Pin::new_unchecked(&*madt_ptr) };
+
     kprintln!("FADT is found: 0x{:X}", fadt_ptr as u64);
     FADT.call_once(|| *fadt_ptr);
 
     kprintln!("MADT is found: 0x{:X}", madt_ptr as u64);
-    APIC_INFO.call_once(|| ApicInfo::from_madt(&*madt_ptr));
+    APIC_INFO.call_once(|| ApicInfo::from_madt(madt));
 }
 
 pub fn get_fadt() -> &'static Fadt {