qcom_mdt_get_size(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… qcom_mdt_get_size(9) β€” Kernel API Manual, bestie edition

okay so picture this: it's a kernel API manual page, the function is called qcom_mdt_get_size, and it's about to tell you exactly how much memory room the mdt needs. it's giving "let me just check how big this is before we commit" energy and honestly? iconic. πŸŽ€


✨ NAME ✨

qcom_mdt_get_size β€” acquire the size of the memory region needed to load mdt

πŸ¦‹ SYNOPSIS πŸ¦‹

ssize_t qcom_mdt_get_size (const struct firmware *fw );

🌸 ARGUMENTS 🌸

  • fw β€” the firmware object for the mdt file. that's the whole vibe check right there, one (1) firmware struct and nothing else πŸ’–

πŸ”₯ DESCRIPTION πŸ”₯

She returns the size of the loaded firmware blob, full stop. That's the number you asked for, no cap.

But bestie β€” if something goes sideways and it fails, you're getting -EINVAL back. Lowkey a jump scare, but at least it's honest about it. 😭

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/soc/qcom/mdt_loader.c, plus these fellow main characters right here:


and that's the whole page, bestie, you ate that 🫢

source/version: ./drivers/soc/qcom Β· dated October 2026 Β· qcom_mdt_get_size(9) β€” mwah, see u next manpage πŸ’œβœ¨

πŸ“¦ where this page comes from