vasilito
198e59c474
Round 3 of the LG Gram 16Z90TP compatibility work. Wires the last
remaining SystemQuirkFlags consumer that was deferred from Round 1:
acpi_irq1_skip_override, implemented as a kernel-side DMI match
(Linux's irq1_level_low_skip_override[] pattern).
Three changes:
1. New kernel module src/acpi/smbios.rs (~320 lines):
- Minimal SMBIOS / DMI table scanning for early-boot platform
identification. Scans 0xF0000-0xFFFFF for _SM3_/_SM_ anchor,
validates checksums, walks the structure table, extracts
sys_vendor + product_name + board_name + board_vendor from
Type 1 + Type 2 structures.
- Defensive by design: every error returns None, no panics.
Failed or absent SMBIOS is never fatal — callers fall through
to 'no quirks'.
- String lifetimes are 'static (mapped physical memory is never
unmapped during kernel lifetime).
- Pattern ported from acpid/src/dmi.rs (userspace), simplified
for kernel context (no std, no allocations during scan).
2. acpi/mod.rs: expose map_physical_range as pub(crate), add
'pub mod smbios', call smbios::init() in init_after_mem BEFORE
Madt::init() so SMBIOS_INFO is populated when ioapic runs.
3. arch/x86_shared/device/ioapic.rs: add IRQ1_SKIP_OVERRIDE_VENDORS
table (currently ['LG Electronics']) and should_skip_irq1_override()
check. In handle_src_override: if irq_source==1 AND polarity_raw
indicates ActiveHigh AND platform matches the vendor table, skip
the override so the DSDT's ActiveLow trigger stays in effect.
Without this skip, the LG Gram's i8042 keyboard IRQ stops firing
after the MADT override flips it to ActiveHigh — keys are dropped
or the controller wedges. Linux's fix is the same pattern in
drivers/acpi/resource.c irq1_level_low_skip_override[].
Build verification deferred per operator directive (kernel boot code
requires canonical build + QEMU proof). The code follows the kernel's
existing patterns (KernelMapper::lock_rw, map_linearly, RmmA::phys_to_virt)
and uses the kernel's built-in info!/debug! macros rather than the log
crate.
Kernel
Redox OS Microkernel
Requirements
nasmneeds to be available on the PATH at build time.
Building The Documentation
Use this command:
cargo doc --open --target x86_64-unknown-none
Debugging
QEMU
Running QEMU with the -s flag will set up QEMU to listen on port 1234 for a GDB client to connect to it. To debug the redox kernel run.
make qemu gdb=yes
This will start a virtual machine with and listen on port 1234 for a GDB or LLDB client.
GDB
If you are going to use GDB, run these commands to load debug symbols and connect to your running kernel:
(gdb) symbol-file build/kernel.sym
(gdb) target remote localhost:1234
LLDB
If you are going to use LLDB, run these commands to start debugging:
(lldb) target create -s build/kernel.sym build/kernel
(lldb) gdb-remote localhost:1234
After connecting to your kernel you can set some interesting breakpoints and continue
the process. See your debuggers man page for more information on useful commands to run.
Notes
-
Always use
foo.get(n)instead offoo[n]and try to cover for the possibility ofOption::None. Doing the regular way may work fine for applications, but never in the kernel. No possible panics should ever exist in kernel space, because then the whole OS would just stop working. -
If you receive a kernel panic in QEMU, use
pkill qemu-systemto kill the frozen QEMU process.
How To Contribute
To learn how to contribute to this system component you need to read the following document:
Development
To learn how to do development with this system component inside the Redox build system you need to read the Build System and Coding and Building pages.
How To Build
To build this system component you need to download the Redox build system, you can learn how to do it on the Building Redox page.
This is necessary because they only work with cross-compilation to a Redox virtual machine, but you can do some testing from Linux.
Funding - Unix-style Signals and Process Management
This project is funded through NGI Zero Core, a fund established by NLnet with financial support from the European Commission's Next Generation Internet program. Learn more at the NLnet project page.
