MAX_SURFACES(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… MAX_SURFACES(9) β€” a whole kernel API manual page, bestie

okay so real talk, this one's a shortie but she's important. We're in the MAX_SURFACES zone of the kernel API manual, and honestly? she's carrying the whole vibe of "how many surfaces can we even stack on one CRTC."


✨ NAME ✨

MAX_SURFACES β€” no cap, she's literally the representative of the upper bound of surfaces that can be piped to a single CRTC 🫢

like, think of CRTC as the one main-character display pipeline, and MAX_SURFACES is the bouncer at the door going "bestie, that's the limit, we can't let any more in." iconic behavior honestly.


🌸 SYNOPSIS 🌸

MAX_SURFACES

yes that's it. that's the whole synopsis. no arguments, no flags, no nothing β€” she just is. minimalism ate and left no crumbs πŸ’…


πŸ¦‹ SEE ALSO πŸ¦‹

okay this is the part where she name-drops literally everyone in her contacts. buckle up, we're going through the whole group chat:

fr fr, go read MAX_PLANES(9) next if you want the full lore drop β€” they're giving sibling energy and the whole state-update pipeline (dc_update_state*, dc_check_state_update) is lowkey the main character arc here. iykyk πŸ’–

πŸŽ€ a lil sign-off πŸŽ€

this absolute gem lives over in ./drivers/gpu/drm/amd/display/dc, and she's stamped October 2026 β€” so yeah, mark your calendar bestie, that's the version/date situation. go forth and respect the surface limit, periodt πŸ’œπŸ”₯

πŸ“¦ where this page comes from