3 modedb default video mode support
6 Currently all frame buffer device drivers have their own video mode databases,
7 which is a mess and a waste of resources. The main idea of modedb is to have
9 - one routine to probe for video modes, which can be used by all frame buffer
11 - one generic video mode database with a fair amount of standard videomodes
13 - the possibility to supply your own mode database for graphics hardware that
14 needs non-standard modes, like amifb and Mac frame buffer drivers (which
17 When a frame buffer device receives a video= option it doesn't know, it should
18 consider that to be a video mode option. If no frame buffer device is specified
19 in a video= option, fbmem considers that to be a global video mode option.
21 Valid mode specifiers (mode_option argument):
23 <xres>x<yres>[-<bpp>][@<refresh>]
24 <name>[-<bpp>][@<refresh>]
26 with <xres>, <yres>, <bpp> and <refresh> decimal numbers and <name> a string.
27 Things between square brackets are optional.
29 To find a suitable video mode, you just call
31 int __init fb_find_mode(struct fb_var_screeninfo *var,
32 struct fb_info *info, const char *mode_option,
33 const struct fb_videomode *db, unsigned int dbsize,
34 const struct fb_videomode *default_mode,
35 unsigned int default_bpp)
37 with db/dbsize your non-standard video mode database, or NULL to use the
38 standard video mode database.
40 fb_find_mode() first tries the specified video mode (or any mode that matches,
41 e.g. there can be multiple 640x480 modes, each of them is tried). If that
42 fails, the default mode is tried. If that fails, it walks over all modes.
44 BTW, only a few drivers use this at the moment. Others are to follow
45 (feel free to send patches).