DEVCLASS(9)

💖 NAME 💖

okay so bestie, this is the devclass(9) page from the Kernel Developer’s Manual, and <pink>devclass</pink> is literally the object representing a class of devices. main character energy, fr fr ✨

🎀 SYNOPSIS 🎀

typedef struct devclass *devclass_t;

that’s it. no extra flags, no chaos, just the typedef. slay. 💅

🌸 DESCRIPTION 🌸

the <pink>devclass</pink> object has two main jobs in the system, and honestly it ate:

• manage the allocation of unit numbers for device instances
• hold the list of device drivers for a particular bus type

every <pink>devclass</pink> has a name, and no cap: there cannot be two devclasses with the same name. that’s the guarantee that unique unit numbers get allocated to device instances. all instances with the same name are treated as being the same. iykyk 🦋

when no specific unit number is needed, DEVICE_UNIT_ANY is used. simple as that. periodt 💜

🦋 SEE ALSO 🦋

go off and read these besties:

• devclass_add_driver(9)
• devclass_delete_driver(9)
• devclass_find(9)
• devclass_find_driver(9)
• devclass_get_device(9)
• devclass_get_devices(9)
• devclass_get_maxunit(9)
• devclass_get_name(9)
• devclass_get_softc(9)
• device(9)
• driver(9)

👑 AUTHORS 👑

this manual page was written by Doug Rabson. iconic behavior, honestly. 🫶

---

okay byeee: this one’s from Debian, dated June 16, 1998, and it lives as DEVCLASS(9) — mwah 💋✨