STRUCT DRM_VC4_MMAP_BO(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

okok so this page is struct drm_vc4_mmap_bo(9) β€” and it lives in the Kernel API Manual, bestie. It's the ioctl argument for mapping VC4 BOs. that's the whole vibe. πŸŽ€


✨ SYNOPSIS ✨

here's the struct, literally exactly as it is, no notes:

struct drm_vc4_mmap_bo {
    __u32 handle;
    __u32 flags;
    __u64 offset;
 };

🫢 Members 🫢

the members are right there in the struct above, babe β€” handle, flags, offset. iykyk. πŸ‘‘


🌸 DESCRIPTION 🌸

okay so this is the part where i need you to listen, because it's a little bit of a plot twist: this does not actually perform an mmap. nope. not even a little. πŸ™ˆ

what it does instead is return the offset you need to use in an mmap on the DRM device node. that's it. that's the whole job. and the reason that slaps is that it means tools like valgrind end up knowing about the mapped memory. main character behaviour fr fr. πŸ’€βœ¨

and about flags β€” there are currently no values for the flags argument, but it may be used in a future extension. so like, it's reserved. sitting there. being mysterious. we respect it. πŸ¦‹


πŸ”₯ SEE ALSO πŸ”₯

  • Kernel file ./include/uapi/drm/vc4_drm.h
  • struct drm_vc4_submit_cl(9)
  • struct drm_vc4_wait_seqno(9)
  • struct drm_vc4_wait_bo(9)
  • struct drm_vc4_create_bo(9)
  • struct drm_vc4_create_shader_bo(9)
  • struct drm_vc4_label_bo(9)

go read them, they're all iconic in their own way πŸ’œ


ngl if you got here looking for an actual mmap call, this isn't it β€” go use that offset on the DRM device node like the description said. periodt. πŸ’…

okay that's the whole page, bestie!! πŸ“ it came from ./include/uapi/drm, dated October 2026, and it's filed under struct drm_vc4_mmap_bo(9) β€” mwah, love that for us πŸŒˆβ­πŸ’–

πŸ“¦ where this page comes from