1. What display configurations support desktop rotation by Intel® Embedded Graphics Drivers and the Intel® System Controller Hub US15W chipset?
Intel® Embedded Graphics Drivers support desktop rotation through the “Rotation” function using the Intel Embedded Graphics Drivers graphical user interface (GUI) tool in Single, Clone, and Extended mode configurations. Refer to the user guide for a list of rotation instructions and operating system limitations.
2. Does the Intel® System Controller Hub US15W chipset with Intel® Embedded Graphics Drivers offer dedicated hardware support for DirectX* 9.0Ex and OpenGL* 2.0?
3. What are some of the high-level differences between the Intel open source Linux* graphics driver and the Intel Embedded Graphics Drivers for Linux?
The Intel Embedded Graphics Drivers:
4. Does internal low voltage differential signaling (LVDS) support both Standard Panels Working Group (SPWG) and OpenLDI* data formats?
No, internal LVDS in all current mobile chipsets only supports SPWG data formats. Other transmitters that support LVDS can support both via port driver attribute 49.
5. What third-party serial DVO (SDVO) devices do Intel Embedded Graphics Drivers support?
Intel Embedded Graphics Drivers support a variety of SDVO devices from Chrontel* and Silicon Image* for HDMI*, DVI, TVOut, VGA/CRT, and LVDS via the chipset’s internal SDVO port. Refer to the user guide, plan of record (POR) update, and product brief for an up-to-date list of supported devices.
6. Do Intel Embedded Graphics Drivers support sharing of I2C* bus across multiple SDVO devices?
Yes, but the “Data Address Byte” of the SDVO devices should be different. Check the user guide for more information on how to configure them. Please note that for two-transmitter support it is critical to specify the I2CDAB hardware address option in the configuration for each one. Typically SDVO devices will be found on port 70h and 72h, but your hardware may vary. In the Configuration EDitor (CED), the configuration option will be found on the SDVO Configuration page under the “I2C Settings” button in the I2C Bus Configuration section. Specify your addresses in each device's “Device Address Byte” box.
7. What drawing functions are accelerated in the Intel Embedded Graphics Drivers?
See the user guide for more information.
8. How do I change or increase the memory graphics used? Do the Intel Embedded Graphics Drivers allow runtime changes?
On a Microsoft Windows XP/eXP* system, this can be done from SysBIOS. For X-Server* this should be done from xorg.conf. See the user guide for more information.
9. What Shader Model* level does the graphics core of the Intel® System Controller Hub US15W chipset provide?
The Intel® System Controller Hub US15W chipset supports Shader Model level 2.0 with some minor restrictions.
10. Does this Intel Embedded Graphics Driver support OpenGL*?
Yes, most if not all chipsets are supported on Linux 2.6 kernel Linux distributions, and in Windows on the Intel® System Controller Hub US15W chipset as detailed in the Intel Embedded Graphics Drivers v10.2 User Guide, POR Update, and Product Brief.
11. What is EDID and how does it work?
EDID stands for Extended Display Information Data, one of the Video Electronics Standards Organization (VESA) body of standards that allow for a display or monitor to provide information back to the driver for proper display resolution, mode setup, and configuration.
CRT/VGA monitors exchange EDID information over the I2C bus with Intel® Embedded Graphics Drivers so the driver generates only display modes and timings that are compatible with the monitor to which it is connected.
Some LVDS panels do not allow for exchange of EDID information; these displays are called “EDID-less” and require custom detailed timing descriptor (DTD) timings to be generated via CED.
12. Where can I find information about which versions, application programming interface (API) calls, and features Intel® Embedded Graphics Drivers support for OpenGL*?
See the User Guide, Appendix D for information on support for OpenGL* and OpenGL ES*.
13. What are the differences between OpenGL and OpenGL ES?
Two of the more significant differences between OpenGL ES and OpenGL are the removal of the glBegin–glEnd calling semantics for primitive rendering (in favor of vertex arrays) and the introduction of fixed-point data types for vertex coordinates and attributes to better support the computational abilities of embedded processors, which often lack a floating point unit (FPU).
14. Does Intel have any plans to provide PhysX* support on any product?
No. Intel believes acceptable platform solutions exist without implementing NVIDIA proprietary technologies, such as PhysX, CUDA*, and so on.
15. Is the OpenVG* API supported by Intel® Embedded Graphics Drivers?
No. However, OpenVG* is supported by the newer Intel® Embedded Media and Graphics Driver (Intel® EMGD) driver. For more information regarding OpenVG, please review this page: http://en.wikipedia.org/wiki/Openvg.
16. Can users implement dynamic backlight control through pulse width modulation (PWM) using the Intel® Embedded Graphics Drivers?
Yes, it is possible for users to have an application that dynamically controls the LVDS backlight, but you first need to make sure that the platform or board being used can control the backlight using PWM. The LVDS connectors need to be hooked up to the PWM inverter.
Then you need the Intel® Embedded Graphics Drivers that can program the PWM that controls the LVDS backlight. Currently, both Intel® Embedded Graphics Drivers and Intel EMGD can support LVDS PWM on the Intel® System Controller Hub US15W chipset and Tunnel Creek board. It is not confirmed whether the codes have been ported for the Intel® Atom™ processor 400 and 500 series. The driver takes in two config inputs to enable PWM. One is the frequency of the inverter, and the other is the maximum intensity of the LVDS panel in percentage. Intel® Embedded Graphics Drivers and Intel EMGD normally set the maximum intensity to 100 percent, but configuring this parameter will set the maximum panel intensity, not the default startup intensity. What this means is that no matter what you do, the brightest setting you can achieve is what you configure in the driver.
The third part is the user application that controls the intensity of the LVDS. If you have the PCI config spec of the Intel® Atom™ processor 400 and 500 series, go to the display device (PCI device 2) section and see the PCI configuration register. Find an entry called LEGACY Backlight Brightness (LBB). On Intel® System Controller Hub US15W chipset, it is offset 0xF4 to 0xF7. You will need to write an application that writes to this PCI config space. You will need to see the Intel® Atom™ processor 400 and 500 series spec that applies to Tunnel Creek. Bit 0:7 controls the brightness of LVDS backlight. It has 255 levels of brightness. But bear in mind that the settings on the driver (mentioned in the paragraph above) will set the maximum brightness. This means if you set the max to 50%, even if you set the LBB to 255, it will be 50% intensity.
You can then create an application using sliders, and so on to modify the LBB value which will control the backlight.
17. Do Intel® Embedded Graphics Drivers support the Microsoft Silverlight* web application framework that integrates multimedia, graphics, animations, and interactivity into a single runtime environment?
Intel® Embedded Graphics Drivers do not currently support Microsoft Silverlight* dedicated acceleration. However, Intel® Embedded Graphics Drivers do accelerate many of the basic features and functions that Silverlight uses. For Windows, Intel® Embedded Graphics Drivers accelerate DirectX* (and WPF) and, for Linux, accelerates OpenGI*/GLES. In summary, Intel® Embedded Graphics Drivers currently have no specific Silverlight acceleration, but Silverlight works on top of the operating systems that Intel® Embedded Graphics Drivers are accelerating.