mtk_vdec_h2...d_start_code(9)

🎀 NAME 🎀

okay so this is mtk_vdec_h264_find_start_code — bestie, it finds the h264 start code using sofeware 💅 (yes that's how it's spelled in the source, we respect the source in this house). It's a page from the Kernel API Manual, and honestly? iconic of it.

---

✨ SYNOPSIS ✨

int mtk_vdec_h264_find_start_code (unsigned char *data , unsigned int
data_sz );

that's the whole vibe. returns an int, takes two args. slay.

---

🌸 ARGUMENTS 🌸

• data — the input buffer address. like, where the bytes actually live, no cap. 🫶
• data_sz — the input buffer size. how much of that buffer we're allowed to look at, periodt.

---

👑 RETURN 👑

it returns the start code position. that's it, that's the whole return value — go find your start code, main character energy only ⭐

lowkey important: it's an int, so treat that position like a real return value and not a vibe check 💀

---

🦋 SEE ALSO 🦋

fr fr, go read the kernel file first, it's giving source of truth:

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

and then the whole friend group of related pages, all of them, no skips:

• struct mtk_h264_dpb_info(9)
• struct h264_fb(9)
• mtk_vdec_h264_get_ref_list(9)
• mtk_vdec_h264_get_ctrl_ptr(9)
• mtk_vdec_h264_fill_dpb_info(9)
• mtk_vdec_h264_copy_sps_params(9)
• mtk_vdec_h264_copy_pps_params(9)
• mtk_vdec_h264_copy_slice_hd_params(9)
• mtk_vdec_h264_copy_scaling_matrix(9)
• mtk_vdec_h264_copy_decode_params(9)
• mtk_vdec_h264_update_dpb(9)
• mtk_vdec_h264_get_mv_buf_size(9)

---

💖 cute sign-off 💖

this drop came from ./drivers/media/platform/media..., dated October 2026, and it's filed under mtk_vdec_h2...d_start_code(9) if you ever need to find it again. mwah 💋 go read your kernel headers bestie, i believe in you 🌈💜