STRUCT H264_FB(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct h264_fb(9) β€” h264 decode frame buffer information πŸ’–

okay bestie, gather round, because this one is a kernel API manual page (yes, (9) section, we're in the big leagues now) and it's literally just a struct that holds the frame buffer info for h264 decoding. that's the whole vibe. no cap. πŸŽ€


✨ SYNOPSIS ✨

struct h264_fb {
    u64 vdec_fb_va;
    u64 y_fb_dma;
    u64 c_fb_dma;
    s32 poc;
    u32 reserved;
 };

look at her. five members. impeccable alignment. she ate. πŸ’…


🌸 Members 🌸

here's the breakdown, one member at a time, because we respect each of them individually:

  • vdec_fb_va β€” virtual address of struct vdec_fb. yeah, she's a VA, she's virtual, she's living her best life in address space.
  • y_fb_dma β€” dma address of the Y frame buffer (luma). that's the brightness girlies πŸ’‘
  • c_fb_dma β€” dma address of the C frame buffer (chroma). the colour girlies 🌈
  • poc β€” picture order count of frame buffer. literally the frame's place in line, its whole timeline moment, main character energy.
  • reserved β€” for 8 bytes alignment 🫢 it's not doing much but it's doing it perfectly. padding icon.
fr fr do not touch reserved. it's there for 8 bytes alignment and that's its entire personality. respect it.

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file:

./drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_h264_req_common.h

and the whole friend group, all of them, linked and everything:

like okay, squad goals, the h264 crew showed up. πŸ”₯πŸ‘‘


and that's the page bestie, that's the whole thing, no notes πŸ’œ β€” this one came straight out of ./drivers/media/platform/media... and it's dated October 2026, and if you need me i'll be right here, page struct h264_fb(9) forever and always ✨🧚

πŸ“¦ where this page comes from