hdmi_avi_inf...me_pack_only(9)

📦 version 7.3.1, in nixpkgs unstable

🎀 hdmi_avi_infoframe_pack_only 💅

okay so bestie, welcome to the Kernel API Manual entry for hdmi_avi_infoframe_pack_only(9) — yes that's the full name, yes it's a mouthful, no we're not shortening it, it's iconic as is. ✨

🌸 NAME 🌸

hdmi_avi_infoframe_pack_only — write HDMI AVI infoframe to binary buffer

Like, that's the whole vibe. You got an AVI infoframe, you got a binary buffer, and this function is the matchmaker. 🫶

🦋 SYNOPSIS 🦋

ssize_t hdmi_avi_infoframe_pack_only (const struct hdmi_avi_infoframe
       *frame , void *buffer , size_t size );

literally just look at it. three args. so clean. 😭

⭐ ARGUMENTS ⭐

  • frame — the HDMI AVI infoframe itself, the main character of this whole operation 👑
  • buffer — destination buffer, aka where the packed bytes are gonna live rent-free
  • size — size of buffer, bestie please actually pass the right one, it's not decorative 💀

✨ DESCRIPTION ✨

So what does it do? It packs the information contained in the frame structure into a binary representation that can be written into the corresponding controller registers. yes, all of that, no cap. 🧚

It also computes the checksum as required by section 5.3.5 of the HDMI 1.4 specification. like it's not just vibing, it's doing actual spec-compliant math. obsessed. 🔥

Then it returns the number of bytes packed into the binary buffer, or a negative error code on failure. so check that return value, bestie, i'm begging 🙈

ngl the _only in the name is doing real work here — this one packs and returns the byte count directly, that's the whole point 🎀

🌈 SEE ALSO 🌈

Kernel file ./drivers/video/hdmi.c — and the entire friend group, fr fr:

and that's the page!! 💖✨🎀🦋

sign-off time: this lil beauty lives in ./drivers/video, dated October 2026, and it's filed under the Kernel API Manual — periodt. 💜🌸

📦 where this page comes from