drm_gem_fb_get_obj(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– drm_gem_fb_get_obj(9) β€” get the GEM object that's backing your framebuffer πŸ’–

okay so bestie, this is a page from the Kernel API Manual, and it's about one tiny little helper that's lowkey doing main character work behind the scenes. πŸŽ€


✨ NAME ✨

drm_gem_fb_get_obj β€” get the GEM object backing the framebuffer πŸ¦‹


🌸 SYNOPSIS 🌸

struct drm_gem_object * drm_gem_fb_get_obj (struct drm_framebuffer *fb ,
       unsigned int plane );

like, you hand it a framebuffer and a plane index, and it hands you back the pointer. simple as that, no cap. ✨


πŸ’… ARGUMENTS πŸ’…

  • fb β€” the framebuffer. yeah. that one. πŸ–ΌοΈ
  • plane β€” the plane index. which plane are we talking about, bestie? 🌈

🫢 DESCRIPTION 🫢

okay so here's the thing that actually matters: this function does not take any additional reference beyond the one that the drm_frambuffer already holds. πŸ’€ like, it does not bump the refcount for you. the framebuffer's already holding that reference, so you're just borrowing the pointer. no extra credit, no extra ref, periodt.


⭐ RETURN ⭐

it gives you back a pointer to drm_gem_object for the given framebuffer and plane index β€” or NULL if it does not exist. πŸ™ˆ so yeah, check for the NULL, bestie, it's giving "might not be there" energy.


🧚 SEE ALSO 🧚

the whole friend group, honestly πŸ‘‘:


ngl this one's short but it ate. know your refcounts, know your planes, and always check for NULL. πŸ’–

🌸 that's the whole vibe, bestie β€” brought to you by ./drivers/gpu/drm, October 2026, and this lil' drm_gem_fb_get_obj(9) moment. slay, bye! πŸ’…βœ¨

πŸ“¦ where this page comes from