XE_RTP_RULE_...ERSION_RANGE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

ok so this is the XE_RTP_RULE_GRAPHICS_VERSION_RANGE page from the Kernel API Manual (yes the real one, the manpage title literally reads XE_RTP_RULE_...ERSION_RANGE(9) because it got truncated, iconic of it honestly), and it's all about a rule that matches a range of graphics version. like a little range matcher. bestie it does exactly one thing and slays at it πŸŽ€


✨ SYNOPSIS ✨

XE_RTP_RULE_GRAPHICS_VERSION_RANGE (ver_start__ , ver_end__ );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • ver_start__ β€” the first graphics IP version you want to match. the lower bound, the beginning, the opener of the era πŸ’–
  • ver_end__ β€” the last graphics IP version to match. the upper bound, the closer, the final girl 🌸

🧚 DESCRIPTION 🧚

ok so here's the tea β˜• β€” the range this rule matches is [ ver_start__, ver_end__ ], which means inclusive on both sides, no cap. both endpoints are in the club, they both get in, the bouncer is not being weird about it. periodt. πŸ’…

⚠️ highkey important: inclusive on both sides, so don't come for me if both of them match β€” that's literally the whole vibe check.

and for the expected usage, go read XE_RTP_RULES β€” that's the main character page, this one is just its very well-dressed supporting cast 🫢


🌈 SEE ALSO 🌈

this is the whole group chat, nobody gets left on read πŸ”₯


and that's the whole page bestie, no notes πŸ’œ

🫢 cute little sign-off: this lives under ./drivers/gpu/drm/xe in the kernel tree, dated October 2026, and it's the XE_RTP_RULE_...ERSION_RANGE(9) page (yes still truncated, still iconic). k bye, go match some versions πŸ’–βœ¨

πŸ“¦ where this page comes from