MediaTek Vcodec hardware video encoder backend
The hardware video encoder backend for MediaTek's V4L2 codec subsystem, providing H.264 and VP8 encoding acceleration on MediaTek SoCs. It powers video capture and streaming use cases on Chromebooks and on MediaTek Genio IoT boards still being sold in 2025.
recommendation
Worth keeping but documenting its niche, because this is the codec-specific encoder half of MediaTek's V4L2 video stack (H.264 and VP8 paths) and MediaTek is still shipping Genio IoT SoCs with hardware video encode in 2025. Patch traffic is light but real, with a build-warning fix landing in September 2025 and being picked up for stable backport, so the code is maintained rather than abandoned. An annotation noting which MediaTek SoC families and userspace clients (e.g. v4l2h264enc on Genio) actually exercise it would help future readers.
repository signals
sources
- spinics.net
Upstream/stable activity reached this directory in September 2025 for a build-warning fix in venc_h264_if.c, indicating the code is still maintained rather than abandoned.
- spinics.net
A 2026 stable-tree backport attempt references the 2025 encoder fix, further showing this code is still relevant enough to be considered for longterm kernels.
- mediatek.com
MediaTek was still marketing new Genio SoCs with H.264/H.265 video encode capability in 2025, so Mediatek video-encode hardware remains in current-product deployment.
- genio-community.mediatek.com
A late-2025 MediaTek Genio community thread discusses using v4l2h264enc on Genio hardware, which is contemporary deployment evidence for Linux userspace on this encoder stack.
codex reasoning notes (technical)
Local shell inspection showed this directory contains real codec-specific encoder implementation files (venc_h264_if.c, venc_vp8_if.c), not just helpers. Local git log with inline safe.directory showed the split/creation commit in 2023 and later fixes including 2024-10 and 2025 touches; no sign of terminal inactivity. Web search for lore/removal discussion did not surface a removal series, while web search did surface stable-commits/stable backport pages for this exact path and current MediaTek product/deployment pages. Low change volume suggests annotating rather than pure keep, but active fixes and still-sold hardware argue against deprecate/remove.