fb_match_mode(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fb_match_mode(9)

okay so bestie, welcome to the Kernel API Manual β€” this one's a little cutie from the framebuffer corner of the kernel and honestly it's giving "find my exact match" energy. It lives in fb_match_mode(9) and it does exactly one thing, but it does it flawlessly ✨


πŸŽ€ NAME

fb_match_mode β€” find a videomode which exactly matches the timings in var πŸ’–

like, exactly. not "close enough", not "vibes are similar" β€” we're talking precise timing match, no cap.


🌸 SYNOPSIS

const struct fb_videomode * fb_match_mode (const struct
fb_var_screeninfo *var , struct list_head *head );

πŸ¦‹ ARGUMENTS

  • var β€” pointer to struct fb_var_screeninfo 🫢 this is the var you're trying to match against, the main character of the search ngl
  • head β€” pointer to struct list_head of modelist ✨ the list you're digging through, aka where all the candidate modes are chilling

⭐ RETURN

Returns a struct fb_videomode, or NULL if none found 😭 β€” so yeah, if your timing match doesn't exist in that list, you get nothing back. brutal but fair.


πŸ‘‘ SEE ALSO

okay so there's a whole friend group here, they all hang out together:


πŸ’€ friendly reminder that "exactly matches" means exactly. if you wanted "eh, close enough", go bother fb_find_nearest_mode(9) instead, iykyk.

alright bestie that's the whole page, mwah πŸ’‹ β€” this one's from ./drivers/video/fbdev/core, dated October 2026, and it's fb_match_mode(9) signing off πŸŽ€βœ¨πŸ’œ

πŸ“¦ where this page comes from