docs/ was ten files where a plan, a description, a guide and a bug report all
sat next to each other. It is now architecture/ (what SchOS is), plan/ (what it
will be), guides/ (how to work on it) and history/ (why it is like this), with
an index that states the one rule holding it together: when something is
finished it moves from plan/ to architecture/ and is rewritten as a description
of the thing rather than a record of building it.
A ticked checkbox says the work happened. It does not say what the work
*produced*, and six months later the checkbox is all that is left. The network
stack proved the point: finished, verified end to end, and for a month the only
description of it anywhere was a checkbox four levels of indentation deep.
So roadmap.md went from 534 lines to 181 -- nothing deleted, the done work
graduated. Seven subsystems that were finished and undescribed now have
descriptions: boot, kernel, syscalls, filesystem, networking, graphics, usb,
init. Every one ends with "What it does not do", which is the section that pays;
a document listing only strengths is marketing, and the reader who needs it most
is the one about to trip over a limitation nobody wrote down.
schfs.md still opened with "phases 1 through 3 1/2 are done, phase 4 is next"
long after all five had landed. It is a description now, with the phase record
and the hard-won bugs moved to history/.
Three corrections found on the way, all load-bearing:
* projects/schcom/README.md claimed SCM_RIGHTS was done. There is no
sendmsg/recvmsg in the kernel at all, and an entire GUI plan rested on it.
* The root README said "No TCP/IP" months after the stack landed.
* history/kernel.md sec.7 was marked "in progress" on a problem that process
groups solved.
Also adds plan/1.0.md, which draws a finish line so the open list stops being
infinite, and marks schwm/ and schde/ superseded: in Wayland the compositor is
the window manager, so that split dissolves rather than being abandoned.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VQ7Qx8E1q1M1bbCq8QLHS2
89 lines
3.5 KiB
C
89 lines
3.5 KiB
C
#pragma once
|
|
|
|
// The device model: one list of everything attached, whatever bus found it.
|
|
//
|
|
// Before this there were two registries in kernel/drivers/registry.c -- one
|
|
// array of PCI drivers, one of USB drivers -- and nothing that knew about both.
|
|
// That is fine for binding drivers to hardware, which is all it was for, and
|
|
// useless for the three things wanted next:
|
|
//
|
|
// *Enumeration.* "What is in this machine, and what claimed it" had no
|
|
// answer that covered a USB disk and a PCI display at once. A device manager
|
|
// is exactly that question, so it needs exactly this list.
|
|
//
|
|
// *Classes.* A compositor should ask for "the display" and not care whether
|
|
// that is the VBE framebuffer or virtio-gpu. Without a class, every consumer
|
|
// hardcodes a driver, and adding the second driver means editing the
|
|
// consumers -- which is how a framebuffer address ends up hardcoded in three
|
|
// places, as it once was here.
|
|
//
|
|
// *A boundary for drivers that are not compiled in.* Drivers the user
|
|
// installs (see docs/architecture/devices.md) have to attach somewhere that is not "an
|
|
// array in registry.c", because that array is fixed at link time.
|
|
//
|
|
// The shape is deliberately the one NeXTSTEP/macOS uses rather than Linux's:
|
|
// a device is an object with a class and an ops vtable, and consumers talk to
|
|
// the class. It is *not* a device tree -- there is no parent/child nesting
|
|
// here, only a flat list with a bus tag, because nothing yet needs to walk a
|
|
// hierarchy and a tree that nobody traverses is just a harder list.
|
|
|
|
#define DEV_NAMELEN 24
|
|
|
|
// Which bus found it. This is provenance, not capability -- what the device
|
|
// *does* is its class.
|
|
enum dev_bus {
|
|
DEVBUS_PLATFORM = 0, // found by looking, not by enumerating: PS/2, VBE
|
|
DEVBUS_PCI,
|
|
DEVBUS_USB,
|
|
DEVBUS_NBUS
|
|
};
|
|
|
|
// What it is. A consumer asks for a class and gets whatever is bound.
|
|
enum dev_class {
|
|
DEVCLASS_OTHER = 0,
|
|
DEVCLASS_DISPLAY,
|
|
DEVCLASS_INPUT,
|
|
DEVCLASS_STORAGE,
|
|
DEVCLASS_NET,
|
|
DEVCLASS_BUS, // a controller that finds more devices (xHCI, hubs)
|
|
DEVCLASS_NCLASS
|
|
};
|
|
|
|
struct device {
|
|
char name[DEV_NAMELEN]; // "vga0", "xhci0" -- unique, human-readable
|
|
char desc[48]; // free text for the enumerator
|
|
enum dev_bus bus;
|
|
enum dev_class class;
|
|
|
|
// Where it came from, for the enumerator to print. Zero when not applicable.
|
|
uint16 vendor, product;
|
|
uint8 b, s, f; // PCI bus/slot/func
|
|
|
|
const char *driver; // whatever claimed it, or 0 for unclaimed
|
|
void *ops; // class-specific vtable; see display.h
|
|
void *priv; // the driver's own state
|
|
|
|
int in_use;
|
|
};
|
|
|
|
#define NDEVICE 32
|
|
|
|
// Register a device. Returns it, or 0 if the table is full. The name is made
|
|
// unique by appending an index, so a caller passes "vga" and gets "vga0".
|
|
struct device *device_add(const char *base, enum dev_bus bus,
|
|
enum dev_class class, const char *driver);
|
|
|
|
// Set the human-readable description. Bounded copy into the fixed field, so
|
|
// callers do not each need to know how long it is.
|
|
void device_set_desc(struct device *, const char *);
|
|
|
|
// Walk. Returns 0 past the end; index is dense over registered devices.
|
|
struct device *device_at(int i);
|
|
int device_count(void);
|
|
|
|
// First device of a class with a bound driver, or 0. This is how a consumer
|
|
// finds "the display" without naming a driver.
|
|
struct device *device_find_class(enum dev_class class);
|
|
|
|
const char *dev_bus_name(enum dev_bus);
|
|
const char *dev_class_name(enum dev_class);
|