WSBELL(9)

✨ WSBELL(9) — the wscons system bell support glow-up ✨

okay so this is the wsbell manual page, from the Kernel Developer's Manual — yes bestie we're in kernel dev territory, buckle up 🎀

---

🌸 NAME 🌸

wsbell, wsbelldevprint — it's giving wscons system bell support 💅 like literally the bell module for wscons, no cap.

---

🦋 SYNOPSIS 🦋

#include <dev/wscons/wsconsio.h>
#include <dev/wscons/wsbellvar.h>

int
wsbelldevprint(void *aux, const char *pnp);

---

💖 DESCRIPTION 💖

So the wsbell module is a whole component of the wscons(9) framework, and its entire personality is keyboard-independent bell support. Iconic. ✨

All of the actual support is provided by the wsbell(4) device driver — and that driver must be a child of the hardware device driver, like that's the vibe check, no exceptions. 💀

And here's the tea: the only hardware device drivers that can provide a wsbell facility are speaker(4) devices. That's it. That's the list. 🫶

---

🎀 DATA TYPES 🎀

Speaker drivers that wanna support wscons bell devices will make use of these data types, periodt:

• struct wsbelldev_attach_args — a structure used to attach the wsbell(4) child device. It's got the following members:
  • void *accesscookie;

like it's a tiny struct but it's the main character of the attach process, lowkey 🔥

---

⭐ FUNCTIONS ⭐

• wsbelldevprint(aux, pnp) — the default wsbell printing routine that gets used by config_found(). (peep autoconf(9) if you need the lore) 💜

---

🌈 AUTOCONFIGURATION 🌈

Hot take incoming: speaker drivers that wanna use the wsbell module must be a parent to the wsbell(4) device, and they gotta provide an attachment interface. no shortcuts bestie ✋

So to actually attach the wsbell(4) device, the speaker driver has to:

1. allocate and populate a wsbelldev_attach_args structure,
2. stick a pointer to the parent's device structure in there as an access cookie 🍪,
3. and then call config_found() to perform the attach (see autoconf(9) for the full rundown).

that's the whole recipe, slay 💅

---

🧚 OPERATION 🧚

When a bell event is received on a wsdisplay(4) device, the system bell is sounded. 🔔

that's it. that's the operation. short and sweet, we love a concise queen 👑

---

🔥 CODE REFERENCES 🔥

• The wscons subsystem lives in the directory sys/dev/wscons. 🗂️
• The wsbell module itself is implemented within the file sys/dev/wscons/wsbell.c.
• ioctl(2) operations are listed in sys/dev/wscons/wsconsio.h.

(and yes, the original really does say "implement" instead of "implemented" in that second bullet — I'm not fixing it, I'm just a girl 🫶)

---

👑 SEE ALSO 👑

ioctl(2), wsbell(4), wscons(4), wskbd(4), autoconf(9), driver(9), intro(9), wscons(9), wsdisplay(9), wskbd(9)

like literally go read all of these, they're all connected, iykyk 🦋

---

ngl the bell module is small but it's doing its little job and we respect it 💖

okay bye bestie — this page dropped with the Debian crew on June 30, 2017, so if you see a date on it, that's why 🌸 stay ringing, mwah 💋