From 40d45c1422c442b77910c058fe242f0f736d4a82 Mon Sep 17 00:00:00 2001 From: vasilito Date: Sat, 18 Jul 2026 00:33:56 +0900 Subject: [PATCH] docs(hardware): record working text-console login + driver coverage Text login (getty -> brush) works on bare/mini after the relibc F_DUPFD_CLOEXEC fix; document storage/USB/GOP bare-metal boot coverage and the outstanding Intel 2.5GbE igc (I225/I226) and e1000e (I219) network driver gap for modern Arrow Lake boards. --- HARDWARE.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/HARDWARE.md b/HARDWARE.md index aa347da78f..b6bbfd8951 100644 --- a/HARDWARE.md +++ b/HARDWARE.md @@ -52,6 +52,24 @@ We also recommend to add your `pciutils` log as a comment on [this](https://gitl This section contain limitations that apply to any status. +- Text-mode console login is **working** on the `redbear-bare` and `redbear-mini` + targets: the boot reaches a `getty` login prompt (serial debug console and + framebuffer VT) and authenticates into the default shell **`brush`** (a + Rust-native shell; `zsh`/`ion` are no longer the default). This depends on a + relibc fix that translates the POSIX `F_DUPFD_CLOEXEC` fcntl command to the + Redox syscall ABI — without it `OwnedFd::try_clone()` returned EINVAL and every + `tokio` runtime (all zbus system daemons and the shell) failed to start. +- Storage, USB and display bring-up cover the common modern-Intel (incl. Arrow + Lake) bare-metal boot path: NVMe (`nvmed`), AHCI/SATA (`ahcid`), USB 3 xHCI + (`xhcid`) with USB HID input, and UEFI GOP framebuffer (`vesad`). An empty + ATAPI/optical drive is now handled as a normal no-media state instead of + logging I/O errors. +- Wired networking driver coverage is Intel `e1000` (`e1000d`), Intel 10G + (`ixgbed`), Realtek `rtl8139`/`rtl8168`, and `virtio-net`. **Intel 2.5 GbE + `igc` (I225/I226, common on modern Arrow Lake / Z890 boards) and `e1000e` + (I219) are not yet supported** — a machine relying solely on one of those has + no Ethernet until a driver is added. Text login is unaffected (it does not + require networking). - ACPI bring-up is **materially complete for boot baseline**; implemented: kernel RSDP/RSDT/XSDT/MADT/FADT coverage, AML mutexes with real tracked state, EC widened accesses via byte transactions, kstop-based shutdown eventing, explicit `RSDP_ADDR` forwarding into `acpid`,