DRM_IVPU_CA...MEMORY_RANGE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… DRM_IVPU_CA...MEMORY_RANGE(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” yes that's the manual name, we're fancy here ✨ this little page is about the capability flag DRM_IVPU_CAP_DMA_MEMORY_RANGE, and honestly? it's giving "small but mighty" energy πŸ¦‹


🌸 NAME 🌸

DRM_IVPU_CAP_DMA_MEMORY_RANGE β€” and that's literally it, no description attached, the name is the moment, periodt πŸ’… (also yes, the header up top truncates it to DRM_IVPU_CA...MEMORY_RANGE(9) β€” that's just the page title being dramatic and running out of room, the real flag name is the full one πŸŽ€)


✨ SYNOPSIS ✨

DRM_IVPU_CAP_DMA_MEMORY_RANGE

no args, no params, no little asterisks to worry about β€” just the flag, sitting there, iconic, minding its own business πŸ‘‘


πŸ’– DESCRIPTION πŸ’–

so here's the tea, bestie πŸ“: this capability means the driver has the ability to allocate a separate memory range that's accessible by hardware DMA. that's it, that's the whole vibe. separate memory range, hardware DMA can reach it, the driver can set it up. slay πŸ’…

no cap, that's the entire description β€” short, sweet, and it ate πŸ”₯


πŸŽ€ SEE ALSO πŸŽ€

like, go read these too, iykyk 🫢 first up the kernel file itself:

and then the whole friend group of related references, no cap, all of them:

  • DRM_IVPU_CAP_METRIC_STREAMER(9)
  • DRM_IVPU_CAP_MANAGE_CMDQ(9)
  • DRM_IVPU_CAP_BO_CREATE_FROM_USERPTR(9)
  • struct drm_ivpu_param(9)
  • struct drm_ivpu_bo_create(9)
  • struct drm_ivpu_bo_create_from_userptr(9)
  • struct drm_ivpu_bo_info(9)
  • struct drm_ivpu_submit(9)
  • struct drm_ivpu_cmdq_submit(9)
  • struct drm_ivpu_bo_wait(9)
  • struct drm_ivpu_metric_streamer_start(9)
  • struct drm_ivpu_metric_streamer_get_data(9)
  • struct drm_ivpu_cmdq_create(9)
  • struct drm_ivpu_cmdq_destroy(9)
  • struct drm_ivpu_metric_streamer_stop(9)

like a whole squad of (9) pages, we love a linked ecosystem 🌈


lowkey a reminder that the whole SEE ALSO list is required reading if you wanna be a main character in this driver's lore πŸ’€ don't skip it bestie

and that's a wrap!! 🌸 this page lives in ./include/uapi/drm and it's dated October 2026 β€” so yeah, future-coded of it, we stan a forward-thinking manpage πŸ‘‘ bye bestie, go allocate something separate and DMA-accessible πŸ’œπŸ¦‹

πŸ“¦ where this page comes from