drivers.html 42 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660
  1. <!doctype html>
  2. <html lang="en">
  3. <head>
  4. <meta charset="utf-8">
  5. <meta name="viewport" content="width=device-width, initial-scale=1">
  6. <title>Drivers &amp; Buses | NebOS Architecture</title>
  7. <meta name="description" content="NebOS drivers: PCI enumeration, floppy/ATA/AHCI storage, the USB core with UHCI, OHCI, EHCI and xHCI, HID input, USB mass storage, serial, board sensors and the panic path.">
  8. <link rel="icon" href="favicon.svg" type="image/svg+xml">
  9. <link rel="stylesheet" href="style.css">
  10. </head>
  11. <body>
  12. <a class="skip" href="#main">Skip to content</a>
  13. <header class="site-header">
  14. <a class="brand" href="index.html">
  15. <span class="brand-mark" aria-hidden="true"></span>
  16. <span>NebOS <span class="brand-sub">Architecture</span></span>
  17. </a>
  18. <nav class="site-nav" aria-label="Architecture sections">
  19. <a href="index.html">Overview</a>
  20. <a href="boot.html">Boot</a>
  21. <a href="memory.html">Memory</a>
  22. <a href="cpu.html">CPU</a>
  23. <a href="drivers.html" aria-current="page">Drivers</a>
  24. <a href="filesystems.html">Filesystems</a>
  25. <a href="graphics.html">Graphics</a>
  26. <a href="network.html">Network</a>
  27. <a href="userland.html">Userland</a>
  28. <a href="development.html">Development</a>
  29. </nav>
  30. </header>
  31. <main id="main" class="page">
  32. <div class="page-head">
  33. <p class="kicker">Drivers &amp; buses</p>
  34. <h1>Polled hardware, one vtable per bus.</h1>
  35. <p class="lede">
  36. Most NebOS drivers are polled rather than interrupt-driven: storage,
  37. USB and every NIC are serviced from process context. That trades
  38. latency and CPU time for simple, single-owner state and a kernel that
  39. stays easy to reason about on old hardware.
  40. </p>
  41. <div class="meta">
  42. <span class="pill">PCI enumeration</span>
  43. <span class="pill">FDC · PATA · SATA</span>
  44. <span class="pill">UHCI · OHCI · EHCI · xHCI</span>
  45. <span class="pill">PS/2 · USB · I2C touchpad</span>
  46. </div>
  47. </div>
  48. <nav class="toc" aria-label="On this page">
  49. <h2>On this page</h2>
  50. <ul>
  51. <li><a href="#inventory">Driver inventory</a></li>
  52. <li><a href="#pci">PCI &amp; discovery</a></li>
  53. <li><a href="#storage">Storage</a></li>
  54. <li><a href="#usb">USB stack</a></li>
  55. <li><a href="#wifi">WiFi (Intel 7265D/3165, 6200/6300)</a></li>
  56. <li><a href="#hid">Input</a></li>
  57. <li><a href="#serial">Serial</a></li>
  58. <li><a href="#sensors">Sensors &amp; power</a></li>
  59. <li><a href="#rtc">Wall clock (RTC)</a></li>
  60. <li><a href="#panic">Panic screen</a></li>
  61. <li><a href="#limits">Limits</a></li>
  62. <li><a href="#sources">Source map</a></li>
  63. </ul>
  64. </nav>
  65. <section id="inventory">
  66. <h2>Driver inventory</h2>
  67. <p>
  68. Every driver in the tree is small enough to read in one sitting. The
  69. table below is the quickest way to find the one responsible for a
  70. device.
  71. </p>
  72. <div class="table-wrap">
  73. <table>
  74. <thead>
  75. <tr><th>Subsystem</th><th>Driver</th><th>Bus / access</th><th>Service model</th></tr>
  76. </thead>
  77. <tbody>
  78. <tr><td>Floppy</td><td><span class="file">disk.c</span></td><td>ISA FDC + DMA channel 2</td><td>IRQ 6; FAT operations set <code>sys_fs_busy</code></td></tr>
  79. <tr><td>PATA</td><td><span class="file">ata.c</span></td><td>Legacy ports or PCI native BARs</td><td>Polled PIO, DRQ wait per sector</td></tr>
  80. <tr><td>SATA</td><td><span class="file">ahci.c</span></td><td>PCI AHCI MMIO</td><td>Polled, READ/WRITE DMA EXT</td></tr>
  81. <tr><td>eMMC</td><td><span class="file">sdhci.c</span></td><td>Intel Braswell SDHCI, PCI <code>00:10.0</code> (<code>8086:2294</code>)</td><td>Polled PIO, 1-bit/25 MHz; no DMA/IRQ</td></tr>
  82. <tr><td>USB</td><td><span class="file">usb.c</span> + <span class="file">uhci.c</span> <span class="file">ohci.c</span> <span class="file">ehci.c</span> <span class="file">xhci.c</span></td><td>PCI I/O ports or MMIO</td><td>Polled; hotplug watcher in the WM loop</td></tr>
  83. <tr><td>Network</td><td><span class="file">e1000e.c</span> <span class="file">r8168.c</span> <span class="file">ne2000.c</span> <span class="file">asix.c</span> <span class="file">rndis.c</span></td><td>PCI or USB</td><td>Polled, one active receiver</td></tr>
  84. <tr><td>WiFi</td><td><span class="file">iwl_trans.c</span> <span class="file">iwl_mvm.c</span> <span class="file">iwl_dvm.c</span> <span class="file">wifi.c</span></td><td>PCIe, Intel 7265D/3165 (<code>8086:095a/095b/3165/3166</code>) and 6200/6300 (<code>8086:4239/422c</code>, <code>4238/422b</code>)</td><td>Polled RX ring; firmware from <code>/ramfs/firmware</code>, loaded on first use</td></tr>
  85. <tr><td>PS/2</td><td><span class="file">mouse.c</span>, <span class="file">io.c</span></td><td>i8042</td><td>IRQ 1 keyboard, IRQ 12 mouse; polling fallback</td></tr>
  86. <tr><td>Touchpad</td><td><span class="file">i2c.c</span>, <span class="file">touchpad.c</span>, <span class="file">touchpad_gesture.c</span></td><td>LPSS DesignWare I2C, slave <code>0x15</code></td><td>Polled input register every 25 ms; software tap and two-finger scroll gestures; no GPIO interrupt driver</td></tr>
  87. <tr><td>Serial</td><td><span class="file">serial.c</span></td><td>16550 UART, COM1</td><td>IRQ 4 ring buffer + polled transmitter</td></tr>
  88. <tr><td>Thermal</td><td><span class="file">thermal.c</span></td><td>Intel DTS MSR</td><td>Sampled once a second from the scheduler tick</td></tr>
  89. <tr><td>Board sensors / EC</td><td><span class="file">it87.c</span>, <span class="file">tpec.c</span>, <span class="file">ec.c</span>, <span class="file">cros_ec.c</span></td><td>Super I/O, ThinkPad H8 EC, Chrome OS EC (temps, fans, battery, AC, switches)</td><td>Polled; EC battery-index/FIFO/page-selector writes only</td></tr>
  90. <tr><td>Wall clock</td><td><span class="file">rtc.c</span></td><td>CMOS RTC ports <code>0x70/0x71</code></td><td>Read/write under the BKL; update-cycle retries and a 1970–2069 two-digit year window</td></tr>
  91. </tbody>
  92. </table>
  93. </div>
  94. </section>
  95. <section id="pci">
  96. <h2>PCI &amp; discovery</h2>
  97. <p>
  98. <span class="file">pci.c</span> walks bus/device/function and exposes
  99. BAR and capability access. The USB scan checks all functions: real
  100. PIIX3/PIIX4/VIA layouts put the USB function at 0:07.2 or 0:01.2, not
  101. 0:07.0. Controllers with unassigned BARs are ignored rather than
  102. driven at address zero.
  103. </p>
  104. <p>
  105. MMIO regions are mapped through <code>paging_map_mmio()</code>. PCI
  106. interrupts are disabled before touching MMIO, so every driver polls
  107. its own status registers. <code>lspci</code> lists every function;
  108. with a filter it prints BAR type, size and address details.
  109. </p>
  110. </section>
  111. <section id="storage">
  112. <h2>Storage</h2>
  113. <p>
  114. <span class="file">blkdev.c</span> is a small registry of block
  115. devices. Each device exposes sector read/write plus geometry; FAT,
  116. the format command and the installer sit above that interface and
  117. never talk to a controller directly. Devices are named
  118. <code>floppy0</code>, <code>ide0</code>, <code>sata0</code>,
  119. <code>mmc0</code>, <code>usb0</code> and so on; partitions append
  120. <code>p1</code>, <code>p2</code>.
  121. </p>
  122. <figure class="figure">
  123. <svg viewBox="0 0 920 246" role="img" aria-labelledby="storage-title storage-desc">
  124. <title id="storage-title">Storage software layers</title>
  125. <desc id="storage-desc">The VFS, format and install tools use a block-device registry, which dispatches to the floppy, ATA PIO, AHCI, SDHCI or USB mass-storage driver, then to the physical disk.</desc>
  126. <rect class="svg-box blue" x="40" y="30" width="230" height="62" rx="9"/>
  127. <text class="svg-text" x="60" y="57">VFS · FAT · format · install</text>
  128. <text class="svg-sub" x="60" y="77">files, or a whole-image clone</text>
  129. <rect class="svg-box accent" x="345" y="30" width="230" height="62" rx="9"/>
  130. <text class="svg-text" x="365" y="57">blkdev registry</text>
  131. <text class="svg-sub" x="365" y="77">sector read / write + geometry</text>
  132. <rect class="svg-box" x="650" y="30" width="230" height="62" rx="9"/>
  133. <text class="svg-text" x="670" y="57">driver</text>
  134. <text class="svg-sub" x="670" y="77">FDC · ATA · AHCI · SDHCI · USB</text>
  135. <path class="svg-line blue" d="M270 61h67"/>
  136. <path class="svg-line blue" d="M330 55l7 6-7 6"/>
  137. <path class="svg-line accent" d="M575 61h67"/>
  138. <path class="svg-line accent" d="M635 55l7 6-7 6"/>
  139. <rect class="svg-box green" x="40" y="142" width="230" height="62" rx="9"/>
  140. <text class="svg-text" x="60" y="169">floppy.img</text>
  141. <text class="svg-sub" x="60" y="189">CHS + ISA DMA</text>
  142. <rect class="svg-box green" x="345" y="142" width="230" height="62" rx="9"/>
  143. <text class="svg-text" x="365" y="169">ide0 / ide0pN</text>
  144. <text class="svg-sub" x="365" y="189">PIO, legacy or native BARs</text>
  145. <rect class="svg-box green" x="650" y="142" width="230" height="62" rx="9"/>
  146. <text class="svg-text" x="670" y="169">sata0 · mmc0 · usb0</text>
  147. <text class="svg-sub" x="670" y="189">AHCI · SDHCI · USB MSC</text>
  148. <path class="svg-line" d="M175 92v42"/>
  149. <path class="svg-line" d="M169 126l6 7 6-7"/>
  150. <path class="svg-line" d="M460 92v42"/>
  151. <path class="svg-line" d="M454 126l6 7 6-7"/>
  152. <path class="svg-line" d="M765 92v42"/>
  153. <path class="svg-line" d="M759 126l6 7 6-7"/>
  154. </svg>
  155. <figcaption>
  156. <strong>One narrow waist.</strong> Filesystems and tools only see
  157. <code>struct blk_dev</code>. The floppy still needs IRQ 6, but ATA,
  158. AHCI, SDHCI and USB MSC are polled; a FAT operation takes a
  159. non-preemptible section and <code>format_busy</code> keeps a
  160. destructive format/install exclusive. The installer clones the
  161. MBR and every used sector of the source image.
  162. </figcaption>
  163. </figure>
  164. <h3>Floppy</h3>
  165. <p>
  166. <span class="file">disk.c</span> drives the 8272-compatible FDC
  167. through ISA DMA channel 2, with the single-sector DMA buffer at
  168. <code>0x4000</code>. Retries handle the usual real-hardware flakiness.
  169. The second floppy slot can hold <code>root.img</code>.
  170. </p>
  171. <h3>PATA</h3>
  172. <p>
  173. <span class="file">ata.c</span> uses the legacy command block or the
  174. PCI IDE interface's native BARs. Multi-sector PIO waits for DRQ
  175. before every sector because drives drop it between sectors; it polls
  176. the command-block status rather than the alternate-status BAR, and
  177. falls back to single-sector commands when a bridge leaves DRQ pending.
  178. </p>
  179. <h3>SATA/AHCI</h3>
  180. <p>
  181. <span class="file">ahci.c</span> drives the first AHCI controller
  182. only, with no IRQs and no NCQ. It does COMRESET, IDENTIFY through the
  183. shared <code>ata_identify_parse()</code>, and READ/WRITE DMA EXT
  184. through a page-allocated bounce buffer. A disk added after boot needs
  185. a rescan; there is no COMRESET hotplug.
  186. </p>
  187. <h3>eMMC/SDHCI</h3>
  188. <p>
  189. <span class="file">sdhci.c</span> drives the Intel Braswell MMC
  190. function at PCI <code>00:10.0</code> (<code>8086:2294</code>, class
  191. <code>0805</code>), the HP Chromebook's eMMC. It resets the SDHCI
  192. host, selects the 1.8 V rail and Host Control 2's 1.8 V signalling,
  193. runs a 400 kHz initialization clock, then CMD0/1/2/3/7/16 and CMD8
  194. to read EXT_CSD (<code>SEC_COUNT</code> at 212,
  195. <code>CACHE_SIZE</code> at 249), and switches to a 25 MHz data clock.
  196. Sector I/O is CMD17/CMD24 through the polled PIO buffer port at
  197. 1-bit/25 MHz; there is no DMA, IRQ, bus-width/high-speed switch or
  198. hotplug. The read/write loops yield every 32 sectors so a long
  199. format does not starve the window manager. The eMMC appears as
  200. <code>mmc0</code>, and <code>format mmc0</code> writes an MBR + FAT
  201. partition exactly like an IDE/SATA disk. The write path flushes the
  202. card cache with CMD6 <code>FLUSH_CACHE</code> when EXT_CSD reports
  203. one.
  204. </p>
  205. </section>
  206. <section id="usb">
  207. <h2>USB stack</h2>
  208. <p>
  209. <span class="file">usb.c</span> is controller-agnostic. It handles
  210. enumeration, descriptor parsing, hub recursion, bus scans, per-controller
  211. addresses, the hotplug watcher and interrupt-IN consumers. Each host
  212. controller implements the <code>usb_hcd_ops</code> vtable in
  213. <span class="file">usb_hcd.h</span>.
  214. </p>
  215. <figure class="figure">
  216. <svg viewBox="0 0 920 300" role="img" aria-labelledby="usb-title usb-desc">
  217. <title id="usb-title">USB controller topology</title>
  218. <desc id="usb-desc">EHCI handles high-speed root ports, UHCI and OHCI handle low and full speed devices, xHCI handles USB2 and USB3 root ports. All feed the same USB core, which drives HID input and USB mass storage.</desc>
  219. <rect class="svg-box accent" x="30" y="24" width="200" height="64" rx="9"/>
  220. <text class="svg-text" x="50" y="50">EHCI</text>
  221. <text class="svg-sub" x="50" y="70">high-speed root ports</text>
  222. <rect class="svg-box blue" x="252" y="24" width="200" height="64" rx="9"/>
  223. <text class="svg-text" x="272" y="50">UHCI</text>
  224. <text class="svg-sub" x="272" y="70">full/low speed · 1 instance</text>
  225. <rect class="svg-box blue" x="474" y="24" width="200" height="64" rx="9"/>
  226. <text class="svg-text" x="494" y="50">OHCI</text>
  227. <text class="svg-sub" x="494" y="70">full/low speed · up to 4</text>
  228. <rect class="svg-box green" x="696" y="24" width="194" height="64" rx="9"/>
  229. <text class="svg-text" x="716" y="50">xHCI</text>
  230. <text class="svg-sub" x="716" y="70">USB2 + USB3 root ports</text>
  231. <path class="svg-line accent" d="M130 88v40h330v28"/>
  232. <path class="svg-line blue" d="M352 88v68"/>
  233. <path class="svg-line blue" d="M574 88v68"/>
  234. <path class="svg-line green" d="M793 88v40H460v28"/>
  235. <rect class="svg-box" x="300" y="156" width="320" height="58" rx="9"/>
  236. <text class="svg-text" x="320" y="181">usb core</text>
  237. <text class="svg-sub" x="320" y="201">enumeration · hubs · hotplug · interrupt-IN slots</text>
  238. <path class="svg-line" d="M460 214v34"/>
  239. <path class="svg-line" d="M454 240l6 7 6-7"/>
  240. <rect class="svg-box" x="300" y="248" width="320" height="50" rx="9"/>
  241. <text class="svg-text" x="320" y="266">usbhid · keyboard + mouse</text>
  242. <text class="svg-text" x="320" y="286">usbmsc · mass storage</text>
  243. </svg>
  244. <figcaption>
  245. <strong>Companions are not optional.</strong> EHCI is scanned first
  246. so its port resets can hand non-high-speed devices back to a
  247. companion. There is no transaction translator: a low/full-speed
  248. device behind a high-speed hub is invisible to EHCI.
  249. </figcaption>
  250. </figure>
  251. <div class="table-wrap">
  252. <table>
  253. <thead>
  254. <tr><th>Controller</th><th>Transport</th><th>Instances</th><th>Implementation notes</th></tr>
  255. </thead>
  256. <tbody>
  257. <tr><td>UHCI</td><td>PCI I/O ports</td><td>1</td><td>Frame list at <code>0x3000</code>; control QH plus one QH per interrupt slot.</td></tr>
  258. <tr><td>OHCI</td><td>PCI MMIO</td><td>up to 4</td><td>HCCA from the page allocator, static ED/TD sets, TDs start at <code>CC = NotAccessed</code>.</td></tr>
  259. <tr><td>EHCI</td><td>PCI MMIO</td><td>up to 4</td><td>Async QH/qTD schedule, page-allocated descriptors, polling only, no periodic list.</td></tr>
  260. <tr><td>xHCI</td><td>PCI MMIO</td><td>—</td><td>USB2 and USB3 root ports; direct SuperSpeed devices use a 512-byte EP0 and the port speed in the slot context (USB3 hubs are not decoded). Halts and waits for <code>HCH</code> around <code>HCRST</code>; 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.</td></tr>
  261. </tbody>
  262. </table>
  263. </div>
  264. <p>
  265. Hubs are class-9 devices: <code>usb.c</code> sets their configuration,
  266. powers every downstream port (honouring <code>bPwrOn2PwrGood</code>),
  267. resets and waits for <code>PORT_ENABLE</code>, then enumerates
  268. recursively. This is what makes the X201's internal PCH hubs work.
  269. Hotplug watches root ports; a device behind a hub is only found when a
  270. full scan runs (<code>lsusb</code> also bumps the USB generation so
  271. <code>usbhid</code> re-attaches).
  272. </p>
  273. <h3>Mass storage</h3>
  274. <p>
  275. <span class="file">usbmsc.c</span> is a device-level probe alongside
  276. the ASIX Ethernet driver. It claims an interface with class 8,
  277. subclass 6 and protocol 0x50, parses its bulk IN/OUT endpoints and
  278. identifies the disk with SCSI INQUIRY + READ CAPACITY. Commands use
  279. Bulk-Only Transport with LUN 0 and 512-byte blocks: READ(10),
  280. WRITE(10), SYNCHRONIZE CACHE and a BOT reset/endpoint-halt recovery.
  281. Short bulk-IN chunks are accumulated within a BOT data stage; a
  282. failed READ(10) gets REQUEST SENSE, retries and a 1-sector
  283. fallback. Present devices are registered as <code>usb0..</code>
  284. (<code>BLK_USB</code>) by <code>blk_scan()</code>, so
  285. <code>storage</code>, the VFS, <code>format</code> and
  286. <code>install</code> can use them.
  287. </p>
  288. <p>
  289. Bulk transfers exist on EHCI and xHCI only; a mass-storage device on
  290. a UHCI/OHCI companion is left unclaimed. The xHCI driver drives
  291. direct USB3 root-port devices (USB3 hubs are not decoded), so a
  292. SuperSpeed stick on the Chromebook works. This is what makes the
  293. installer's <code>usb0</code> source possible: it reads the whole
  294. live image into RAM first and then writes the target, so slow eMMC
  295. writes cannot leave the USB source idle between chunks.
  296. </p>
  297. <h3>USB tethering</h3>
  298. <p>
  299. <span class="file">rndis.c</span> is another device-level probe. It
  300. scans every configuration for an RNDIS control function
  301. (<code>02/02/FF</code>, <code>E0/01/03</code> or an <code>EF</code>
  302. variant) and a data interface with bulk endpoints, selects that
  303. configuration, then sends RNDIS INIT/QUERY/packet-filter messages
  304. over the control interface. Ethernet frames travel in 44-byte RNDIS
  305. packet headers on the bulk pair, so the existing IPv4 stack sees a
  306. normal netdev named <code>rndis</code>. This is Android USB
  307. tethering, not WiFi; QEMU's full-speed <code>usb-net</code> device is
  308. the test target (<code>make run-rndis</code>). CDC-ECM/NCM and the
  309. RNDIS interrupt notification endpoint are not implemented.
  310. </p>
  311. </section>
  312. <section id="wifi">
  313. <h2>WiFi (Intel 7265D/3165, 6200/6300)</h2>
  314. <p>
  315. Two Intel generations share one PCIe transport. The HP Chromebook's
  316. Wireless-AC 7265 rev D or 3165 runs the newer <em>MVM</em> firmware
  317. (<span class="file">iwl_mvm.c</span>); the ThinkPad X201's Centrino
  318. Advanced-N 6200 (or Ultimate-N 6300) runs the older <em>DVM</em>
  319. firmware (<span class="file">iwl_dvm.c</span>).
  320. <span class="file">iwl_fw.c</span> picks the layer from the PCI
  321. probe, so <span class="file">wifi.c</span> and the
  322. <code>wifi</code> command are the same for both. Everything is
  323. polled; every ring and buffer is page-allocated so nothing big lands
  324. in the kernel BSS.
  325. </p>
  326. <figure class="figure">
  327. <svg viewBox="0 0 920 300" role="img" aria-labelledby="wifi-title wifi-desc">
  328. <title id="wifi-title">WiFi software layers</title>
  329. <desc id="wifi-desc">The ring-3 wifi command runs the WPA2 handshake and talks to wifi.c through SYS_WIFI; the network stack uses wifi.c as a normal netdev. wifi.c uses iwl_mvm.c for firmware commands, which uses the iwl_trans.c PCIe transport to reach the card.</desc>
  330. <rect class="svg-box blue" x="40" y="20" width="400" height="56" rx="9"/>
  331. <text class="svg-text" x="60" y="44">wifi command + wpa.c (ring 3)</text>
  332. <text class="svg-sub" x="60" y="64">scan · PBKDF2 · 4-way / group handshake</text>
  333. <rect class="svg-box blue" x="480" y="20" width="400" height="56" rx="9"/>
  334. <text class="svg-text" x="500" y="44">net stack</text>
  335. <text class="svg-sub" x="500" y="64">DHCP · DNS · TCP via struct netdev</text>
  336. <rect class="svg-box accent" x="40" y="112" width="840" height="50" rx="9"/>
  337. <text class="svg-text" x="60" y="134">wifi.c — 802.11 station + the wifi netdev</text>
  338. <text class="svg-sub" x="60" y="152">auth/assoc · 802.11 ↔ Ethernet (LLC/SNAP, CCMP header) · EAPOL queue · SYS_WIFI</text>
  339. <rect class="svg-box" x="40" y="182" width="840" height="44" rx="9"/>
  340. <text class="svg-text" x="60" y="209">iwl_mvm.c (7265D) · iwl_dvm.c (6200/6300) — firmware commands, via iwl_fw.c</text>
  341. <rect class="svg-box green" x="40" y="246" width="840" height="44" rx="9"/>
  342. <text class="svg-text" x="60" y="273">iwl_trans.c — CSR/PRPH access, TFD + RX rings, firmware section DMA (PCIe)</text>
  343. <path class="svg-line blue" d="M240 76v28"/>
  344. <path class="svg-line blue" d="M234 98l6 7 6-7"/>
  345. <path class="svg-line blue" d="M680 76v28"/>
  346. <path class="svg-line blue" d="M674 98l6 7 6-7"/>
  347. <path class="svg-line" d="M460 162v14"/>
  348. <path class="svg-line" d="M460 226v14"/>
  349. </svg>
  350. <figcaption>
  351. <strong>Keys stay in ring 3 until installed.</strong> The supplicant
  352. derives the PTK and unwraps the GTK; the kernel only moves EAPOL
  353. frames and hands the TK/GTK to the firmware, which does CCMP.
  354. Sources: <span class="file">ucmd_wifi.c</span>,
  355. <span class="file">wpa.c</span>, <span class="file">wifi.c</span>,
  356. <span class="file">iwl_fw.c</span>, <span class="file">iwl_mvm.c</span>,
  357. <span class="file">iwl_dvm.c</span>, <span class="file">iwl_trans.c</span>.
  358. </figcaption>
  359. </figure>
  360. <ul>
  361. <li><strong>Transport.</strong> <span class="file">iwl_trans.c</span> follows Linux iwlwifi for the 7000 family: APM init, one legacy RX queue of 256 × 4 KB RBDs, gen1 128-byte TFDs, byte-count tables in dwords, and the FH service channel loading firmware sections through a 128 KB bounce buffer. The NIC is kept awake (MAC access request held) and interrupts stay masked; PCI INTx is disabled. Host commands use the wide 8-byte header (legacy commands go out as group 1).</li>
  362. <li><strong>Firmware.</strong> <code>iwlwifi-7265D-29.ucode</code> ships in the command pack as <code>firmware/iwlwifi-7265D-29.ucode</code> (1,036,312 bytes). It is a single-CPU image with LMAC scan, DQA queues and the old station API. <span class="file">iwl_mvm.c</span> runs the INIT image (NVM read for the MAC address, calibration, PHY-DB collection), then the runtime image (PHY-DB replay, DQA, aux station, PHY context, CAM power, MCC <code>ZZ</code>, station MAC context).</li>
  363. <li><strong>Queues.</strong> Command queue 0 (FIFO 7), aux queue 1 (scan probes), BSS queue 4 for the AP station (management and data, BE FIFO).</li>
  364. <li><strong>Station.</strong> <span class="file">wifi.c</span> builds open-system authentication and the association request itself, without WMM or HT IEs, so data frames are plain non-QoS 802.11 + LLC/SNAP. Management frames go at 1 Mb/s CCK (6 Mb/s on 5 GHz), data at a fixed 12 Mb/s OFDM (no rate scaling table yet).</li>
  365. <li><strong>Security.</strong> WPA2-PSK with CCMP only. The 4-way and group handshakes run in ring 3 (<span class="file">wpa.c</span>); the kernel queues EAPOL frames and installs the TK/GTK with <code>ADD_STA_KEY</code>. TX uses the firmware's CCMP engine with the key embedded in <code>TX_CMD</code>; the host builds the 8-byte CCMP header and its packet number. On the tested 7265D-29 the firmware does not use the installed keys for RX and reports <code>SEC_ENC_ERR</code>, so RX CCMP is decrypted in software by <span class="file">ccmp.c</span> (AES-CCM, RFC 3610) with the same TK/GTK. There is no software replay window yet.</li>
  366. <li><strong>Bring-up on first use.</strong> The boot probe only finds the PCI function. The firmware is loaded by the first <code>wifi</code> command, so boot time and RAM do not change when WiFi is unused. The netdev reports <code>link_up() = 0</code> until it is connected, so the boot DHCP is skipped.</li>
  367. <li><strong>kexec.</strong> <code>netdev_shutdown()</code> always stops the card through <code>wifi_shutdown()</code>, even when it is not the active netdev, because its RX ring would keep writing into pages the next kernel reuses.</li>
  368. </ul>
  369. <h3>6200/6300: the DVM firmware</h3>
  370. <p>
  371. The transport differences live in one per-family descriptor
  372. (<code>fam_7000</code>/<code>fam_6000</code> in
  373. <span class="file">iwl_trans.c</span>):
  374. </p>
  375. <div class="table-wrap">
  376. <table>
  377. <thead>
  378. <tr><th>Parameter</th><th>7265D/3165 (MVM)</th><th>6200/6300 (DVM)</th></tr>
  379. </thead>
  380. <tbody>
  381. <tr><td>Firmware</td><td><code>iwlwifi-7265D-29.ucode</code> (TLV)</td><td><code>iwlwifi-6000-4.ucode</code> (v2 header: inst/data sections at <code>0x0</code>/<code>0x800000</code>)</td></tr>
  382. <tr><td>Scheduler queues</td><td>31</td><td>20</td></tr>
  383. <tr><td>Command queue / FIFO</td><td>0 / 7</td><td>4 / 7</td></tr>
  384. <tr><td>Data queues</td><td>aux 1, BSS 4 (configured by firmware, <code>SCD_QUEUE_CFG</code>)</td><td>VO 0 (management), VI 1, BE 2 (data), BK 3 (configured by the transport)</td></tr>
  385. <tr><td>Command header</td><td>8-byte wide (group 1)</td><td>4-byte</td></tr>
  386. <tr><td>Byte-count table</td><td>dwords</td><td>bytes</td></tr>
  387. <tr><td>MAC address</td><td>NVM via <code>NVM_ACCESS_CMD</code></td><td>OTP read by the host through <code>CSR_EEPROM_REG</code></td></tr>
  388. </tbody>
  389. </table>
  390. </div>
  391. <ul>
  392. <li><strong>Bring-up.</strong> The host reads the 2 KB OTP (MAC at word 0x15, radio config at 0x48, crystal calibration through the calibration link), writes the radio SKU bits during NIC init, then runs the INIT image: <code>CALIBRATION_CFG_CMD</code> and every <code>CALIBRATION_RES_NOTIFICATION</code> stored by op code until <code>CALIBRATION_COMPLETE</code>. The runtime image gets the stored results back as <code>REPLY_PHY_CALIBRATION_CMD</code>, DC calibration, TX antennas, an RXON, TX power and a CAM power table.</li>
  393. <li><strong>RXON.</strong> DVM has no MAC/PHY contexts: one <code>REPLY_RXON</code> carries channel, BSSID, filters and association. A full RXON first clears the association, which wipes the firmware's station table, so the broadcast station (15) and the AP station (0) are re-added with their fixed-rate <code>LINK_QUALITY</code> tables, and a new TX power command follows every retune.</li>
  394. <li><strong>Scan.</strong> One <code>REPLY_SCAN_CMD</code> per band: 2.4 GHz, then 5 GHz after <code>SCAN_COMPLETE_NOTIFICATION</code>. Only channels the EEPROM regulatory tables mark valid are scanned, and probes are only sent where they are marked active and not radar. A firmware assert makes the next scan or connect reload the firmware instead of failing until reboot.</li>
  395. <li><strong>Keys.</strong> <code>REPLY_ADD_STA</code> in modify mode on the AP station (pairwise offset 0, group offset 1). RX frames are the same <code>RX_PHY</code> + <code>RX_MPDU</code> pair as on the 7265D, so the software CCMP fallback in <span class="file">wifi.c</span> covers both cards. The 6200 transmits on antenna B (its <code>ANT_BC</code> configuration).</li>
  396. </ul>
  397. </section>
  398. <section id="hid">
  399. <h2>Input</h2>
  400. <p>
  401. <span class="file">usbhid.c</span> gives every HID class-3 interface
  402. with an interrupt-IN endpoint one of the six USB interrupt slots. Boot
  403. interfaces (subclass 1, protocol 1/2) are used as-is; other class-3
  404. interfaces are classified by reading their HID report descriptor.
  405. Composite receivers and several devices can coexist; mouse reports
  406. from all slots are merged.
  407. </p>
  408. <ul>
  409. <li><strong>Mouse.</strong> Three-byte boot reports: buttons in <code>b0 &amp; 7</code>, signed <code>dx/dy</code>. HID's +y is flipped to the PS/2 convention.</li>
  410. <li><strong>Keyboard.</strong> Eight-byte boot reports (modifier + six keycodes). Reports are diffed and decoded through a HID-usage → scancode-set-1 table, then injected with <code>io_inject_scancode()</code>.</li>
  411. <li><strong>Repeat.</strong> A boot keyboard only reports changes, so <code>io.c</code> adds software typematic repeat (500 ms delay, 33 ms rate).</li>
  412. <li><strong>PS/2.</strong> The i8042 path shares the cursor and keyboard code; the BIOS legacy USB emulation is disabled because the kernel owns the devices.</li>
  413. </ul>
  414. <p>
  415. <code>mouseinfo</code> shows the active backend and whether a USB
  416. keyboard is attached. Headless regression tests inject mouse motion
  417. and keys through QMP and verify the result with screen dumps.
  418. </p>
  419. <h3>I2C touchpad</h3>
  420. <p>
  421. The HP Chromebook 11 G5 EE has no PS/2 port: its Elan touchpad is a
  422. HID-over-I2C device on LPSS I2C6. The LPSS I2C functions are hidden
  423. from PCI in ACPI mode, so <span class="file">touchpad.c</span> scans
  424. the two firmware BAR windows for a DesignWare component and
  425. <span class="file">i2c.c</span> drives that controller in fast mode,
  426. polled and without interrupts.
  427. </p>
  428. <ul>
  429. <li><strong>Probe.</strong> Slave address <code>0x15</code>: reset
  430. (<code>0x0100</code>), consume the 2-byte acknowledgement, read the
  431. HID descriptor, select absolute mode (<code>0x0300 = 1</code>) and
  432. wake the device (<code>0x0800</code>). Resetting last leaves it
  433. silent until the next power cycle.</li>
  434. <li><strong>Reports.</strong> The Elan vendor report <code>0x5D</code>
  435. carries a finger bitmask and five packed bytes per active finger
  436. (X/Y high bits, X low, Y low, size, pressure). The decoder feeds the
  437. device-independent <span class="file">touchpad_gesture.c</span>
  438. engine; a future PS/2 or USB touchpad backend only has to produce
  439. the same two-contact frame. The native max-X/Y commands
  440. (<code>0x0106</code>/<code>0x0107</code>) give the corner zone a
  441. physical coordinate frame.</li>
  442. <li><strong>Tap gestures.</strong> A short stationary contact is
  443. turned into a synthetic button press: two fingers is a right click,
  444. one finger starting in the bottom-right zone (right 25% x bottom
  445. 25% of the pad) is a right click, and one finger elsewhere is a
  446. left click. The press is held for 120 ms so applications polling
  447. <code>SYS_WIN_POINTER</code> sample it. Taps shorter than two 25 ms
  448. samples, longer than 300 ms, moved more than 60 coordinate units,
  449. or accompanied by a physical clickpad press are ignored.</li>
  450. <li><strong>Physical clickpad.</strong> The single clickpad button
  451. is latched at its leading edge: a press whose finger starts in the
  452. bottom-right zone reports the right button, anywhere else reports
  453. the left button, and the choice holds until the button is released
  454. (so a corner drag stays a right drag).</li>
  455. <li><strong>Two-finger scroll.</strong> With exactly two contacts,
  456. the pointer freezes and the centroid movement accumulates. After
  457. about 30 device units it becomes a scroll and emits movement / 2
  458. in pixels; natural direction (two fingers up = later content) is
  459. the default, and the two-finger right tap is suppressed once the
  460. gesture has scrolled. The pointer re-anchors when one finger
  461. remains. The <code>scroll on|off|natural|traditional</code> option
  462. tunes it.</li>
  463. <li><strong>Polling.</strong> The report GPIO has no driver yet, so
  464. the input register is read every 25 ms. Back-to-back reads stall the
  465. device, which is why the poll is throttled rather than run flat
  466. out.</li>
  467. <li><strong>Discovery and tuning.</strong> <code>touchpad</code>
  468. prints the probe result, max coordinates, last report and synthesized
  469. click counters, and takes <code>rightclick off|tap|corner|both</code>,
  470. <code>tapclick on|off</code> or
  471. <code>scroll on|off|natural|traditional</code>; <code>mouseinfo</code>
  472. lists the Elan vendor/product ID next to the PS/2 and USB backends.</li>
  473. </ul>
  474. </section>
  475. <section id="serial">
  476. <h2>Serial</h2>
  477. <p>
  478. <span class="file">serial.c</span> drives the 16550 at COM1, 115200
  479. 8N1, with an IRQ-driven receive ring buffer. It is used for the boot
  480. trace, the netlog mirror source, the <code>dbg</code> monitor and the
  481. <code>KXE2</code> kexec receiver.
  482. </p>
  483. <p>
  484. The transmitter is polled, so a machine without a serial port still
  485. boots normally. <code>serial_puthex</code> and
  486. <code>serial_putdec</code> are the structured dump helpers used by
  487. drivers.
  488. </p>
  489. </section>
  490. <section id="sensors">
  491. <h2>Sensors, power &amp; thermals</h2>
  492. <ul>
  493. <li><strong>DTS.</strong> <span class="file">thermal.c</span> reads <code>IA32_THERM_STATUS</code> on an allowlist of Core/Core 2, Nehalem/Westmere, Bonnell and Airmont/Braswell models. TjMax comes from <code>IA32_TEMPERATURE_TARGET</code> on Nehalem/Westmere; Airmont uses coretemp's 90 °C table (the kernel does not read the MSR before the IDT exists), and Bonnell uses the table.</li>
  494. <li><strong>IT87xx.</strong> <span class="file">it87.c</span> reads the Super I/O temperatures and fan tachometers on the ASUS AT3IONT-I. Nothing is written to fan control.</li>
  495. <li><strong>ThinkPad EC.</strong> <span class="file">tpec.c</span> is gated on an SMBIOS Lenovo/IBM match and reads temperatures and fan mode through the shared ACPI EC protocol in <span class="file">ec.c</span> (ports <code>0x62/0x66</code>, command <code>0x80</code> read / <code>0x81</code> write, OBF/IBF waits, stale-byte drain, bounded polls). Battery/AC state comes from <code>0x38/0x39</code> (present, charging, discharging), <code>0x46</code> bit 4 (AC online), and the page-selected 16-byte window at <code>0xA0..0xAF</code>; <code>0x81</code> selects the battery and page (0 dynamic, 1 mode, 2 design, 5 manufacturer, 6 model). That page selector is the only EC write, and it is restored when it changed.</li>
  496. <li><strong>Chrome EC.</strong> <span class="file">cros_ec.c</span> probes the Chrome OS EC, gated on the ACPI memory version, the <code>'E','C'</code> memmap id and the device feature bits; it skips the probe when the ThinkPad EC is present. Its ACPI window <code>0x20..0xFF</code> mirrors memmap <code>0x00..0xDF</code>: temperature sensors <code>0x00..0x0f</code>/<code>0x18..0x1f</code> (raw − 73 °C), fans <code>0x10..0x17</code> (<code>0xffff</code> absent), switches <code>0x30</code> (lid/power button), and the battery block <code>0x40..0x7f</code> (AC/present/charging flags at <code>0x4c</code>, voltage/rate/remaining/design/last-full/cycle count, and the 8-byte strings). <code>EC_ACPI_MEM_BATTERY_INDEX</code> <code>0x12</code> selects the battery and waits for <code>BATT_INDEX</code> <code>0x4e</code>; <code>EC_ACPI_MEM_STRINGS_FIFO</code> <code>0x16</code> returns longer strings when supported. The Cyan full-charge workaround is applied, and the units are mAh/mA. <span class="file">power_src.c</span> picks the ThinkPad backend first, then the Chrome EC; <code>SYS_CROS_EC_SENSORS</code> (107) exposes the EC temperature/fan/switch snapshot.</li>
  497. <li><strong>MTRRs.</strong> <span class="file">mtrr.c</span> manages write-combining ranges for the framebuffer and reports the effective mapping.</li>
  498. </ul>
  499. <p>
  500. <code>sensors</code> prints DTS values on the 90/100/125 °C scales,
  501. board sensors and both EC types; <code>powerinfo</code> prints the
  502. source (<code>thinkpad</code> or <code>chrome ec</code>), the AC
  503. adapter, battery model/manufacturer/serial, capacities, voltage,
  504. rate and cycle count through <code>SYS_POWER_INFO</code>;
  505. <code>power</code> prints ratios, effective MHz and C-state hints.
  506. The WM top bar shows the CPU temperature and, on both ThinkPads
  507. and Chromebooks, a status icon at the far right for the first
  508. present battery: a plug while the AC adapter is online, a
  509. level-filled battery on battery, with a percentage tooltip below
  510. the icon on hover. The tooltip is painted after the windows, so
  511. it always stays on top. Machines without an EC show neither.
  512. </p>
  513. </section>
  514. <section id="rtc">
  515. <h2>Wall clock (RTC)</h2>
  516. <p>
  517. <span class="file">rtc.c</span> talks to the MC146818-compatible
  518. CMOS clock through ports <code>0x70/0x71</code>. Reads honour the
  519. register-B BCD/binary and 12/24-hour modes, retry when the
  520. update-in-progress bit is set, and decode the hour's PM flag. The
  521. RTC only stores a two-digit year, so the kernel expands it over a
  522. 1970–2069 window (70–99 → 1900s, 00–69 → 2000s); a board whose
  523. dead battery left 1980 or 1990 therefore reads correctly instead of
  524. being pushed a century forward. Writes validate the calendar (leap
  525. years included), raise the register-B SET bit, preserve the mode
  526. bits and write the computed weekday. On ACPI machines the FADT
  527. century register (offset 108, normally CMOS <code>0x32</code>) is
  528. written as well, so the firmware and other operating systems see
  529. the intended century; boards without ACPI get no arbitrary NVRAM
  530. write.
  531. </p>
  532. <p>
  533. <code>SYS_RTC_GET</code>/<code>SYS_RTC_SET</code> (104/105) expose
  534. the full <code>struct sys_datetime</code>; the older
  535. <code>SYS_RTC_HMS</code>/<code>SYS_RTC_DATETIME</code> calls remain
  536. the small read-only views. The WM’s top-bar date/time is a click
  537. target that opens <code>bin/settime</code>; its <em>Sync NTP</em>
  538. button fetches UTC through <code>SYS_NTP_SYNC</code> (106), backed
  539. by the SNTP client in <span class="file">ntp.c</span>, and writes
  540. it with <code>SYS_RTC_SET</code>. The <code>date</code> command
  541. prints the same clock in the classic Linux format.
  542. </p>
  543. </section>
  544. <section id="panic">
  545. <h2>Panic screen</h2>
  546. <p>
  547. On a ring-0 fault, <span class="file">panic.c</span> draws straight
  548. into the framebuffer — bypassing the shadow buffer and the WM — and
  549. mirrors the same data to COM1 before halting. The banner includes the
  550. vector and error code, GPRs, control registers, current pid/name,
  551. uptime, instruction bytes and stack return-address candidates in the
  552. kernel image.
  553. </p>
  554. <p>
  555. Faults from ring 3 do not halt: the process is killed with a short
  556. message in its terminal and serial log. There is no interactive
  557. debugger on screen; the <code>dbg</code> kernel command drives a
  558. serial monitor instead.
  559. </p>
  560. </section>
  561. <section id="limits">
  562. <h2>Limits</h2>
  563. <ul>
  564. <li><strong>Polling.</strong> USB, storage and network drivers consume CPU time while waiting; there is no IRQ-driven data path outside PS/2, serial and the PIT.</li>
  565. <li><strong>EHCI.</strong> High-speed root ports only; no split transactions for low/full-speed devices behind a high-speed hub.</li>
  566. <li><strong>xHCI.</strong> USB2 and USB3 root ports; direct SuperSpeed devices work, but USB3 hub port-status decoding is not implemented.</li>
  567. <li><strong>HID.</strong> Report IDs are not handled, absolute pointers/tablets are ignored, and there is no wheel support.</li>
  568. <li><strong>AHCI.</strong> First controller only, no hotplug after boot, disks above 2 TB are clamped to 32-bit LBA.</li>
  569. <li><strong>eMMC.</strong> Polled 1-bit/25 MHz PIO; no DMA, IRQ, CMD6 bus-width/high-speed/DDR switch or hotplug. Only the eMMC function is driven; the SDIO/SD functions and SD card reader are not.</li>
  570. <li><strong>Storage serialization.</strong> A FAT/floppy operation sets <code>sys_fs_busy</code> and stalls process switching for its duration; the PIT keeps ticking.</li>
  571. <li><strong>EC.</strong> The Chrome EC path uses the ACPI v2 memmap only: no MEC host-command interface, EC SCI events, charger current/voltage, charging limit or EC firmware version. The ThinkPad H8 path is limited to its page-selected battery window and has no SCI handler. Battery/AC is polled by the WM once a second.</li>
  572. <li><strong>WiFi.</strong> Intel 7265 rev D/3165 (7265D firmware) and 6200/6300 (6000 firmware, written without hardware in the loop); WPA2-PSK/CCMP and open networks, no WPA3/SAE, 802.1X, TKIP or WEP. No roaming, power save, background scan, HT/VHT, aggregation or rate scaling. Group rekeys need the background <code>wifi __keep</code> helper running. RX CCMP falls back to the byte-oriented software AES-CCM path when the firmware rejects the installed keys, so it has no replay window and is CPU-bound at high RX rates.</li>
  573. <li><strong>Suspend.</strong> There is no S0ix/suspend path; package C-states and the EC sleep handshake remain firmware-managed.</li>
  574. </ul>
  575. </section>
  576. <section id="sources">
  577. <h2>Source map</h2>
  578. <ul class="filelist">
  579. <li><code>pci.c</code>, <code>pci.h</code> — enumeration</li>
  580. <li><code>blkdev.c</code> — block registry</li>
  581. <li><code>sdhci.c</code>, <code>sdhci.h</code> — Intel Braswell eMMC</li>
  582. <li><code>disk.c</code> — floppy / DMA</li>
  583. <li><code>ata.c</code>, <code>ahci.c</code> — PATA/SATA</li>
  584. <li><code>usb.c</code>, <code>usb_hcd.h</code> — USB core</li>
  585. <li><code>uhci.c</code>, <code>ohci.c</code>, <code>ehci.c</code>, <code>xhci.c</code></li>
  586. <li><code>usbmsc.c</code>, <code>usbmsc.h</code> — USB BOT/SCSI mass storage</li>
  587. <li><code>rndis.c</code>, <code>rndis.h</code> — USB RNDIS tethering</li>
  588. <li><code>iwl_trans.c</code>, <code>iwl_trans.h</code> — Intel WiFi PCIe transport (7000 and 6000 families)</li>
  589. <li><code>iwl_mvm.c</code>, <code>iwl_mvm.h</code> — 7265D/3165 firmware commands (MVM)</li>
  590. <li><code>iwl_dvm.c</code>, <code>iwl_dvm.h</code> — 6200/6300 firmware commands (DVM)</li>
  591. <li><code>iwl_fw.c</code>, <code>iwl_fw.h</code> — firmware-layer dispatch</li>
  592. <li><code>wifi.c</code>, <code>wifi.h</code> — 802.11 station, <code>wifi</code> netdev, <code>SYS_WIFI</code></li>
  593. <li><code>ccmp.c</code>, <code>ccmp.h</code> — software CCMP RX fallback (AES-CCM)</li>
  594. <li><code>install.c</code> — live-image clone installer</li>
  595. <li><code>usbhid.c</code>, <code>mouse.c</code>, <code>io.c</code> — input</li>
  596. <li><code>i2c.c</code>, <code>i2c.h</code> — DesignWare/LPSS I2C master</li>
  597. <li><code>touchpad.c</code>, <code>touchpad.h</code> — Elan HID-over-I2C touchpad</li>
  598. <li><code>touchpad_gesture.c</code>, <code>touchpad_gesture.h</code> — device-independent contact gestures (tap, right-click zones, scroll)</li>
  599. <li><code>touchpad_gesture_test.c</code> — host test (<code>make test-touchpad</code>)</li>
  600. <li><code>serial.c</code>, <code>serial_ring_buf.c</code></li>
  601. <li><code>thermal.c</code>, <code>it87.c</code>, <code>tpec.c</code>, <code>ec.c</code>, <code>cros_ec.c</code>, <code>power_src.c</code>, <code>mtrr.c</code></li>
  602. <li><code>rtc.c</code> — CMOS wall clock read/write</li>
  603. <li><code>panic.c</code>, <code>timer.S</code> — fatal exceptions</li>
  604. </ul>
  605. </section>
  606. </main>
  607. <footer class="site-footer">
  608. <div class="inner">
  609. <p><strong>NebOS 0.2.0</strong> · Architecture documentation · <a href="index.html">overview</a></p>
  610. <p>Maintain alongside <code>AGENTS.md</code> and the source files listed on each page.</p>
  611. </div>
  612. </footer>
  613. </body>
  614. </html>