BUS_READ_IVAR(9)

💅 BUS_READ_IVAR(9) 💅

okay bestie, welcome to the Kernel Developer's Manual — this page is all about BUS_READ_IVAR(9) and BUS_WRITE_IVAR(9), the two methods for handling bus-specific device instance variables ✨

🎀 NAME 🎀

BUS_READ_IVAR, BUS_WRITE_IVAR — manipulate bus-specific device instance variables, periodt 💅

✨ SYNOPSIS ✨

First, include these, no cap:

#include <sys/param.h>
#include <sys/bus.h>

Then the function signatures, literally:

int
BUS_READ_IVAR(device_t dev, device_t child, int index,
    uintptr_t *result);

int
BUS_WRITE_IVAR(device_t dev, device_t child, int index,
    uintptr_t value);

💖 DESCRIPTION 💖

These two methods manage a bus specific set of instance variables of a child device, and that's the whole vibe 🫶

The intention is that each different type of bus defines a set of appropriate instance variables — such as ports and irqs for ISA bus etc. — because every bus has its own little personality, iykyk.

This information could be given to the child device as a struct, but that makes it hard for a bus to add or remove variables without forcing an edit and recompile for all drivers, which may not be possible for vendor supplied binary drivers 😭. So yeah, these methods are the move.

⭐ RETURN VALUES ⭐

Zero is returned on success. Otherwise, an appropriate error is returned. That's it, bestie 💅

🦋 SEE ALSO 🦋

• device(9)
• driver(9)

🌸 AUTHORS 🌸

This manual page was written by Doug Rabson. iconic behavior, honestly 💖

---

okay that's the whole page! made with 💜 — source/version: Debian, date: June 16, 1998. bye bestie, go read some ivars 🎀✨