![](3D"sumdpvlsi_files/image001.gif")
&nb=
sp; =
&nb=
sp; =
&nb=
sp; =
&nb=
sp; =
&nb=
sp; =
DPVL-SI Standard
|
|
Phone: (408) 957-9270 Fax: (408) 957-9277 |
VESA DPVL SOFTWARE INTERFACE STANDARD
Version
1
February 28, 2006
Purpose
This proposal defines a device independent software interface
handler which resides between the graphics subsystem of an operating system=
and
a device specific graphics card driver.&nb=
sp;
This handler allows third party software developers to create a DPVL
system that can be used by any graphics board that supports the extensions
defined in this proposed standard.
Summary
To help enable the
proliferation of DPVL enabled monitors, it is advantageous for a software
interface standard to allow the majority of the DPVL software to be develop=
ed
in a device independent manner. Two
software interfaces are defined by the proposed standard. The first interface is between the
device independent DPVL-Software Interface (DPVL-SI) handler and the device
specific graphics card driver. The
second interface is between the device independe=
nt DPVL-SI
Handler and an application program utilizing features of the DPVL standard.=
Windows-specific
and Linux-specific implementations are included in this standard.
Tabl=
e of
Contents
PREFACE
Intellectual Property S=
tatement..........................................=
.......................................................... =
REF ip
\h \* MERGEFORMAT 5
Trademarks..........................................=
...........................................................................=
............. 5
Patents .........................=
...........................................................................=
..................................... 5
Other Documents Referen=
ced..........................................=
............................................................. 5
Support For This Standa=
rd..........................................=
................................................................. 5
Conformance Glossary -<=
/span> Definition of Terms.........=
...................................................................... 5
2.1.1 Filter
driver implementation technique (Windows)
2.1.2 .dll
implementation technique (Windows)
2.2.1 X
Extension implementation technique (Linux)
3.2.7 DPVLValidateVirt=
ualResolution
3.2.8 DPVLSetVirtualRe=
solution
3.2.9 DPVLSetHWCursorS=
hape
(optional)
3.2.10 DPVLSetHWCursorPosition
(optional)
4.2 Mechanism
for Accessing the Features
4.3 Feature
Function Parameters
4.3.4 Scaled
Video Stream Setup
4.3.11 Transparency
Map Packet
5.1 Driver
Interface/ Retrieving the Interface.
5.1.1 DPVL_QUERY_IMPLE=
MENTATION
(0xFACADE00)
5.1.8 DPVLValidateVirt=
ualResolution
5.1.9 DPVLSetVirtualRe=
solution
5.1.11 DPVLSetHWCursorPosition
5.2.2 Feature
Function Parameters
6.1.6 DPVLValidateVirt=
ualResolution
6.1.7 DPVLSetVirtualRe=
solution
6.1.9 DPVLSetHWCursorP=
osition
6.2.1 Feature
Function Parameters
LIST OF FIGURES
Figure 2‑1 -
Software Interface Block Diagram for filter driver implementation under Win=
dows
Figure 2‑2: =
Software
Interface Block Diagram for a .dll implementation under Windows
Figure 2‑3: =
Software
Interface Block Diagram for a Linux based X extension implementation
LIST OF TABLES
Table 1‑1: R=
eference
Documents
Table 3‑1:
Parameters for the DPVLGetDeviceAttr function.
Table 3‑2:
Parameters for the DPVLGetCrtcAttr function.
Table 3‑3:
Parameters for the DPVLEnable function.
Table 3‑4:
Parameters for the DPVLSetCRT function.
Table 3‑5:
Parameters for the DPVLValidateResolution function.
Table 3‑6:
Parameters for the DPVLSetVirtualResolution function.
Table 3‑7:
Parameters for the DPVLSetHWCursorShape function.
Table 3‑8:
Parameters for the DPVLSetHWCursorPosition function.
Table 3‑9:
Parameters for the DPVLSetSignaling function.
Table 4‑1: L=
ist of
the features which the application layer supports.
Table 4‑2:
Parameters for retrieving IOCTL codes of the various application interface
functions
Table 4‑3 :
Parameters in the DPVLGetUserFeatures function.
Table 4‑4 Pa=
rameters
needed for implementing the Video Packet Function.
Table 4‑5:
Parameters needed for implementing the Genlock Function.
Table 4‑6:
Parameters needed for implementing theScaled Video Stream Setup Function
Table 4‑7:
Parameters needed for implementing the Scaled Video Stream Function
Table 4‑8:
Parameters needed for implementing the Gamma Table Function
Table 4‑9:
Parameters needed for implementing the Frame Buffer Control Function
Table 4‑10:
Parameters needed for implementing the BitBlt Function.
Table 4‑11:
Parameters needed for implementing the Area Fill Function
Table 4‑12:
Parameters needed for implementing the Pattern Fill Function
Table 4‑13:
Parameters needed for implementing the Transparency Map Function
Table 5‑1:
Parameters for obtaining the escape code for DPVLGetInterface
Table 5‑2:
Parameters for obtaining the escape codes for the Driver interface function=
s
Table 5‑3:
Parameters for the DPVLGetDeviceAttr Escape Call
Table 5‑4: F=
lags
returned by the DPVLGetDeviceAttr Escape call
Table 5‑5:
Parameters for the DPVLGetCrtcAttr Escape Call
Table 5‑6:
Parameters for the DPVLEnable Escape Call
Table 5‑7:
Parameters for the DPVLSetCrt Escape Call
Table 5‑8:
Definition of the flags parameter in the DPVLSetCrt Escape Call=
Table 5‑9:
Definition of the priority parameter in the DPVLSetCrt Escape Call=
Table 5‑10: =
Return
Values from the DPVLSetCrt Escape Call
Table 5‑11:
Parameters for the DPVLValidateVirtualResolution Escape Call=
Table 5‑12:
Parameters for the DPVLSetVirtualResolution Escape Call
Table 5‑13:
Parameters for the DPVLSetHWCursorShape Escape Call
Table 5‑14:
Parameters for the DPVLSetHWCursorPosition Escape Call
Table 5‑15:
Parameters for the DPVLSetSignaling Escape Call
Table 5‑16:
Definition of the flags parameter in the DPVLSetSignaling Escape Call=
Table 5‑17:
Parameters for retrieving DrvEscape codes of various application interface
functions
Table 5‑19 :
Parameters in the DPVLGetUserFeatures function.
Table 5‑20
Parameters used in the SceneSync function.
Table 5‑21 P=
armeters
used in the VideoPacket function.
Table 5‑22:
Parmeters used in the Genlock function.
Table 5‑23:
Parameters used in the ScaledVideoStreamSetup function.
Table 5‑24:
Parameters used in the ScaledVideoStream function.
Table 5‑25:
Parameters used in the GammaTable function.
Table 5‑26:
Parameters used in the FrameBufferControl function.
Table 5‑27:
Parameters used in the BitBlt function.
Table 5‑28:
Parameters used in the Area Fill function.
Table 5‑29:
Parameters used in the Pattern Fill function.
Table 5‑30:
Parameters used in the Transparency Map function.
Table 6‑1:
Definition of the DPVL_GET_INTERFACE data structure.
Table 6‑2:
Definition of the DPVL_GET_INTERFACE data structure.
Table 6‑3: F=
lags
returned by the DPVLGetDeviceAttr function call
Table 6‑4:
Definition of the DPVL_GET_CRTC_ATTR data structure.
Table 6‑5:
Definition of the flags parameter in the DPVLSetCrt function call=
Table 6‑6:
Definition of the priority parameter in the DPVLSetCrt function call=
Table 6‑7: R=
eturn
Values from the DPVLSetCrt function call
Table 6‑8:
Definition of the flags parameter in the DPVLSetSignaling function Call=
Table 6‑9:
Definition of the DPVL_GET_USER_FEATURES data structure.
Table 6‑10 P=
armeters
used in the SceneSync function
Table 6‑11:
Parameters used in the VideoPacket function.
Table 6‑12:
Parmeters used in the Genlock function.
Table 6‑13:
Parameters used in the ScaledVideoStreamSetup function.
Table 6‑14:
Parameters used in the ScaledVideoStream function.
Table 6‑15:
Parameters used in the GammaTable function.
Table 6‑16:
Parameters used in the FrameBufferControl function.
Table 6‑17:
Parameters used in the BitBlt function.
Table 6‑18:
Parameters used in the Area Fill function.
Table 6‑19:
Parameters used in the Pattern Fill function.
Table 6‑20:
Parameters used in the Transparency Map function.
While every precaution =
has been
taken in the preparation of this standard, the Video Electronics Standards
Association and its contributors assume no responsibility for errors or
omissions, and make no warranties, expressed or implied, of functionality or
suitability for any purpose.
Windows is a registered
trademark of Microsoft Corporation.
VESA proposals and stan=
dards
are adopted by the Video Electronics Standards Association without regard a=
s to
whether their adoption may involve any patents or articles, materials, or
processes. Such adoption does not assume any liability to any patent owner,=
nor
does it assume any obligation whatsoever to parties adopting the proposals =
or
standards documents.
=
Note: Versions
identified here are current, but users of this standard are advised to ensu=
re
they have the latest versions of referenced standards and documents.
|
Source |
Name |
Version / Date |
|
VESA |
Digita=
l Packet
Video Link (DPVL) Standard |
Ver. 1, April 18, 2004 |
|
VESA |
Enhanc=
ed
Display Data Channel (E-DDC) Standard |
Ver. 1.1, March 24, 2004 |
Table 1
=
Supp=
ort
for this Standard
Clarifications and appl=
ication
notes to support this standard may be written. To obtain the latest standard
and any support documentation, contact VESA.
I=
f you
have a product which incorporates any variant of the DPVL system, you should
ask the company that manufactured your product for assistance. If you are a
manufacturer, VESA can assist with any clarification you may require. All
comments or reported errors should be submitted in writing to VESA using on=
e of
the following methods.
<= o:p>
Fax: =
408-957
9277, direct this note to Technical Support at VESA
e-mai=
l: &nb=
sp; support@ve=
sa.org
mail<=
/span>: &nb=
sp; =
Technical
Support
Video Electronics Standar=
ds
Association
=
Conf=
ormance
Glossary – Definition of Terms
The requirements and specifications for the VESA DPVL-SI standard
adhere to the following definitions and conventions:
a)&n=
bsp;
Features or
functions that are required to be implemented are identified by the word
b)&n=
bsp;
Features or
functions that are desirable, but that are not required to be implemented a=
re
identified by the word should in bold type. Failure to adhere to a f=
eature
or function identified by should may inhi=
bit
the implementation of some features or functions in specific applications a=
nd
environments.
c)&n=
bsp;
Features or
functions that are optional and are not needed to be implemented are identi=
fied
by the word may in bold type. Such features or functions represent g=
oals
to be achieved, and may enhance convenience and utility of the VESA DPVL-So=
ftware
Interface.
d)&n=
bsp;
A number pr=
efaced
with 0x is a hexadecimal number, any number with=
out a
preface of 0x is a decimal number.
&=
nbsp; &nbs=
p;
=
Revi=
sion
History
February 28, 2006 – Initial release of the stand=
ard
=
Ackn=
owledgements
This document would not=
have
been possible without the efforts of the VESA Display Systems Standards
Committee’s DPVL Task Group. In particular, the following individuals=
and
their companies contributed significant time and knowledge to this edition =
of
the standard.
|
Syed <=
span
class=3DSpellE>Athar Hussain |
ATI
Technologies |
|
Marcus=
Andrews |
Micros=
oft |
|
**Rica=
rdo Baratto |
|
|
Wayne =
Young |
NVidia |
|
**Jaso=
n Nieh |
|
|
Michael
Anderson |
Portra=
it
Displays Inc. |
|
Jim We=
bb |
Displa=
y Labs |
|
Mark <=
span
class=3DSpellE>Stockfisch |
Quantu=
m Data |
|
Takash=
i Matsui |
EIZO N=
ANAO |
|
Ian Mi=
ller |
Samsung
Electronics |
|
Steve =
Millman |
IBM |
|
Joe |
Tech S=
ource |
|
Kai |
IBM |
|
Phil M=
erritt |
Tech S=
ource |
|
Eric <=
span
class=3DSpellE>Wogsberg |
Jupiter
Systems |
|
Alain
d’Hautecourt |
ViewSonic |
|
Ameet Chitre |
Micros=
oft |
|
&=
nbsp; |
&=
nbsp; |
**
non-member participant
1.
Overview
This document describes the Digital Packet Video Link
Software Interface (DPVL-SI) Standard, which defines software interfaces
between a device independent software handler and a device specific graphics
driver. The standard also def=
ines a
software interface between the device independent software handler and an
application layer program.
1.1
Background<=
/span>
Since the DPVL standard was released, companies want=
ing to
develop DPVL-compliant products for general use have had a difficult time
writing the software necessary to create a complete system. Primarily this difficulty is due t=
o the
necessity of possessing specific knowledge of and the ability to modify the
graphics drivers provided by the graphics card companies. The graphics card companies are he=
sitant
to expend the effort needed to create the entire DPVL software system until
they can see a clear widespread use, and have multiple hardware implementat=
ions
to choose from. The monitor c=
ompanies
that have the ability to create DPVL compliant hardware are reluctant to em=
bark
on development projects to create the hardware when there is no standard
software available. Monitor
companies typically do not have the software expertise to create a full DPVL
software system. Therefore, to
alleviate this problem, a software interface standard is needed to allow the
majority of the DPVL software to be developed in a device independent
manner. The device specific p=
ortion
should require minimal modifications to already existing graphics card driv=
ers.
1.2
Objectives<=
/span>
The objective of the DPVL-SI standard is to define t=
wo
software interfaces. The first interface is between the device
independent DPVL-SI Handler and the device specific graphics card driver. Section 1 provides an overview and justification of =
the
proposed standard. Section 2 =
describes
the architecture of the software interfaces and how they fit into the overa=
ll
system. Section 3 describes t=
he
interface between the device independent DPVL-SI Handler and the device
specific graphics card driver (hereafter called the “Driver Interface=
”)
in an operating system agnostic manner.&nb=
sp;
Section 4 defines the interface between the device independent DPVL-=
SI
Handler and an application program (hereafter called the “Application
Interface”) in an operating system agnostic manner. Annex 1 in sectio=
n 5 defines
interfaces in a Microsoft Windows implementation. Annex 2 in section 6 defines the
interfaces in a Linux environment.1.3
Document La=
yout