STRUCT H264_RING_FB_LIST(9)

💖 struct h264_ring_fb_list(9) 💖

okay bestie, welcome to the manual page for struct h264_ring_fb_list — literally the ring frame buffer list, and yes it's from the Kernel API Manual and yes it's iconic 🎀

Think of it as the little circular queue that holds your frame buffers. Main character energy, honestly.

✨ SYNOPSIS ✨

struct h264_ring_fb_list {
    struct h264_fb fb_list[H264_MAX_FB_NUM];
    unsigned int read_idx;
    unsigned int write_idx;
    unsigned int count;
    unsigned int reserved;
 };

no cap, that's the whole shape of it 🦋

🌸 Members 🌸

here's the vibe check on every single field, bestie — none of them are getting skipped:

• fb_list — the frame buffer array 💅 it's an array of struct h264_fb, sized H264_MAX_FB_NUM, and it's where the buffers actually live.
• read_idx — the read index 🫶 where you're reading from in the ring.
• write_idx — the write index ✨ where you're writing to in the ring.
• count — buffer count in list 🌈 literally just how many buffers are chilling in there.
• reserved — for 8 bytes alignment 👑 that's its whole job. it exists so things line up. respect it.

ngl read_idx and write_idx are the main characters here — everything else is supporting cast 💀

🦋 SEE ALSO 🦋

• Kernel file: ./drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_h264_if.c
• struct h264_fb(9)
• struct vdec_h264_dec_info(9)
• struct vdec_h264_vsi(9)
• struct vdec_h264_inst(9)

go read all of them, iykyk 📚✨

and that's a wrap, bestie 💜 this one came from ./drivers/media/platform/media..., dated October 2026, and it's the struct h264_ring_fb_list(9) page — slay, periodt 🌟🎀