dc_dmub_srv_...s_dmcub_info(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dc_dmub_srv_...s_dmcub_info(9)

okay bestie, welcome to the Kernel API Manual ✨ β€” yes this is a kernel API manual page, yes it's from the Kernel API Manual section, and yes we're gonna read it together like it's the most iconic thing ever. (it lowkey is 🫢)


🌸 NAME 🌸

dc_dmub_srv_log_preos_dmcub_info β€” it logs preos dmcub fw info. that's the whole vibe. it logs it. preos. dmcub. fw. info. πŸŽ€


✨ SYNOPSIS ✨

void dc_dmub_srv_log_preos_dmcub_info (struct dc_dmub_srv *dc_dmub_srv
);

so it's a void function, meaning it gives you nothing back, it just does the thing and leaves πŸ’… and it takes exactly one argument, a struct dc_dmub_srv * named dc_dmub_srv. that's it. that's the whole signature. ate.


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dc_dmub_srv β€” okay so the manpage literally just says -- undescribed -- 😭 no cap, the docs did NOT show up for this one. it's the struct dc_dmub_srv * from above, that's all we're officially told. the manpage is being mysterious and honestly? main character energy.

πŸ‘‘ DESCRIPTION πŸ‘‘

  • dc β€” pointer to DC object 🌈

that's it. that's the description. one line. one little pointer. it's giving minimalism, it's giving "the intern wrote the docs", and we respect it fr fr πŸŽ€

no cap bestie β€” that single line about dc is literally all the description this page gives you. don't go inventing extra behaviour for it, because the manual doesn't say πŸ’€

⭐ SEE ALSO ⭐

okay this is where the page goes FULL group chat and name-drops everyone πŸ”₯ first up, the kernel file itself, then the whole friend group:

like, that's the whole entourage 🧚 every single one of them, exactly as written, no cap πŸ’œ


πŸ’– and that's the page!! huge shoutout to the source over at ./drivers/gpu/drm/amd/display/dc and to October 2026 for timestamping this lil masterpiece β€” catch you in the next one, bestie, slay πŸŒΈβœ¨πŸ’…
πŸ“¦ where this page comes from