IRFRAME(4)

✨ NAME ✨

okay bestie, meet irframe — the IrDA frame level driver 💖 this one lives in section 4 of the Kernel Interfaces Manual, and yes we folded the manual name in right here so it can have main character energy 🫶

---

💅 SYNOPSIS 💅

irframe* at oboe?
irframe* at udsir?
irframe* at uirda?
irframe* at ustir?
pseudo-device irframetty

#include <dev/irdaio.h>

---

🦋 DESCRIPTION 🦋

The irframe driver provides support for IrDA frame level transmission. It does not contain the IrDA protocol stack per se, but the stack can be built on top of the irframe driver. Literally that’s the whole vibe: frame level support, not the full stack, bestie 💅

Access to frames is via the read(2) and write(2) system calls. Each write constitutes one frame, and each read yields one frame. The poll(2) system call can be used to check for availability of frames. There are also a number of ioctl(2) calls to manipulate the device, and they are iconic:

• IRDA_RESET_PARAMS — reset the parameters set by IRDA_SET_PARAMS 💖
• IRDA_SET_PARAMS (struct irda_params) — set the speed, extra beginning of frame bytes, and maximum frame size ✨
• IRDA_GET_SPEEDMASK (int) — get the set of allowable speeds 🏎️
• IRDA_GET_TURNAROUNDMASK (int) — get the set of allowable turn around times 🔁

---

🌈 SEE ALSO 🌈

go check these besties, no cap:

• cir(4)
• irframetty(4)
• oboe(4)
• uirda(4)
• ustir(4)
• comms/birda package

---

🎀 HISTORY 🎀

The irframe driver appeared in NetBSD 1.6. periodt 🫶

---

okay that’s the whole page, sourced from Debian and dated December 2, 2001 — bye bestie, slay your IrDA frames 💅🫶