drm_mode_addfb2(9)

💅 drm_mode_addfb2 💅

okay so bestie, welcome to the drm_mode_addfb2(9) page — yeah it's section 9 of the Kernel API Manual, the kernel-internals girlies' home turf. sit down, hydrate, and let's get into it 🫶

---

✨ NAME ✨

drm_mode_addfb2 — add an FB to the graphics configuration 🔥

🦋 SYNOPSIS 🦋

int drm_mode_addfb2 (struct drm_device *dev , void *data , struct
drm_file *file_priv );

that's it. that's the whole signature. she's giving minimal, she's giving efficient, we love her for it 👑

🎀 ARGUMENTS 🎀

• dev — the drm device for the ioctl. your main character device, literally ✨
• data — data pointer for the ioctl. just the pointer, the payload, the vessel 💫
• file_priv — drm file for the ioctl call. your file, your vibe, your private little handle 🌸

🌈 DESCRIPTION 🌈

Add a new FB to the specified CRTC, given a user request with format. yes bestie, an FB — a framebuffer — and she's getting added to the CRTC you asked for, based on the format you requested 🖼️✨

and here's the tea: this is the 2nd version of the addfb ioctl. v2! the glow-up! 🙈 she supports multi-planar framebuffers (plural planes, so fancy) and she uses fourcc codes</> as pixel format specifiers. fourcc! iconic format-specifier behavior, no cap 💅

Called by the user via ioctl. fr fr, that's the entry point — userland knocks, ioctl answers 🚪✨

⭐ RETURN ⭐

Zero on success, negative errno on failure. so: 0 = slay, negative errno = not slay 😭 that's the whole vibe check

👑 SEE ALSO 👑

• Kernel file ./drivers/gpu/drm/drm_framebuffer.c overview(9) — the source of truth, go read her 📖
• drm_mode_addfb(9) — the original, the prequel 🎬
• drm_mode_rmfb(9) — the removal era, we love a clean exit
• drm_mode_getfb(9) — retrieving info, nosy but make it legit
• drm_mode_getfb2_ioctl(9) — the v2 info-getter, matching energy ✨
• drm_mode_dirtyfb_ioctl(9) — dirty in the good way, pixels only 🫧
• drm_fb_release(9) — letting go, healing era 🌱
• drm_framebuffer_init(9) — set her up right
• drm_framebuffer_lookup(9) — find your fave 🔍
• drm_framebuffer_unregister_private(9) — the private era ends
• drm_framebuffer_cleanup(9) — cleaning up, we stan a tidy queen 🧹
• drm_framebuffer_remove(9) — gone, but remembered 💀

---

real talk bestie: ioctl paths are kernel territory, so if something returns a negative errno, that's your signal to actually read it — no guessing, no vibes-only debugging 🙏

okay that's the page!! sourced straight from the kernel tree at ./drivers/gpu/drm 💖 and dated October 2026 — so this manual page is literally from the future, she's ahead of her time, main character energy periodt 👑✨🎀🦋