STRUCT VENC_H264_VPU_CONFIG_EXT(9)
πΈ NAME πΈ
okay so this is the struct venc...u_config_ext(9) page in the Kernel API Manual, and it's literally the Structure for h264 encoder configuration. The page also drops these access hints, iykyk: AP-W/R : AP is writer/reader on this item, and VPU-W/R: VPU is write/reader on this item. π
β¨ SYNOPSIS β¨
Here's the whole struct, bestie β no cap, copy it exactly:
struct venc_h264_vpu_config_ext {
u32 input_fourcc;
u32 bitrate;
u32 pic_w;
u32 pic_h;
u32 buf_w;
u32 buf_h;
u32 gop_size;
u32 intra_period;
u32 framerate;
u32 profile;
u32 level;
u32 wfd;
u32 max_qp;
u32 min_qp;
u32 reserved[8];
};
π§ Members π§
vibe check the members, bestie β every single one is iconic in its own way:
input_fourccβ input fourcc, periodt.bitrateβ target bitrate (in bps). πΈpic_wβ picture width. Picture size is visible stream resolution, in pixels, to be used for display purposes; must be smaller or equal to buffer size. So yes, it has to fit inside the buffer, no cap.pic_hβ picture height.buf_wβ buffer width. Buffer size is stream resolution in pixels aligned to hardware requirements.buf_hβ buffer height.gop_sizeβ group of picture size (idr frame).intra_periodβ intra frame period.framerateβ frame rate in fps.profileβ as specified in standard.levelβ as specified in standard.wfdβ WFD mode 1:on, 0:off.max_qpβ max quant parameter.min_qpβ min quant parameter.reservedβ reserved configs. (And in the synopsis it'sreserved[8], just saying. π )
π₯ SEE ALSO π₯
- Kernel file β
./drivers/media/platform/mediatek/vcodec/encoder/venc/venc_h264_if.c struct venc_h264_vpu_buf_34(9),struct venc_h264_vsi_34(9)
mwah π source/version: ./drivers/media/platform/media... β date: October 2026 β footer title: struct venc...u_config_ext(9). byeee π«Άβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms