XE_RTP_RULE...ERSION_RANGE(9)

📦 version 7.3.1, in nixpkgs unstable

💅 XE_RTP_RULE_MEDIA_VERSION_RANGE(9) — like, the whole glow-up

okay so bestie, welcome to the Kernel API Manual ✨ this little page is all about XE_RTP_RULE_MEDIA_VERSION_RANGE, and honestly? she's a vibe. tiny rule, big energy. let's get into it 🎀

🌸 NAME 🌸

XE_RTP_RULE_MEDIA_VERSION_RANGE — literally just creates a rule that matches a range of media version 💖 that's it, that's the whole job, and she does it flawlessly.

✨ SYNOPSIS ✨

XE_RTP_RULE_MEDIA_VERSION_RANGE (ver_start__ , ver_end__ );

look at her go 🫶 two args, no drama.

🎀 ARGUMENTS 🎀

  • ver_start__ — the first media IP version you wanna match. the beginning of the era, the opening act 👑
  • ver_end__ — the last media IP version you wanna match. the finale, the closing number 💫

🦋 DESCRIPTION 🦋

so here's the tea, and it's important tea ☕: the range this rule matches is [ ver_start__, ver_end__ ] — and that means inclusive on both sides, no cap. ver_start__ is in, ver_end__ is in, everybody's invited to the party 🎉

bestie pls don't forget the inclusive thing, it's literally the whole point of the note 😭

for how you're actually supposed to use this thing, go check out XE_RTP_RULES — she's the main character energy that explains the expected usage 🌈

💜 SEE ALSO 💜

buckle up, this list is long and honestly iconic:

Kernel file ./drivers/gpu/drm/xe/xe_rtp.h 🗂️ plus a whole squad:

like, the whole friend group fr fr 💀💅

and that's the page, bestie!! 🍓 this little masterpiece lives over in ./drivers/gpu/drm/xe, dated October 2026, and it signs off as XE_RTP_RULE...ERSION_RANGE(9) — yes the footer truncates her name, she's mysterious like that 😭✨ go forth and match some media versions, ily 🧚💜

📦 where this page comes from