Lines Matching +full:display +full:- +full:timings
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
23 <xres>x<yres>[M][R][-<bpp>][@<refresh>][i][m][eDd]
24 <name>[-<bpp>][@<refresh>]
30 <bpp> and <refresh>, if specified) the timings will be calculated using
31 VESA(TM) Coordinated Video Timings instead of looking up the mode from a table.
37 Sample usage: 1024x768M@60m - CVT timing with margins
41 'e' will force the display to be enabled, i.e. it will override the detection
42 if a display is connected. 'D' will force the display to be enabled and use
44 signals (e.g. HDMI and DVI-I). For other outputs it behaves like 'e'. If 'd'
50 video=VGA-1:1280x1024@60me
54 video=LVDS-1:d video=HDMI-1:D
58 Sample usage: 720x480,rotate=180 - 720x480 mode, rotated by 180 degrees
62 - margin_top, margin_bottom, margin_left, margin_right (integer):
64 - reflect_x (boolean): Perform an axial symmetry on the X axis
65 - reflect_y (boolean): Perform an axial symmetry on the Y axis
66 - rotate (integer): Rotate the initial framebuffer by x
68 - panel_orientation, one of "normal", "upside_down", "left_side_up", or
73 -----------------------------------------------------------------------------
75 What is the VESA(TM) Coordinated Video Timings (CVT)?
81 and coordinated set of standard formats, display refresh rates, and
82 timing specifications for computer display products, both those
83 employing CRTs, and those using other display technologies. The
84 intention of CVT is to give both source and display manufacturers a
85 common set of tools to enable new timings to be developed in a
88 This is the third standard approved by VESA(TM) concerning video timings. The
89 first was the Discrete Video Timings (DVT) which is a collection of
90 pre-defined modes approved by VESA(TM). The second is the Generalized Timing
91 Formula (GTF) which is an algorithm to calculate the timings, given the
96 requirement. This is inappropriate for digital display interface with its high
98 Also, GTF does not take into account the aspect ratio of the display.
105 to the global mode database whenever a new mode is released by display
108 calculation is specified. (The CVT compatibility of the display can be
109 determined from its EDID. The version 1.3 of the EDID has extra 128-byte
115 <pix>M<a>[-R]
119 a = aspect ratio (3 - 4:3; 4 - 5:4; 9 - 15:9, 16:9; A - 16:10)
120 -R = reduced blanking
122 example: .48M3-R - 800x600 with reduced blanking
126 - aspect ratio can only be one of the above values
127 - acceptable refresh rates are 50, 60, 70 or 85 Hz only
128 - if reduced blanking, the refresh rate must be at 60Hz
131 timings will still be calculated.
133 -----------------------------------------------------------------------------
143 with db/dbsize your non-standard video mode database, or NULL to use the
152 video=<driver>:<xres>x<yres>[-<bpp>][@refresh]
161 amifb - Amiga chipset frame buffer
162 aty128fb - ATI Rage128 / Pro frame buffer
163 atyfb - ATI Mach64 frame buffer
164 pm2fb - Permedia 2/2V frame buffer
165 pm3fb - Permedia 3 frame buffer
166 sstfb - Voodoo 1/2 (SST1) chipset frame buffer
167 tdfxfb - 3D Fx frame buffer
168 tridentfb - Trident (Cyber)blade chipset frame buffer
169 vt8623fb - VIA 8623 frame buffer