hdmi_infoframe_pack(9)

📦 version 7.3.1, in nixpkgs unstable

💅 hdmi_infoframe_pack(9) — the Kernel API Manual glow-up ✨

okay so bestie, welcome to the Kernel API Manual entry for hdmi_infoframe_pack(9) — this is the little function that takes your HDMI infoframe from "struct vibes" to "actual bytes a controller can read" 🎀

🌸 NAME 🌸

hdmi_infoframe_pack — check a HDMI infoframe, and write it to binary buffer. that's the whole job, and she does it flawlessly 🫶

✨ SYNOPSIS ✨

ssize_t hdmi_infoframe_pack (union hdmi_infoframe *frame , void *buffer
, size_t size );

🦋 ARGUMENTS 🦋

  • frame — the HDMI infoframe in question. yes, that one 💅
  • buffer — the destination buffer, aka where the packed-up bytes are gonna live 🎀
  • size — size of buffer. literally just how much room you're giving her 🌸

🔥 DESCRIPTION 🔥

so what she does first is validate that the infoframe is consistent — vibe check passed, bestie — and then she updates the derived fields (like length) based on the other fields, because some things are just consequences of other things, iykyk 😌

after that, she packs all the information chillin' in the frame structure into a binary representation that can be written straight into the corresponding controller registers. no cap, that's the whole flex 💅✨

she also computes the checksum as required by section 5.3.5 of the HDMI 1.4 specification — because the spec said so and we do not argue with the spec 👑

and what does she return? the number of bytes packed into the binary buffer 🎉 ... or a negative error code on failure 😭 (sad girl hours, but at least you know)

💜 SEE ALSO 💜

kernel file ./drivers/video/hdmi.c, plus the whole friend group 🫶:

and that's the page, bestie 🌈 this one lives over in ./drivers/video and it's dated October 2026 — go forth and pack those frames, ily, mwah 💖🎀🦋

📦 where this page comes from