vasilito
bd656d7f2c
Round 7 LG Gram 16Z90TP-G.AL89C compatibility work.
BLOCKING ERRORS FIXED (smbios.rs):
- Wrap map_physical_range() calls in unsafe {} blocks at lines 83, 180
(unsafe-op-in-unsafe-fn is denied in edition 2024)
- Fix lifetime: bytes is &'static [u8] since mapped SMBIOS memory persists
for kernel lifetime; propagate &'static through dmi_string, decode_type_1,
decode_type_2 signatures
E0133 WARNINGS FIXED (interrupt/mod.rs):
- Wrap mwait_loop inline asm! in unsafe {} block
- Wrap enable_and_halt() + mwait_loop() calls in idle_loop in unsafe {} blocks
UNNECESSARY-UNSAFE WARNINGS FIXED:
- cpuid.rs: remove unsafe {} wrapper around now-safe __cpuid_count intrinsic
- tsc.rs: remove unsafe {} wrapper around now-safe rdtsc intrinsic
GENERAL WARNING CLEANUP (~40 warnings across 19 files):
- Remove unused imports: rmm/lib.rs, acpi/mod.rs, rsdt.rs, rxsdt.rs,
slit.rs, srat/, xsdt.rs, context/mod.rs, memory/mod.rs, numa.rs,
scheme/user.rs, syscall/fs.rs
- Prefix unused variables with _
- Remove unnecessary mut
- Remove unnecessary unsafe {} blocks: stop.rs, srat/mod.rs, memory/mod.rs
Verified: repo cook kernel --force-rebuild succeeds with zero errors and
zero warnings.
LG Gram 16Z90TP-G.AL89C: SMBIOS scan now reads vendor/model/panel
orientation table for quirks-driven panel orientation detection.
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.
