STRUCT DRM_TEGRA_RELOC(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

struct drm_tegra_reloc(9) β€” Kernel API Manual β€” GEM object relocation structure. yes bestie, that’s the whole NAME situation, and it’s giving β€œthe struct that handles GEM object relocation” energy ✨


✨ SYNOPSIS ✨

okay so here’s the exact struct, no cap:

       struct drm_tegra_reloc {
           struct {
             __u32 handle;
             __u32 offset;
           } cmdbuf;
           struct {
             __u32 handle;
             __u32 offset;
           } target;
           __u32 shift;
           __u32 pad;
        };

πŸŽ€ Members πŸŽ€

  • cmdbuf β€” cmd information πŸ’…
    • cmdbuf.handle β€” Handle to the GEM object containing the command buffer for which to perform this GEM object relocation.
    • cmdbuf.offset β€” Offset, in bytes, into the command buffer at which to insert the relocated address.
  • target β€” relocate target information 🎯
    • target.handle β€” Handle to the GEM object to be relocated.
    • target.offset β€” Offset, in bytes, into the target GEM object at which the relocated data starts.
  • shift β€” The number of bits by which to shift relocated addresses. bit-shifty business, iykyk 🌈
  • pad β€” Structure padding that may be used in the future. Must be 0.
🚨 bestie, pad is structure padding that may be used in the future, and it must be 0. not a suggestion, fr fr πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹


okay that’s the whole page, bestie 🫢 β€” source/version corner: ./include/uapi/drm; date: October 2026; page: struct drm_tegra_reloc(9). periodt ✨

πŸ“¦ where this page comes from