VESA &= nbsp; &nbs= p; &= nbsp; &nbs= p; &= nbsp; VTB-= EXT Standard

Video Electronics Standards Associa= tion

860 Hillview Court, Suite 150 &nb= sp; = &nb= sp; = &nb= sp; = Phone: (408) 957-9270

Milpitas<= /st1:City>, CA 95035 = &nb= sp; = &nb= sp; = &nb= sp; = Fax: (408) 957-9277

VESA VIDEO TIMING BLOCK EXTENSION DAT= A STANDARD =

Release A

November 24, 2003

Purpose

This standard defines data formats to carry configuration information, allowing optimum use of displays. <= /span>

Summary

This document (Release A) describes version = 1 of a 128-byte data structure known as the "Video Timing Block Extension (VTB-EXT)”. The VTB-EXT data structure may contain up to six Detailed Timing Block (DTB) Descriptors, or up to 40 Coordinated Video Timing (CVT) Descriptors, or up to 61 Standard Timing (ST) Descriptors, or a combination= of DTB, CVT and ST video timing descriptors. VTB-EXT requires the use of base = EDID data structure version 1.3 (or newer). Use of VTB-EXT described in this document requires use of the addressing method described in the Enhanced DDC Standard (E-DDC).

Note

This issue of the VTB-EXT document contains specifications for the mandatory/optional data structures contained in this extension block. The base EDID data structure (version 1.3 or newer) is def= ined in a separate document= .

SPEC= IAL NOTICE: There are several references to GTF in the VTB-EXT Standard. VESA is in the proce= ss of replacing the GTF Standard with the CVT Standard. When this occurs, all = GTF references in the VTB-EXT Standard shall be replaced with CVT.

  &nbs= p;            &= nbsp;           &nbs= p;          =

Preface

Intellectual Property<= /span>

Copyright © 1994 - 2003 Video Electronics Standards Association.&nbs= p; All rights reserved.

While every precaution has been taken in the preparation of this standard, the Vi= deo Electronics Standards Association and its contributors assume no responsibi= lity for errors or omissions, and make no warranties, expressed or implied, of functionality or suitability for any purpose.

Trademarks<= span style=3D'font-size:14.0pt;mso-bidi-font-size:12.0pt'>

All trademarks used within this document are the property of their respective owners. VESA, DDC, EDID, GTF, CVT, etc. are trademarks of the Video Electro= nics Standard Association.

Patents

VESA proposals and standards are adopted by the Video Electronics Standards Association without regard as to whether their adoption may involve any pat= ents 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.

Support for this Stand= ard

Clarifications and application notes to supp= ort this standard may be written. To obtain the latest standard and any support documentation, contact VESA.

If you have a product, which incorporates ED= ID, you should ask the company that manufactured your product for assistance. If you are a manufacturer, VESA can assist you with any clarification you may require. All comments or reported errors should be submitted in writing to = VESA using one of the following methods.

·         Fax&n= bsp;           :        &= nbsp; 408-957 9277, direct this note to Technical Support at VESA

·         e-mail:       support@vesa.org

·         mail:=           Technical Support

  =             &nb= sp;         Video Electronics Standards Association

        &= nbsp;           &nbs= p;   860 Hillview Court, Suite 150

        &= nbsp;           &nbs= p;   Milpitas, CA 95035<= /span>

        &= nbsp;           &nbs= p;

·         website:     www.vesa@org

Revision History

November 24, 2003 – Initial release of the standard.

Acknowledgments=

This document would not have been poss= ible without the efforts of the VESA Display Committee. In particular, the follo= wing individuals and their companies contributed significant time and knowledge = to this edition of the VTB-EXT document.

<= /p>

<= /p>

<= /p>

<= /p>

Syed Athar Hussain

ATI Technologies Inc.

Don Chambers

Cables To Go

Takashi Matsui

EIZO NANAO

Graham Loveridge

Genesis Microchip

Jim Webb

Genesis Microchip

Susan Luerich

IBM

Ian Miller

Samsung

Steve Hasegawa

Sony

Workgroup Leader

Jack Hosek

NEC-Mitsubishi

Document Editor

Alain d’Hautecourt

ViewSonic

Table of Contents

Revision History..........................................= ....................................................................... 3

1.<= span style=3D'mso-tab-count:1'>       OVERVIEW.= ...........................................................................= ............................................. 5

1.1 &n= bsp;   Summary..................= ...........................................................................= ............................. 5<= o:p>

1.2 &n= bsp;   Background..................= ...........................................................................= ..................... 5<= o:p>

1.3 &n= bsp;   Standard Objectives........= ...........................................................................= ............. 5<= o:p>

1.4 &n= bsp;   Reference Documents........= ...........................................................................= .......... 6<= o:p>

2.<= span style=3D'mso-tab-count:1'>       Video Timing Block Extension (VTB-EXT) Data Stru= cture Ver. 1. 7

2.1<= span style=3D'mso-tab-count:1'>     VTB-EXT Data Structure = Format Overview............................= .................... 8<= o:p>

2.2<= span style=3D'mso-tab-count:1'>     Tag Label & Version Number: 2 bytes – Address/Offset 00h to 01h            9<= o:p>

2.3<= span style=3D'mso-tab-count:1'>     VTB-EXT Data Structure Layout: 3 bytes – Address/offset 02h to 04h    9<= o:p>

2.4<= span style=3D'mso-tab-count:1'>     Detailed Timing Section= : 108 bytes (maximum).....................= ..................... 11<= o:p>

2.5<= span style=3D'mso-tab-count:1'>     Coordinated Video Timing (CVT) Descriptors – 120 bytes (maximum)           14<= o:p>

2.6<= span style=3D'mso-tab-count:1'>     Standard Timing Descrip= tors – 122 bytes (maximum).........= ................ 16<= o:p>

2.7<= span style=3D'mso-tab-count:1'>     Unused Bytes..........................................= ................................................................... = 17<= o:p>

2.8<= span style=3D'mso-tab-count:1'>     Checksum – 1 byte= - Address/Offset 7Fh..................= ................................ 18<= o:p>

3.       APPENDIX A – Sample VTB-EXT Block...............................= ............................. 19

3.1<= span style=3D'mso-tab-count:1'>     Example 1 - VTB-EXT blo= ck ex. - for reference only (Ver.1 data structure)= 19<= o:p>

4.<= span style=3D'mso-tab-count:1'>       APPENDIX B – Note Regarding Borders –= ; (For Information Only) 28

5.<= span style=3D'mso-tab-count:1'>       APPENDIX C – Data Formats – (For Inform= ation Only).......................... 29

5.1<= span style=3D'mso-tab-count:1'>     Video Timing Block Exte= nsion (VTB-EXT) High Level Layout.........= .... 29<= o:p>

5.1.1     = Mandatory elements............................= ...................................................................... 29

5.1.2     = EDID Block Map Extension.................= ..................................................................... 30

5.1.3     = General Extension Format....................= ................................................................... = 30

6.<= span style=3D'mso-tab-count:1'>       APPENDIX D – Glossary.................................................................= ........................ 31

7.       APPENDIX E - Answers To Commonly Asked Questions= .................... 32

List of Tables

Table= 2-1 – VTB-EXT Data Structure Version 1. 8

Table 2-2 – Tag Label & Version Number= 9

Table 2-3 – VTB-EXT Data Structure Layout<= /span> 9

Table 2-4 - Detailed Timing Description.. 12

Table 2-5 - Decode of Stereo Mode Bits. 13

Table 2-6 - Sync Signal Description.. 13

Table 2-7 – 3 Byte CVT Descriptor 15

Table 2-8 – 2 Byte Standard Timing Descrip= tors. 17

Table 2-9 – Unused Bytes. 17

Table 2-10 – Checksum... 18

Table 5-1 – Extension Blocks – Manda= tory Elements. 29

Table 5-2 – EDID Block Map Extension.. 30

Table 5-3 – General Extension Format 30

1.     OVERVIEW

1.1=      Summary<= /span>

The Enhanced EDID family of documents includ= es:

1. Enhanced EDID Standard (Basic 128-byte da= ta structure. Rules for how EDID extensions are mapped.)

2. Enhanced EDID Implementation Guide

3. Optional EDID Extension Standards (data structures for additional data contained in EDID extensions are   mapped).
        =             3.1   EDID Structu= re 2 Extension

         3.2   Display Info= rmation Extension (DI-EXT)

         3.3   CEA EDID Tim= ing Extension (CE-EXT) – defined in EIA/CEA 861 Specifications=

         3.4   …future extension structures not yet defined &= nbsp;

1.2=      Backgrou= nd

The use of a base (block 0) EDID in a display has become an integral requirement for “Plug & Play” in the display/graphics subsystem. The ba= se EDID allows the host to identify the display as well as the display’s capabilities. Video timing formats (Established Timings, Standard Timings, Preferred Timing Mode, GTF, etc.) are described in the base EDID. The base = EDID has room for four detailed timing blocks. However, three of these blocks are typically used to satisfy other industry requirements. As a result, only one detailed timing block is available to describe a video timing format and th= is block is reserved for the preferred timing mode. In addition, the display industry has expanded the number and type of displays available in the marketplace. Many of these new displays require video timing formats which cannot be described in the current base EDID. Current base EDID data struct= ure definitions are full and there is no room for expansion. The VTB-EXT Standa= rd was developed to support these new displays by defining additional video ti= ming formats. The VTB-EXT data structure may contain up to= six Detailed Timing Block (DTB) Descriptors or up to 40 Coordinated Video Timing (CVT) Descriptors or up to 61 Standard Timing (ST) Descriptors or a combina= tion of DTB, CVT & ST video timings. If the combination of DTB, CVT & ST vid= eo timings exceeds 122 bytes, then additional VTB-EXT data blocks can be used.=

1.3=      Standard Objectives

The VTB-EXT Standard was developed by VESA to meet, exceed and/or complement certain criteria. These criteria are set forth as Standard Objectives as follows:

·      =    Support Microsoftâ= Plug and Play definition

·      =    Provide information in a compact format to allow the graphics subsystem to be configured based on the capabilities of the attached display

1.4=      Reference Documents

Note: Versions identifi= ed here are current, but users of this standard are advised to ensure they have the latest versions of referenced standards and documents.

<= /span>

·      =    VESA Coordinated Video Timings (CVT) Standard, Version 1, March 26, 2003

·      =    VESA Enhanced Display Data Channel Standard (E-DDC), Version 1, September 2, 199= 9

·      =    VESA Enhanced Extended Display Identification Standard (E-EDID), Release A, Revi= sion 1., February 9, 2000

·      =    VESA Enhanced Extended Display Identification Data Implementation Guide, Version 1.0, June 4, 2001

·      =    VESA Generalized Timing Formula Standard (GTF), Version 1.0, December 18, 1996

·      =    VESA and Industry Standards and Guidelines for Computer Display Monitor Timing (= DMT) – Version 1.0, Revision 0.8, September 17, 1998

·      =    EIA/CEA-861-B, A DTV Profile for Uncompressed High Speed Digital Interfaces, date TBD.

	<= /p>	<= /p>	<= /p>	<= /p>
Syed Athar Hussain	ATI Technologies Inc.
Don Chambers	Cables To Go
Takashi Matsui	EIZO NANAO
Graham Loveridge	Genesis Microchip
Jim Webb	Genesis Microchip
Susan Luerich	IBM
Ian Miller	Samsung
Steve Hasegawa	Sony
			Workgroup Leader
			Jack Hosek	NEC-Mitsubishi

			Document Editor
			Alain d’Hautecourt	ViewSonic