DRM_TEGRA_SU..._GATHER_UPTR(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

DRM_TEGRA_SUBMIT_CMD_GATHER_UPTR β€” bestie, this one executes Host1x opcodes straight from a user pointer, no cap ✨

So this manpage came out of the Kernel API Manual, and it's all about that one iconic constant πŸŽ€


✨ SYNOPSIS ✨

DRM_TEGRA_SUBMIT_CMD_GATHER_UPTR

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so picture this: you've got words words of Host1x opcodes, right? And they're chillin' in the gather_data_ptr buffer πŸ’– This command goes and executes them. That's the whole vibe.

She's lowkey consistent too β€” every single GATHER_UPTR command just uses successive words from the buffer, one after another, like a lil conga line of opcodes 🫢


🌸 SEE ALSO 🌸

Living in the kernel file ./include/uapi/drm/tegra_drm.h, and honestly the whole friend group is here πŸ‘‘

  • struct drm_tegra_gem_create(9)
  • struct drm_tegra_gem_mmap(9)
  • struct drm_tegra_syncpt_read(9)
  • struct drm_tegra_syncpt_incr(9)
  • struct drm_tegra_syncpt_wait(9)
  • struct drm_tegra_open_channel(9)
  • struct drm_tegra_close_channel(9)
  • struct drm_tegra_get_syncpt(9)
  • struct drm_tegra_get_syncpt_base(9)
  • struct drm_tegra_syncpt(9)
  • struct drm_tegra_cmdbuf(9)
  • struct drm_tegra_reloc(9)
  • struct drm_tegra_waitchk(9)
  • struct drm_tegra_submit(9)
  • struct drm_tegra_gem_set_tiling(9)
  • struct drm_tegra_gem_get_tiling(9)
  • struct drm_tegra_gem_set_flags(9)
  • struct drm_tegra_gem_get_flags(9)
  • DRM_TEGRA_SUBMIT_RELOC_SECTOR_LAYOUT(9)
  • DRM_TEGRA_SUBMIT_CMD_WAIT_SYNCPT(9)
  • DRM_TEGRA_SUBMIT_CMD_WAIT_SYNCPT_RELATIVE(9)

πŸ’€ like, that's the entire squad. go say hi. iykyk πŸ’œ

kay that's the whole page bestie, love u, mwah πŸŽ€ β€” brought to you by ./include/uapi/drm, dated October 2026, and filed under DRM_TEGRA_SU..._GATHER_UPTR(9) β­πŸŒˆπŸ’–

πŸ“¦ where this page comes from