drm_mode_getfb2_ioctl(9)
π drm_mode_getfb2_ioctl π
okay bestie, we're in the Kernel API Manual for drm_mode_getfb2_ioctl(9), and this page is literally all about getting the extended FB info. slay. π
πΈ NAME πΈ
drm_mode_getfb2_ioctl β get extended FB info. that's the whole vibe, no cap.
β¨ SYNOPSIS β¨
int drm_mode_getfb2_ioctl (struct drm_device *dev , void *data , struct
drm_file *file_priv );
π§ ARGUMENTS π§
devβ the drm device for the ioctl. like, the device this call is happening on, periodt.dataβ the data pointer for the ioctl. this is where the ioctl's data lives, bestie.file_privβ the drm file for the ioctl call. the file tying this call to the caller, iykyk.
π¦ DESCRIPTION π¦
so the actual job: lookup the FB given its ID and return info about it. easy, iconic, no drama. β¨
and yeah, it's called by the user via ioctl. that's the whole entrance. π«Ά
π RETURN π
Zero on success, negative errno on failure. that's it: 0 = slay, negative errno = π.
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/drm_framebuffer.cβoverview(9) drm_mode_addfb(9)drm_mode_addfb2(9)drm_mode_rmfb(9)drm_mode_getfb(9)drm_mode_dirtyfb_ioctl(9)drm_fb_release(9)drm_framebuffer_init(9)drm_framebuffer_lookup(9)drm_framebuffer_unregister_private(9)drm_framebuffer_cleanup(9)drm_framebuffer_remove(9)
mwah π this cutie lives under ./drivers/gpu/drm, it's dated October 2026, and it's still drm_mode_getfb2_ioctl(9) β bye bestie π«Ά
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms