EDID data exchange is a standardized means for a display to communicate its capabilities to a source device. The premise of this communications is for the display to relay its operational characteristics, such as its native resolution, to the attached source, and then allow the source to generate the necessary video characteristics to match the needs of the display. This maximizes the functional compatibility between devices without requiring a user to configure them manually, thus reducing the potential for incorrect settings and adjustments that could compromise the quality of the displayed images and overall reliability of the system.
Generally, the source device will be a computer graphics card on a desktop or laptop PC, but provisions are in place for many other devices, including HDTV receivers and DVRs, DVD and Blu-ray Disc players, and even gaming consoles, to read EDID and output video accordingly. Originally developed for use between analog computer-video devices with VGA ports, EDID is also now implemented for DVI, HDMI, and DisplayPort.
Prior to the development of EDID, pins 4, 11, 12, and 15 on the VGA connector were sometimes used to define monitor capabilities. These ID bit pins carried either high or low values to define different screen resolutions. VESA extended this scheme by redefining VGA connector pins 9, 12, and 15 as a serial bus in the form of the DDC - Display Data Channel. This allowed for much more information to be exchanged, so that EDID and other forms of communication were possible between the source and the display.
As display types and capabilities increased, 128 bytes became insufficient, and both EDID and DDC were extended so that multiple 128-byte data blocks could be exchanged. This is known as E-EDID and has been implemented in many consumer devices. In fact, the CEA - Consumer Electronics Association has defined its own EDID extensions to cover additional video formats and to support advanced multi-channel audio capabilities.
In December 2007, VESA released DisplayID, a second generation of EDID. It is intended to replace all previous versions. DisplayID is a variable length data structure, of up to 256 bytes, that conveys display-related information to attached source devices. It is meant to encompass PC display devices, consumer televisions, and embedded displays such as LCD screens within laptops, without the need for multiple extension blocks. DisplayID is not directly backward compatible with previous EDID/E-EDID versions, but is not yet widely incorporated in AV products.
The base EDID information of a display is conveyed within a 128-byte data structure that contains pertinent manufacturer and operation-related data. See Table 2. The current EDID version defines the structure as follows:
This byte indicates the number of additional extension blocks available. Various structures for these extension blocks have been defined, including DI-EXT - Display Information Extension, VTB-EXT - Video Timing Block Extension, and LS-EXT - Localized String Extension.
The general structure of CEA-861 extension data is shown in Table 3. CEA-861 allows for a variable number of 18-byte detailed timing descriptions to be included. For example, video timing details for 1080i, which is popular for consumer displays but not for PCs, can be communicated. CEA-861 also specifies a variable length "CEA Data Block Collection" for describing parameters such as display colorimetry, and advanced audio capabilities including surround sound format, audio sampling rate, and even speaker configuration and placement. The significance of the CEA-861 extension is that it aims to address previous operational disparities experienced with integrating consumer-based display devices into computer-based commercial AV systems, allowing for proper conveyance of EDID information between devices.
The DDC uses a standard serial signaling scheme known as the I2C bus. I2C is used extensively where electronic devices and components need to exchange information, due to its simplicity, low pin count, and bi-directional capability. An I2C bus consists of three wires: SDA - data, SCL - clock, and a logic "high" DC pull-up voltage. For the DDC, the logic "high" voltage is specified to be +5V.
EDID information is typically exchanged when the video source starts up. The DDC specifications define a +5V supply connection for the source to provide power to a display's EDID circuitry so that communication can be enabled, even if the display is powered off. At startup, the video source will send a request for EDID over the DDC. The EDID/DDC specifications support hot plug detection, so that EDID information can also be exchanged whenever a display is reconnected to a video source. Hot plug detection is not supported for VGA, but is supported in digital interfaces including DVI, HDMI, and DisplayPort. For these interfaces, the display device will supply a voltage on an HPD - Hot Plug Detect pin, to signal to the video source device that it is connected. The absence of a voltage on the HPD pin indicates disconnection. The video source device monitors the voltage on the HPD pin and initiates EDID requests as it senses incoming voltage.
Display devices can have various levels of EDID implementation and, in some cases, they may lack EDID information altogether. Such inconsistencies can cause operational issues ranging from overscan and resolution problems, to the display device not displaying the source content at all.
Software such as Extron EDID Manager can be used to help troubleshoot possible compatibility issues between the display device and the source. EDID Manager is available as a free download from Extron's Web site, www.extron.com. It is a useful software tool that allows you to read the display's EDID and determine whether a graphic card and the display device may be experiencing EDID handshake problems.
AV systems typically comprise several remotely located displays and often include multiple source devices. It is important to realize this can potentially contribute to EDID-related issues. The necessity to switch, distribute, and route signals from sources to displays presents a considerable challenge in terms of ensuring proper EDID communications and therefore reliable system operation.
For example, systems that employ RGBHV-based distribution have no means of passing EDID information from the display to the source. This could become problematic in system designs where laptops and computers with expectation of seeing EDID are connected into the system. Since EDID information is not being provided to these devices, some of the aforementioned EDID communication issues may occur.
Extron products include features to help prevent or solve many of them by properly managing EDID communications between sources and displays in AV systems. These features provide automatic and continuous EDID management with attached source devices, ensuring proper power-up and reliable output of content.
EDID Emulation is a feature of many Extron DVI and HDMI products, including switchers, distribution amplifiers, and matrix switchers. It maintains constant EDID communication with source devices by providing pre-stored EDID information for various signal resolutions. A user can select the desired signal resolution, and then the corresponding EDID block is conveyed to all attached source devices. This EDID information is constantly available to the sources, even in a switching application where inputs are regularly selected and de-selected. The output of the sources should match the native resolution of the intended display device.
EDID Minder is an advanced, Extron exclusive technology for EDID management. It encompasses EDID Emulation, but also incorporates an additional level of "intelligence." Extron products with EDID Minder can communicate with the display device, and automatically capture and store EDID information from the display. See Figure 3. This captured information can then be used as the reference EDID for the sources. EDID Minder is a standard feature in most Extron DVI and HDMI extenders, switchers, distribution amplifiers, and matrix switchers, as well as products that incorporate DVI or HDMI switching.
The functional role of a given product as a distribution amplifier, switcher, or matrix switcher determines the complexity of EDID Minder implementation. Matrix switching environments represent the most difficult EDID management situation, with simultaneous EDID communications required for multiple inputs and outputs. The displays connected to the outputs are very likely to be of different models and native resolutions. The EDID information between them is different and needs to be conveyed to the source devices. Proper EDID management within the system is crucial to consistent and reliable operation.
Extron HDMI and DVI matrix switchers with EDID Minder achieve this by managing EDID communications for each input/output tie. EDID Minder first analyzes the EDID for all displays connected to the system, applies a complex algorithm to determine a common resolution, refresh rate and color space, and then uses the EDID protocol to set up the input sources. This powerful convenience feature simplifies system setup for the integrator, helps ensure consistent and reliable image display, and makes system operation virtually transparent to the end user.
It looks like you may be using an outdated browser that we no longer support. Extron uses the latest technology to make its website faster and easier to use. For the best experience, please use one of these supported browsers:
In the process of setting up CRT TVs and monitors, I've often worked with modelines, the cryptic strings of numbers which define how a GPU should drive a display cable with rows of pixels. Once critical to 90's Linux users trying to setup XFree86 to display on their CRT monitors, modelines have found a new life among hobbyists who tinker with resolutions and framerates to bring out the full potential from their CRT and gaming LCD monitors. In this article I'll be exploring the origins and history of modelines, how they're used to hook computers up to CRT displays, and how I wrote a modeline generation tool and discovered multiple bugs in Xorg's cvt tool along the way.
7fc3f7cf58