STRUCT VDEC_H264_SLICE_INFO_EXT(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

struct vdec_h264_slice_info_ext β€” okay so this is the extended decode info, and bestie, it's literally the shared data between host and firmware 🫢 like they're passing notes in class, except the notes are decode info, no cap.


✨ SYNOPSIS ✨

struct vdec_h264_slice_info_ext {
    u64 wdma_end_addr_offset;
    u16 nal_info;
    u16 timeout;
    u32 reserved;
    u64 vdec_fb_va;
    u32 crc[8];
 };

Look at that struct, it's giving organized queen energy πŸ‘‘ every field exactly where it belongs, not a single byte out of place, periodt.


πŸŽ€ Members πŸŽ€

  • wdma_end_addr_offset β€” the offset from the buffer start. That's it, that's the whole vibe. She's a distance from where the buffer begins πŸ’«
  • nal_info β€” the nal info of the current picture πŸ–ΌοΈ literally just telling you what this picture's working with.
  • timeout β€” toggles whether a decode operation is a timeout ⏰ highkey important, lowkey tiny. She's a switch, she flips, she decides.
  • reserved β€” reserved πŸ™ˆ don't touch her, she's just sitting there being reserved, main character energy of doing nothing at all.
  • vdec_fb_va β€” the vdec frame buffer struct virtual address πŸ“ where the frame buffer struct lives, like a little address label but for structs.
  • crc β€” displays the hardware status πŸ”₯ she's the one showing you what the hardware's actually up to, an array of 8 doing the lord's work.

🌈 SEE ALSO 🌈

Kernel file, and I need you to read that path exactly how it's written, no typos, she's picky:

./drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_h264_req_multi_if.c

And the whole friend group πŸ¦‹ all of these are connected, iykyk:

  • enum vdec_h264_core_dec_err_type(9)
  • struct vdec_h264_slice_lat_dec_param(9)
  • struct vdec_h264_slice_info(9)
  • struct vdec_h264_slice_vsi(9)
  • struct vdec_h264_slice_share_info(9)
  • struct vdec_h264_slice_fb(9)
  • struct vdec_h264_slice_vsi_ext(9)
  • struct vdec_h264_slice_inst(9)

πŸ’€ quick vibe check: I'm not adding anything extra here, because everything above is literally everything the page says. If you want the deeper lore, go read those SEE ALSO structs, they're the source, fr fr.

And that's the whole page, bestie! πŸ“ This one came from ./drivers/media/platform/media... and the date on it is October 2026 β€” so yeah, she's a little futuristic, a little mysterious, and fully iconic βœ¨πŸ’œ Thanks for reading, mwah! 🧚

πŸ“¦ where this page comes from