riva_rclut(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… riva_rclut(9) β€” read from CLUT register

okay bestie, welcome to riva_rclut(9), straight out of the Kernel API Manual ✨ this one is a tiny little function but she is doing her job and honestly? we respect her for it 🫢


πŸŽ€ NAME

riva_rclut β€” read from CLUT register πŸ’–


✨ SYNOPSIS

void riva_rclut (RIVA_HW_INST *chip , unsigned char regnum , unsigned
char *red , unsigned char *green , unsigned char *blue );

like yes, she's void β€” she doesn't return anything, she just does the thing and moves on, main character energy honestly πŸ‘‘


πŸ¦‹ ARGUMENTS

  • chip β€” pointer to a RIVA_HW_INST object 🌸 that's your hardware-instance bestie, she holds the whole vibe
  • regnum β€” register number πŸ”’ the specific color register you're visiting
  • red β€” red component ❀️ (the red goes in here)
  • green β€” green component πŸ’š (and the green goes in here)
  • blue β€” blue component πŸ’™ (and the blue goes in here, we love a full set)

🌈 DESCRIPTION

So the way this works is she reads red, green, and blue from color register regnum 🎨 like she goes to that one register and comes back with the whole RGB trio, no cap. Your three pointer args (red, green, blue) are where those values land, so they better be valid pointers, iykyk 😭

CALLED FROM: rivafb_setcolreg ⭐ (that's her one caller, her ride-or-die, they're literally inseparable)


πŸ‘‘ SEE ALSO

Kernel file ./drivers/video/fbdev/riva/fbdev.c πŸ“ β€” go read the source, it ate

ngl riva_wclut(9) is literally her sister function β€” rclut reads, wclut writes, they're giving complementary icons fr fr πŸ’…

πŸ’œ and that's the whole page!! brought to you by the fine folks over at ./drivers/video/fbdev/riva, dated October 2026, in the Kernel API Manual β€” slay, go read riva_wclut(9) next, mwah πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from