Development
Hardware documentation
Host bridge
- VIA VX800 : http://linux.via.com.tw/support/beginDownload.action?eleid=563&fid=863
- VIA VX855 : http://linux.via.com.tw/support/beginDownload.action?eleid=561&fid=861
- VIA VX900 : http://linux.via.com.tw/support/beginDownload.action?eleid=562&fid=862
2D
- VIA CX700 : http://www.x.org/docs/via/OGPM_UniChrome_ProII_R108a_Part1_Core_2D.pdf
- VIA VX800 : http://www.x.org/docs/via/OGPM_Chrome9%20HC3_R100a_Part1_Core_2D.pdf
- VIA VX855 : http://www.x.org/docs/via/OGPM_Chrome9%20HCM_R100_Part1_Core_2D.pdf
- VIA VX900 : http://www.x.org/docs/via/OGPM_Chrome9%20HD%20DX9%20_R100_PartI_Core_2D.pdf
3D
- VIA CX700 : http://www.x.org/docs/via/OGPM_UniChrome_ProII_R108a_Part2_3D_Video.pdf
- VIA VX800 : http://www.x.org/docs/via/OGPM_Chrome9%20HC3_R100a_Part2_3D_Video.pdf
- VIA VX855 : http://www.x.org/docs/via/OGPM_Chrome9%20HCM_R100_Part2_3D_Video.pdf
- VIA VX900 : http://www.x.org/docs/via/OGPM_Chrome9%20HD%20DX9%20_R100_PartII_3D_Video.pdf
LVDS encoders
- VIA VT1631L : not available
- VIA VT1636 : ftp://ftp.vt-bridge.org/Docs/Video/DVI_LVDS/DS_VT1636_100_CCPL.pdf
- VIA VT1637 : ftp://ftp.vt-bridge.org/Docs/Video/DVI_LVDS/DS_VT1637_100_CCPL.pdf
- Chrontel CH7019B : http://www.chrontel.com/pdf/7019ds.pdf
TMDS encoders
TV encoders
- VIA VT1625/M : ftp://ftp.vt-bridge.org/Docs/Video/TVENC/DS_VT1625_VT1625M_100_CCPL.pdf
- VIA VT1625S/SM : ftp://ftp.vt-bridge.org/Docs/Video/TVENC/DS_VT1625S_VT1625SM_100_CCPL.pdf
- Chrontel CH7019B : http://www.chrontel.com/pdf/7019ds.pdf
Coding style
The code formatting in the openChrome driver is currently a mess. It is the result of having several different developers, each coding in his own way. The goal is to get as close as possible to some kind of Xorg unified coding style. If the instructions below differ substantially from what's current practice, they will be revised.
Function names start with a lowercase letter and are written like this: viaFunctionName() As a general rule all functions should start with the prefix "via", however to improve clarity, static functions are allowed to start with other names.
Variables also start with a lowercase letter: numOfScreens Global variables should be avoided.
Type names start with an uppercase letter: ViaMagicType Structs are wrapped with typedef.
Indentation and general formatting should be done with the command:
indent -bad -bap -c40 -cd0 -ncdb -ci4 -cli0 -cp0 -ncs -d0 -di4 \
-i4 -ip4 -l78 -nlp -npcs -psl -sob -ss -br -ce -sc
See also the Xorg coding style page: http://www.x.org/wiki/CodingStyle
Todo list
| *Priority * | *Category * | *Task * | *Status * |
| High | RandR | Dual screen | |
| High | DRM | Prepare drm-openchrome for merge into drm-next | |
| Medium | KMS | DRI2 (Xv/XvMC) | |
| Medium | KMS | 2D acceleration (EXA) | |
| Medium | KMS | HW screen rotation | |
| Low | KMS | I2C slave encoders frame work support | |
| Low | KMS | More I2C slave encoders | |
| Low | KMS | TV output | |
| Low | KMS | Display Port output | |
| Low | KMS | Power Management | |
| Low | Video | Multiple Xv ports | |
| Low | Video | MSD hw video decoder support (CX700 and later) | WIP |
| Low | Video | VAAPI/VDPAU support | |
| Low | Video | iDCT/MoComp support | |
| Low | Video | mpeg4 support | |
| Low | 3D | 3D acceleration |
Registers dump
Building the driver with the --enable-viaregtool configure option will generate a via_regs_dump binary that will be placed into /usr/sbin on install.
It can be used to dump the IGP registers as well as other useful information.