Drivers & buses

Polled hardware, one vtable per bus.

Most NebOS drivers are polled rather than interrupt-driven: storage, USB and every NIC are serviced from process context. That trades latency and CPU time for simple, single-owner state and a kernel that stays easy to reason about on old hardware.

PCI enumeration FDC · PATA · SATA UHCI · OHCI · EHCI · xHCI PS/2 · USB · I2C touchpad

Driver inventory

Every driver in the tree is small enough to read in one sitting. The table below is the quickest way to find the one responsible for a device.

SubsystemDriverBus / accessService model
Floppydisk.cISA FDC + DMA channel 2IRQ 6; FAT operations set sys_fs_busy
PATAata.cLegacy ports or PCI native BARsPolled PIO, DRQ wait per sector
SATAahci.cPCI AHCI MMIOPolled, READ/WRITE DMA EXT
USBusb.c + uhci.c ohci.c ehci.c xhci.cPCI I/O ports or MMIOPolled; hotplug watcher in the WM loop
Networke1000e.c r8168.c ne2000.c asix.cPCI or USBPolled, one active receiver
PS/2mouse.c, io.ci8042IRQ 1 keyboard, IRQ 12 mouse; polling fallback
Touchpadi2c.c, touchpad.cLPSS DesignWare I2C, slave 0x15Polled input register every 25 ms; no GPIO interrupt driver
Serialserial.c16550 UART, COM1IRQ 4 ring buffer + polled transmitter
Thermalthermal.cIntel DTS MSRSampled once a second from the scheduler tick
Board sensors / ECit87.c, tpec.c, ec.c, cros_ec.cSuper I/O, ThinkPad H8 EC, Chrome OS EC (temps, fans, battery, AC, switches)Polled; EC battery-index/FIFO/page-selector writes only
Wall clockrtc.cCMOS RTC ports 0x70/0x71Read/write under the BKL; update-cycle retries and a 1970–2069 two-digit year window

PCI & discovery

pci.c walks bus/device/function and exposes BAR and capability access. The USB scan checks all functions: real PIIX3/PIIX4/VIA layouts put the USB function at 0:07.2 or 0:01.2, not 0:07.0. Controllers with unassigned BARs are ignored rather than driven at address zero.

MMIO regions are mapped through paging_map_mmio(). PCI interrupts are disabled before touching MMIO, so every driver polls its own status registers. lspci lists every function; with a filter it prints BAR type, size and address details.

Storage

blkdev.c is a small registry of block devices. Each device exposes sector read/write plus geometry; FAT and the format command sit above that interface and never talk to a controller directly. Devices are named floppy0, ide0, sata0 and so on; partitions append p1, p2.

Storage software layers The VFS and format tools use a block-device registry, which dispatches to the floppy, ATA PIO or AHCI driver, then to the physical disk. VFS · FAT · format files, not sectors blkdev registry sector read / write + geometry driver FDC · ATA · AHCI floppy.img CHS + ISA DMA ide0 / ide0pN PIO, legacy or native BARs sata0 / sata0pN AHCI port index
One narrow waist. Filesystems and tools only see struct blk_dev. The floppy still needs IRQ 6, but ATA and AHCI are polled; a FAT operation takes sys_fs_busy so the scheduler does not switch away mid-transfer.

Floppy

disk.c drives the 8272-compatible FDC through ISA DMA channel 2, with the single-sector DMA buffer at 0x4000. Retries handle the usual real-hardware flakiness. The second floppy slot can hold root.img.

PATA

ata.c uses the legacy command block or the PCI IDE interface's native BARs. Multi-sector PIO waits for DRQ before every sector because drives drop it between sectors; it polls the command-block status rather than the alternate-status BAR, and falls back to single-sector commands when a bridge leaves DRQ pending.

SATA/AHCI

ahci.c drives the first AHCI controller only, with no IRQs and no NCQ. It does COMRESET, IDENTIFY through the shared ata_identify_parse(), and READ/WRITE DMA EXT through a page-allocated bounce buffer. A disk added after boot needs a rescan; there is no COMRESET hotplug.

USB stack

usb.c is controller-agnostic. It handles enumeration, descriptor parsing, hub recursion, bus scans, per-controller addresses, the hotplug watcher and interrupt-IN consumers. Each host controller implements the usb_hcd_ops vtable in usb_hcd.h.

USB controller topology EHCI handles high-speed root ports, UHCI and OHCI handle low and full speed devices, xHCI handles USB2 root ports. All feed the same USB core and HID layer. EHCI high-speed root ports UHCI full/low speed · 1 instance OHCI full/low speed · up to 4 xHCI USB2 root ports only usb core enumeration · hubs · hotplug · interrupt-IN slots usbhid · keyboard + mouse
Companions are not optional. EHCI is scanned first so its port resets can hand non-high-speed devices back to a companion. There is no transaction translator: a low/full-speed device behind a high-speed hub is invisible to EHCI.
ControllerTransportInstancesImplementation notes
UHCIPCI I/O ports1Frame list at 0x3000; control QH plus one QH per interrupt slot.
OHCIPCI MMIOup to 4HCCA from the page allocator, static ED/TD sets, TDs start at CC = NotAccessed.
EHCIPCI MMIOup to 4Async QH/qTD schedule, page-allocated descriptors, polling only, no periodic list.
xHCIPCI MMIO—USB2 root ports only; USB3 SuperSpeed devices are not handled. Halts and waits for HCH around HCRST; EP0 max packet comes from the port speed; EP0 stages are encoded as one TD per stage (EDK2 style) because chained control TDs stall on Braswell.

Hubs are class-9 devices: usb.c sets their configuration, powers every downstream port (honouring bPwrOn2PwrGood), resets and waits for PORT_ENABLE, then enumerates recursively. This is what makes the X201's internal PCH hubs work. Hotplug watches root ports; a device behind a hub is only found when a full scan runs (lsusb also bumps the USB generation so usbhid re-attaches).

Input

usbhid.c gives every HID class-3 interface with an interrupt-IN endpoint one of the six USB interrupt slots. Boot interfaces (subclass 1, protocol 1/2) are used as-is; other class-3 interfaces are classified by reading their HID report descriptor. Composite receivers and several devices can coexist; mouse reports from all slots are merged.

mouseinfo shows the active backend and whether a USB keyboard is attached. Headless regression tests inject mouse motion and keys through QMP and verify the result with screen dumps.

I2C touchpad

The HP Chromebook 11 G5 EE has no PS/2 port: its Elan touchpad is a HID-over-I2C device on LPSS I2C6. The LPSS I2C functions are hidden from PCI in ACPI mode, so touchpad.c scans the two firmware BAR windows for a DesignWare component and i2c.c drives that controller in fast mode, polled and without interrupts.

Serial

serial.c drives the 16550 at COM1, 115200 8N1, with an IRQ-driven receive ring buffer. It is used for the boot trace, the netlog mirror source, the dbg monitor and the KXE2 kexec receiver.

The transmitter is polled, so a machine without a serial port still boots normally. serial_puthex and serial_putdec are the structured dump helpers used by drivers.

Sensors, power & thermals

sensors prints DTS values on the 90/100/125 °C scales, board sensors and both EC types; powerinfo prints the source (thinkpad or chrome ec), the AC adapter, battery model/manufacturer/serial, capacities, voltage, rate and cycle count through SYS_POWER_INFO; power prints ratios, effective MHz and C-state hints. The WM top bar shows the AC adapter state and the first present battery with a valid percentage next to the CPU temperature on both ThinkPads and Chromebooks; machines without an EC show neither.

Wall clock (RTC)

rtc.c talks to the MC146818-compatible CMOS clock through ports 0x70/0x71. Reads honour the register-B BCD/binary and 12/24-hour modes, retry when the update-in-progress bit is set, and decode the hour's PM flag. The RTC only stores a two-digit year, so the kernel expands it over a 1970–2069 window (70–99 → 1900s, 00–69 → 2000s); a board whose dead battery left 1980 or 1990 therefore reads correctly instead of being pushed a century forward. Writes validate the calendar (leap years included), raise the register-B SET bit, preserve the mode bits and write the computed weekday. On ACPI machines the FADT century register (offset 108, normally CMOS 0x32) is written as well, so the firmware and other operating systems see the intended century; boards without ACPI get no arbitrary NVRAM write.

SYS_RTC_GET/SYS_RTC_SET (104/105) expose the full struct sys_datetime; the older SYS_RTC_HMS/SYS_RTC_DATETIME calls remain the small read-only views. The WM’s top-bar date/time is a click target that opens bin/settime; its Sync NTP button fetches UTC through SYS_NTP_SYNC (106), backed by the SNTP client in ntp.c, and writes it with SYS_RTC_SET. The date command prints the same clock in the classic Linux format.

Panic screen

On a ring-0 fault, panic.c draws straight into the framebuffer — bypassing the shadow buffer and the WM — and mirrors the same data to COM1 before halting. The banner includes the vector and error code, GPRs, control registers, current pid/name, uptime, instruction bytes and stack return-address candidates in the kernel image.

Faults from ring 3 do not halt: the process is killed with a short message in its terminal and serial log. There is no interactive debugger on screen; the dbg kernel command drives a serial monitor instead.

Limits

Source map