Home
last modified time | relevance | path

Searched refs:CVT (Results 1 – 11 of 11) sorted by relevance

/OK3568_Linux_fs/external/xserver/hw/xfree86/common/
H A Dextramodes30 # 640x360 59.32 Hz (CVT 0.23M9-R) hsync: 22.19 kHz; pclk: 17.75 MHz
33 # 640x360 59.84 Hz (CVT 0.23M9) hsync: 22.50 kHz; pclk: 18.00 MHz
36 # 720x405 58.99 Hz (CVT 0.29M9-R) hsync: 24.72 kHz; pclk: 21.75 MHz
39 # 720x405 59.51 Hz (CVT 0.29M9) hsync: 25.11 kHz; pclk: 22.50 MHz
42 # 864x486 59.57 Hz (CVT 0.42M9-R) hsync: 29.79 kHz; pclk: 30.50 MHz
45 # 864x486 59.92 Hz (CVT 0.42M9) hsync: 30.32 kHz; pclk: 32.50 MHz
48 # 960x540 59.82 Hz (CVT 0.52M9-R) hsync: 33.26 kHz; pclk: 37.25 MHz
51 # 960x540 59.63 Hz (CVT 0.52M9) hsync: 33.51 kHz; pclk: 40.75 MHz
54 # 1024x576 59.82 Hz (CVT 0.59M9-R) hsync: 35.47 kHz; pclk: 42.00 MHz
57 # 1024x576 59.90 Hz (CVT 0.59M9) hsync: 35.88 kHz; pclk: 46.50 MHz
[all …]
/OK3568_Linux_fs/external/xserver/debian/patches/
H A D001_fedora_extramodes.patch36 +# 1360x768 59.96 Hz (CVT) hsync: 47.37 kHz; pclk: 72.00 MHz
39 +# 1360x768 59.80 Hz (CVT) hsync: 47.72 kHz; pclk: 84.75 MHz
54 +# 1440x900 @ 60.00 Hz (CVT) field rate 59.89 Hz; hsync: 55.93 kHz; pclk: 106.50 MHz
60 +# 1680x1050 59.88 Hz (CVT 1.76MA-R) hsync: 64.67 kHz; pclk: 119.00 MHz
63 +# 1680x1050 59.95 Hz (CVT 1.76MA) hsync: 65.29 kHz; pclk: 146.25 MHz
66 +# 1680x1050 69.88 Hz (CVT) hsync: 76.58 kHz; pclk: 174.00 MHz
69 +# 1680x1050 74.89 Hz (CVT 1.76MA) hsync: 82.31 kHz; pclk: 187.00 MHz
72 +# 1680x1050 84.94 Hz (CVT 1.76MA) hsync: 93.86 kHz; pclk: 214.75 MHz
75 +# 1920x1080 59.93 Hz (CVT 2.07M9-R) hsync: 66.59 kHz; pclk: 138.50 MHz
78 +# 1920x1200 59.95 Hz (CVT 2.30MA-R) hsync: 74.04 kHz; pclk: 154.00 MHz
/OK3568_Linux_fs/kernel/Documentation/fb/
H A Dmodedb.rst37 Sample usage: 1024x768M@60m - CVT timing with margins
75 What is the VESA(TM) Coordinated Video Timings (CVT)?
80 "The purpose of CVT is to provide a method for generating a consistent
84 intention of CVT is to give both source and display manufacturers a
100 The CVT addresses these limitations. If used with CRT's, the formula used
106 manufacturers. Specifying for CVT will work for most, if not all, relatively
108 calculation is specified. (The CVT compatibility of the display can be
113 CVT also introduced a new naming convention (should be seen from dmesg output)::
124 Note: VESA(TM) has restrictions on what is a standard CVT timing:
/OK3568_Linux_fs/external/xserver/hw/xfree86/utils/cvt/
H A Dcvt.c130 PrintComment(DisplayModeRec * Mode, Bool CVT, Bool Reduced) in PrintComment() argument
134 if (CVT) { in PrintComment()
/OK3568_Linux_fs/buildroot/package/x11r7/xlib_libxcvt/
H A DConfig.in5 server implementation of the VESA CVT standard timing mode-
/OK3568_Linux_fs/yocto/poky/meta/recipes-graphics/xorg-lib/
H A Dlibxcvt_0.1.1.bb2 implementation of the VESA CVT standard timing modelines generator"
/OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/
H A Dvidioc-dv-timings-cap.rst148 - CVT/GTF specific: the timings can make use of reduced blanking
149 (CVT) or the 'Secondary GTF' curve (GTF).
H A Dvidioc-g-dv-timings.rst250 - CVT/GTF specific: the timings use reduced blanking (CVT) or the
/OK3568_Linux_fs/device/rockchip/common/images/oem/oem_facial_gate/
H A Dir.yuv389 …SUUUUUTSSTVVX[WYVF30CMYYE*"#'(),$ #"':FOR;57Wd^5 +bL4#:CVT>?B>>=<8:?D;8?<17?9<…
/OK3568_Linux_fs/external/xserver/
H A DChangeLog83311 resolution. From this, using CVT formulas, it derives
83325 These numbers have been rederived using both my own CVT tool
133579 providing pixel exact timings. Neither can you use CVT or GTF to
133589 So instead, make a CVT mode since that's likely to be handled well by
151751 EDID 1.4: Print additional CVT support data in the log.
151757 EDID 1.4: Decode additional CVT support information.
151759 Table 3.28: Display Range Limits & CVT Support Definition
151765 Fix CVT abuse in DDCModesFromStandardTiming.
151767 CVT is enough different from GTF that it should not be used on monitors
154009 EDID 1.4: Decode CVT 3-byte codes and add them to the mode pool.
[all …]
/OK3568_Linux_fs/recovery/
HDrootfs.cpio.gz107070100A8AEB0000041ED0000000000000000000000116841B48100000000000000FD0000000200000000000000000000000200000000.�07070100A8B07C000081A40000000000000000000000016841263500000000000000FD0000000200000000000000000000000900000000.gitkeep��07070100A8B07D000081A40000000000000000000000016841263500000000000000FD0000000200000000000000000000000B00000000.skip_fsck����07070100A8AEB10000A1FF0000000000000000000000016841B0B600000007000000FD0000000200000000000000000000000400000000bin���usr/bin�07070100A8B07E000081A400000000000000000000000168412635000001CC000000FD0000000200000000000000000000001100000000busybox. ...