Intel® Embedded Graphics Drivers specifically target the needs of embedded platform developers, offering a robust alternative to drivers designed for the desktop and mobile market segments. With a flexible architecture, extending to the video BIOS, and a new UEFI video driver, this driver set speeds customer time-to-market by allowing OEMs and system integrators to customize configurations in-house, while maintaining a competitive performance profile.Intel® Embedded Graphics Drivers have been validated on specific Linux. distributions and Microsoft Windows. operating systems. Based on the Intel product and operating system selection, the correct version of driver (10.4 or 10.3.1) is provided.Before downloading this driver, first review the Intel® Embedded Graphics Driver Feature Matrix & to determine the Intel® products and operating systems the driver supports. And the are two separate media and graphics drivers for embedded usage; Intel® EMGD is not a follow-on/next generation driver to IEGD.is a group of drivers that support a broad range of operating systems and chipsets.
The Intel® Embedded Graphics Drivers (IEGD) are developed specifically for embedded Intel® Architecture-based platforms, offering a flexible alternative to drivers designed for the desktop, mobile and MID market segments. IEGD offers Intel's embedded customers extended life support that correlates with the extended life support of embedded silicon products. IEGD differentiates itself through its configuration and support of unique embedded market segment requirements, including an unprecedented support of advanced display combinations and non-standard display dimensions (Intel® Dynamic Display Configuration Technology) and embedded operating systems such as Microsoft XP Embedded.
and Windows Embedded CE., while delivering comparable 3D performance to that of the Intel® Graphics Media Accelerator (GMA) graphics solution, and performance advantages to open source graphics solutions. Intel Embedded Graphics Drivers have also been validated on specific Linux.
distributions and Microsoft Windows. operating systems. The IEGD feature matrix, product brief and the User Guide lists which Linux.
distributions are proactively validated for a given chipset. If your “favorite Linux.” distribution is listed in the feature matrix, product brief and/or user guide then the IEGD driver should work. However, in the event the driver does not work perfectly on that distribution you should work with the “favorite Linux.” distribution company or your own in-house Linux. experts to determine root causes and debug any issues.If your “favorite Linux.” distribution is not listed in the feature matrix, product brief and/or user guide then the chance of the driver working is lower.
You can consider trying to install IEGD on a system with the help of your “favorite Linux.” Linux. distributor. However, a technical solution may not be possible.To better understand how the IEGD Linux. driver works (and how different kernel versions will affect the driver), you need to know how the IEGD Kernel Module (IKM) module is built. Currently, the install.sh script detects a limited set of known or validated Linux.
distributions and makes a copy of the relevant kernel headers for AGPGART and DRM. Stay tuned for a future white paper discussing the drivers’ Linux. integration methods. Intel® Atom™ processor D400/500, N400/500 series. Intel® Atom™ Z500 series with Intel® System Controller Hub US15W/WP/WPT. Intel® Atom™ N270 with Mobile Intel® 945GSE Express Chipset.
Intel® Q45, G41 and G45 Express chipsets. Mobile Intel® GM45, GL40 and GS45 Express chipsets. Intel® Q35 Express Chipset. Mobile Intel® GME965 and GLE960 Express chipsets. Intel® Q965 Express Chipset. Mobile Intel® 945GME Express Chipset. Intel® 945G Express Chipset.
Montevina California
Mobile Intel® 910GMLE and 915GME Express chipsets. Intel® 915GV Express Chipset. The Intel Embedded Graphics Drivers support multiple generations of Intel chipsets and/or system-on-a-chips (SoC) over the extended support span of Embedded Intel Architecture-based platforms, from the Mobile Intel® 910GMLE Express chipset forward to the Intel® System Controller Hub US15W chipset, based on the Embedded Intel® Architecture roadmap.
However, you must build a driver for each specific chipset or SoC you are using and you may need to update to a later version of IEGD to be able to build a driver for a newer chipset. The earliest chipset with integrated graphics that is supported by the Intel Embedded Graphics Drivers is the Intel® 815 chipset. The last release that supports the Intel® 815 chipset was the Intel Embedded Graphics Drivers release 5.1, which remains available through your Intel representative. The last release that supports the Intel® 845 chipset was the Intel Embedded Graphics Drivers release 6.1, which remains available through your Intel representative. The last release that supports the Intel® 852/855 chipset was the Intel Embedded Graphics Drivers release 8.1, which remains available through your Intel representative.The following Intel® GenX/Gen3/Gen4 chipsets are supported only by IEGD 10.3.1 which was the last validated drivers for these chipsets is available on EDC.
Intel® Q45, G41 and G45 Express chipsets. Mobile Intel® GM45, GL40 and GS45 Express chipsets.
Intel® Q35 Express Chipset. Mobile Intel® GME965 and GLE960 Express chipsets.
Intel® Q965 Express Chipset. Mobile Intel® 945GME Express chipset. Intel® 945G Express Chipset. Mobile Intel® 910GMLE and 915GME Express chipsets.
Intel® 915GV Express ChipsetPlease use the most recent Gold release (as of February 2011, the most recent release of IEGD is 10.4) of the Intel Embedded Graphics Drivers for following Intel products. The IEGD 10.4 is available on EDC. Yes, this is possible. The Intel Embedded Graphics Drivers provide the capability using the Configuration Editor to configure both the OS level driver and the Video BIOS with the same settings.
Although the Intel Embedded Graphics Drivers will utilize settings of the embedded Video BIOS, the OS-level drivers are not dependent on the Video BIOS settings. This allows users who may not have the ability to update their system firmware/system BIOS to install and use the Intel Embedded Graphics Drivers with their operating system.
Note that the Configuration Editor will not create settings for the standard desktop Video BIOS.If you require specific capability in the standard desktop Video BIOS in conjunction with the Intel Embedded Graphics Drivers, use Intel's BIOS Modification Program (BMP) tool to configure the standard desktop Video BIOS and CED (Configuration EDitor) to configure the IEGD driver. Contact your Intel representative for more details. Although not always required, it is generally recommended to upgrade both the VBIOS and driver when an update occurs. Intel tests using only the latest of both VBIOS and driver so there may be unexpected results.
Often there are code changes that you will want. Sometimes there are new features that require both to be updated. If after updating only the driver you see a negative change in operation, it is recommended that you then update the platform to the newer VBIOS as well.
This will allow you to verify that the negative operation of the driver was or was not related to some interaction with the older VBIOS. Added Multi GPU Multi-Monitor (formerly Hybrid Graphics) support for platforms based on the Intel Atom Z5xx Processor + Intel US15 System Controller Hub and External x1 PCI-Express graphics card. Refer to the, “Implementing Multiple Displays with IEGD Multi-GPU – Multi-Monitor Mode on Intel® Atom™ Processor with Intel® System Controller Hub US15W Chipset” for additional details. New Linux. AVAUTOPAINTCOLORKEY option integrated for AV which prevents erasure of other contents displayed in the desktop area.
IEDG 10.4 continues to automatically draw the colorkey before displaying the first video frame. Enabled driver support for all LVDS panels with a Data Enable (DE) signal and Data Enable mode supported by IEGD. Approximately tripled the boot/BLDK splash screen size with EPOG driver by implementing support of 8 bits per pixel.BPM format (originally was 24 bpp.BMP). Full-screen display of 1280x720 (720p), 1600x900, 1920x1080 (1080i & 1080p) resolutions in all officially supported Windows and Linux. IEGD operating systems now achieved via internal VGA and/or internal LVDS display controllers. This occurs so long as chipset hardware supports necessary pixel rate for desired resolution.
Some IEGD chipsets do not have integrated VGTA andor LVDS. Check the IEGD Feature Matrix for internal display controller(s) available.
Included VA API in IEGD to allow a vaPutSurface equivalent targeting video surface output as a Pixmap pointer as opposed to a drawable window. Increased DisplayID functionality; X&Y resolution settings now function equivalently via DisplayID (DID) or via EDID files. Enhanced CED application to allow display ID Settings to have priority over INF file settings. The driver fundamentally supports multi-threading. However some functions may not be multi-thread capable. Multi-threading in many instances is dependent on the software (OS/application) as well as the hardware (multi-processor/multithread capable) support capability For example, hardware video acceleration is designed as a single pipeline and although you can feed a single stream with multiple videos in it, you cannot interrupt the current thread in order to service another video decode thread/stream.
– Contains links to download the latest software, Intel® Embedded Graphics Drivers Feature Matrix, EFI Video Driver, an electronic FAQ with a detailed glossary, Video BIOS User Guide, and Product Brief for the Intel® Embedded Graphic Drivers. Additional information can be found on the Download Now, Chipset & OS Compatibility, Features, Frequently Asked Questions, and Overview tabs. – Search on the keyword “graphics” (in field in upper-right corner). (QuAD) – Contains a link for the IEGD 10.x Specification Update (Errata), however the site requires a login and password.
– Contains links to download the latest software, User Guide, Feature Matrix, and Product Brief for the Intel® Embedded Graphic Drivers. – Contains links for IEGD Drivers and an online FAQ. Additional information can be found on the Download Now, Frequently Asked Questions, and Overview tabs. (QuAD) – Contains links for the latest software Product Feature Matrix, User Guide, and Product Brief for customers who have a QuAD account.Then, after extracting the IEGD package, refer to the User Guide found in the C:IEGDIEGD10xworkspacedocumentation folder for instructions on video BIOS and how to configure and build the VBIOS with CED.
The IEGD Specification Update, User Guide and Release Notes are support documents for the driver. They tell customers what’s new with the graphics driver (Release Notes), how to install and use the graphics driver (User Guide) and known errors/defects with the graphics driver and workarounds (Specification Update), if any have been identified. These documents assist in the usage of IEGD.The IEGD API reference manual is more confidential because it conveys information about how the BIOS and IEGD work internally – the IEGD API. It also discusses the set of APIs for handling drivers on Microsoft.
Windows. and X Window, and sample programs for MS-DOS., Windows. XP, Windows. CE, and Linux.There is also information in the IEGD API reference manual about the standard video BIOS interfaces, function definitions, and supported modes. This document discloses information about the external interfaces to the video BIOS, the interrupt 10h-function descriptions, and additional interface components.Despite the additional layer of confidentiality associated with the IEGD API reference manual, it can still be downloaded by any approved user of EDC by accepting the click-through confidentiality login terms. UEFI stands for Unified Extensible Firmware Interface. UEFI is a replacement for Legacy System BIOS and is flexible, fast, and efficient and has no driver size constraints.
The UEFI Pre-boot Firmware architecture can either be 32-bit/64-bit/IA64. There is no binary compatibility. CSM (Compatibility Support Module) is used to boot legacy operating systems and operate with legacy Option ROMs.IEGD supports the EFI driver, which gets merged into the UEFI system Pre-boot Firmware. The EFI driver supports fast boot capability. EPOG stands for Embedded Pre-OS Graphics feature.
EPOG was first supported with the IEGD 10.2 Gold release. This driver is a module within the Boot Loader Development Kit (BLDK).EPOG is configured using CED. CED provides a file called libepog.a, which must be integrated into the firmware.
The EPOG feature enables quick display of the user’s chosen splash screen (8-bit or 24-bit per pixel.bmp format with size less than 50KB). Splash screens are often used to display corporate logos.
The current EPOG driver supports a static splash screen only. Industry suppliers can also provide splash video but this is not currently implemented by Intel.From the time control is handed over to the EPOG driver by the BLDK environment, the EPOG driver typically takes no longer than 500ms to display the splash screen.
The GOP driver is a replacement for legacy video BIOS and enables the use of UEFI Pre-boot Firmware without Compatibility Support Module (CSM). GOP driver can be 32-bit/64-bit/IA64 with no binary compatibility. UEFI Pre-boot Firmware architecture (32-/64-bit) must match the GOP driver architecture (32-/64-bit). IEGD GOP driver can either be Fast Boot (speed optimized and platform specific) or generic (platform agnostic for selective platforms).Here is a quick comparison between GOP and video BIOS. CED is a Windows XP-compatible Graphical User Interface “point and click” application configuration editor for the Intel Embedded Graphics Drivers. It replaces the more cumbersome and manual PCF configuration method of configuring and building IEGD.
It helps make setting up and building the various driver elements including VBIOS much easier. It replaces the PCF/PCF2IEGD configuration process. Online help and logically grouped features, plus error checking assure your configuration is right the first time built.The Configuration EDitor (CED) allows easier pre-installation configuration and generation of the drivers and VBIOS.Note: Although CED can be used to build IEGD drivers for any target operating systems listed below, the CED application runs only under Windows XP on the host platform. Sometimes, for debugging purposes, you would like to know which configuration file is generated by CED. By having access to the config file generated by CED (iegd.inf, xorg.conf, userconfig.c, iegd.reg) you can rule out configuration issues. This feature is also useful when you just need the configuration file (especially in VBIOS) and not the whole driver / VBIOS package.
Go to the folder where you installed CED; usually in C:IEGDIEGD10. Open iegd-ced.ini. Type '-showFiles'. This command is case-sensitive. Save the file. Open CED and follow the standard procedure to generate the package. The config file should be visible in the package folder.
The software does not impose any limits; however, developers need to be sure the chipset’s design specs are not violated. The minimum pixel clock frequency supported and validated on the Intel® System Controller Hub US15W chipset is 20 MHz. The minimum standard active resolution is therefore 640x480 @ 50 Hz vertical refresh which equates to 20 MHz pixel clock. It may be possible to pad the horizontal and vertical blanking and adjust the refresh rate higher to get a lower resolution at the minimum 20 MHz pixel clock, but that is something that needs to be explored with the LCD panel manufacturer. Theoretically, any timing mode that yields a pixel clock frequency between 20 MHz. (maximum allowable pixel clock frequency for US15W internal LVDS controller) can be supported by IEGD and US15W. The minimum pixel clock frequency supported by the US15W sDVO interface is 20 MHz.
The minimum standard active resolution is therefore 640x480 @ 50 Hz vertical refresh which equates to 20 MHz.The maximum pixel clock frequency supported by the US15W sDVO interface is 160 MHz. The maximum standard active resolution is therefore 1920x1080 @ 60 Hz vertical refresh which equates to 148.5 MHz. Common high resolutions such as 1600x1200 and 1280x1024 are also supported since they possess pixel clock rates less than 160 MHz.Any timing mode that yields a pixel clock frequency that is between 20 MHz. Can be supported by IEGD and US15W via sDVO. Check your chosen sDVO device vendor’s data sheet for limitations of the display output. Most VGA and TV encoders cannot support analog CRT, HDTV, and SDTV outputs whose pixel clock rates exceed 80 MHz.Additional details on the graphics capabilities of the Intel® System Controller Hub US15W chipset can be found here.
This is typically a configuration or port driver issue. The sDVO port must be properly configured prior to installation of the driver. It is most important that the address of the sDVO device is set correctly if it is different from the default of 0x70.
There also are settings that allow you to specify certain attributes, depending on what sDVO device you are using. For example, for VGA operation, it is important to set the “VGA Bypass” or “VGA Output” attribute on some VGA sDVO devices to get VGA output. See the User Guide for more information. “Switchable” allows seamless transition between the integrated graphics in the chipset and a higher power “external” graphics engine for best battery power capability. This is a feature you would expect to find in a battery operated device such as a notebook.“Additive” is a technique where the integrated graphics GPU is tapped by the “external” graphics driver to supplement the external graphics GPU processing power.
This feature is of limited value as the overhead on managing the data and transferring the graphics data between the integrated graphics memory and the external graphics tends to override any performance benefits.“Multi-Monitor” is the ability for the integrated graphics to co-exist with the external graphics engine(s) allowing for more unique displays. For example, in Windows you could extend your desktop between the integrated graphics’ two displays plus one, two, or more external graphics displays. This requires a chipset tested to support this mode, and possibly a BIOS modification to leave the integrated graphics on when external graphics are present, especially in the X16 PCIe (PEG) slot.IEGD has always supported Multi-Monitor mode which, in the past, was primarily tested with integrated graphics plus PCI-based external graphics. With the new ability to use the integrated plus PCIe plus PCI, the combinations are endless. IEGD does not officially include Hybrid multi-monitor support for systems using the US15W chipset at the present time.Several retail platforms based on the US15W chipset and IEGD have successfully enabled unique display timings on greater than two panels or monitors simultaneously.
However, much like over clocking the GPU beyond datasheet specifications, enabling Hybrid multi-monitor support with US15W is done at the board vendor’s risk.Intel’s IEGD 10.3.1 Product Brief and IEGD 10.3.1 Feature Matrix currently list the US15W as not supported for Hybrid multi-monitor graphics using IEGD. The CH7318 is a level shifter device for HDMI.
This is not a transmitter device but it provides voltage shifting. The IEGD-supported Series 4 chipsets (Q45/G45/G41/GM45/GS45/GL40) that have integrated HDMI/DVI require only a level shifter to increase the internal voltage to the necessary line voltage. Since IEGD supports some of the Series 4 chipsets (Q45/G45/G41/GM45/GS45/GL40), and the internal HDMI/DVI interfaces that are available, it also supports the necessary level shifters, but not directly. The driver is not aware that the level shifter (for example, the CH7318) is present. Because it is not a transmitter, only a level shifter, it is theoretically invisible to the driver. The driver only knows that there is a DVI or HDMI interface configured. When setting up the IEGD driver with CED, you are not choosing sDVO and then looking for a device labeled CH7318; you are configuring the HDMI interfaces and the additional data to get these interfaces up and running.