For automatically identify, fixes missing and updating Intel Graphics device drivers, Install the latest official drivers and keep your Intel Graphics device drivers.
After upgrading to Windows 10, if you are having issue with Intel HD Graphics driver, you may not watch videos or play games as usual, and the PC may run slowly. To fix the issue, read on to find the solutions. You can resolve the issue by updating the Graphics driver. There are 3 ways you can use to update the driver. Not every way works in all situations. You can start at the top of list and work your way down.
- If you have Intel(R) HD Graphics driver issue after upgrading your system to Windows 10. Don’t worry about that. Here you can find the solutions to fix it.
- Intel Drivers Download by Intel. Drivers for Intel USB Drivers for Intel Video / Graphics Drivers for Intel. From our list of Intel Drivers by Device.
Way 1: Update your Intel(R) HD Graphics driver manually Intel has released Windows 10 drivers for their vast majority of display cards. You can go to and find the right driver. Please make sure you find the right version, as incompatible or wrong driver can cause serious PC problems. After downloading the driver, if you cannot install the driver successfully by just double-clicking the installer file. You follow steps below to update the driver manually step by step. Open Control Panel by typing control panel in search box and clicking Control Panel on the pop-up menu. View by Small icons.
Click Device Manager. In Device Manager, expand category Display adapters. Right click on the Intel device and select Update Driver Software 4. Click Browse my computer for driver software. Click Browse button, and navigate to the location where you save the downloaded driver file. Then follow the on-screen instructions to install the driver. Way 2: Use Windows Update for new drivers Refer steps below to use Windows Update in Windows 10 to update drivers. Click Start menu and click Settings. In Settings Window, click Update & security.
In UPDATE & SECURITY, click Windows Update in left pane. In right pane, click Check for updates, and then wait while Windows is searching for the latest updates.
Click the link that tells you optional updates are available. (If you don’t see this link, it means Windows Update didn’t find any updates for your computer.) 5. Select the driver you want to install, click OK, and then click Install updates.
Way 3: Automatically Update the driver If Way 1 and Way 2 don’t work for you, or if you’re not confident playing around with drivers manually, you can do it automatically with. Driver Easy will automatically recognize your system and find the correct drivers for it. You don’t need to know exactly what system your computer is running, you don’t need to risk downloading and installing the wrong driver, and you don’t need to worry about making a mistake when installing. You can update your drivers automatically with either the FREE or the Pro version of Driver Easy. But with the Pro version it takes just 2 clicks (and you get full support and a 30-day money back guarantee): 1) and install Driver Easy.
2) Run Driver Easy and click Scan Now button. Driver Easy will then scan your computer and detect any problem drivers. 3) Click the Update button next to a flagged Intel graphics card driver to automatically download and install the correct version of it (you can do this with the FREE version). Or click Update All to automatically download and install the correct version of all the drivers that are missing or out of date on your system (this requires the Pro version – you’ll be prompted to upgrade when you click Update All). My Lenovo desk top has a Intel HD Graphics 2000 card.
I upgraded to Windows 10 last year and have had no problems, however about two weeks ago after a Microsoft update all the settings on my display changed to 1366×768. This is not acceptable as everything is now a bit fuzzy.
Microsoft says Lenovo should provide a Windows 10 updated driver, Lenovo says Intel has not updated the series 2000 and blame Windows for the update. There is no update at Intel. Lenovo and Microsoft suggest going back to windows 7.
Bit late to roll back. Any idea if your Driver tool can provide a updated for Windows 10 Intel series 2000 driver.
Data and instructions are sent to the for processing. The rendered results are stored in a, whose content is scanned by the and sent to the screen. A free and open-source graphics device driver is a which controls and supports (APIs) and is released under a license. Graphics are written for specific hardware to work within a specific and to support a range of APIs used by applications to access the graphics hardware. They may also control output to the display if the is part of the graphics hardware.
Most free and open-source graphics device drivers are developed by the project. The driver is made up of a, a, and software which manages access to the graphics hardware. Drivers without freely (and legally) -available source code are commonly known as binary drivers. Binary drivers used in the context of operating systems that are prone to ongoing development and change (such as Linux) create problems for end users and maintainers. These problems, which affect system stability, security and performance, are the main reason for the independent development of free and open-source drivers. When no technical documentation is available, an understanding of the underlying hardware is often gained.
Based on this understanding, device drivers may be written and legally published under any. In rare cases, a manufacturer's driver source code is available on the Internet without a. This means that the code can be studied and altered for personal use, but the altered (and usually the original) source code cannot be freely distributed. Solutions to bugs in the driver cannot be shared, significantly reducing the utility of such drivers in comparison to free and open-source drivers. Illustration of the Linux graphics stack There are objections to binary-only drivers based on copyright, security, reliability and development concerns. As part of a wider campaign against, lead developer said that with a binary driver there is 'no way to fix it when it breaks (and it will break)'; when a product which relies on binary drivers is declared to be by the manufacturer, it is effectively 'broken forever.' The project has also stated that binary drivers 'hide bugs and workarounds for bugs', an observation which has been somewhat vindicated by flaws found in binary drivers (including an in Nvidia's 3D drivers discovered in October 2006 by ).
It is speculated that the bug has existed since 2004; Nvidia have denied this, asserting that the issue was only communicated to them in July 2006 and the 2004 bug was a bug in X.Org (not in Nvidia's driver). Binary drivers often do not work with current versions of open-source software, and almost never support development snapshots of open-source software; it is usually not directly possible for a developer to use Nvidia's or ATI's proprietary drivers with a development snapshot of an X server or a development snapshot of the Linux kernel. Features like cannot be added to binary drivers by anyone but the vendors, which prevents their inclusion if the vendor lacks capacity or interest. In the development community, has made strong statements on the issue of binary-only modules: 'I refuse to even consider tying my hands over some binary-only module. I want people to know that when they use binary-only modules, it's their problem'.
Another kernel developer, has said that a binary-only kernel module does not comply with the kernel's license (the ); it 'just violates the GPL due to fun things like derivative works and linking and other stuff.' Writer and computer scientist has expressed concern that the scheme in Microsoft's operating system may limit the availability of the documentation required to write open drivers, since it 'requires that the operational details of the device be kept confidential.' In the case of binary drivers, there are objections due to philosophy, software quality and concerns.
There are also concerns that the redistribution of closed-source Linux kernel modules may be illegal. The Linux kernel has never maintained a stable in-kernel. There are also concerns that proprietary drivers may contain, like the one found in -series modem drivers. Hardware developer's view. In the future, could use the of the Radeon open-source driver instead of the proprietary; most of the investment is in the userspace driver.
When applications such as a 3D or a shunt calculations from the CPU to the GPU, they usually use a special-purpose API like or and do not address the hardware directly. Because all (from API calls to GPU ) is done by the device driver, it contains specialized knowledge and is an object of optimization. This takes time and money. Leakage of device-driver source code (whether published under a free license or not) can give competitors an advantage — especially newcomers to graphic acceleration, who would gain considerable knowledge without bearing the costs of developing the knowledge. The market was long dominated by PC hardware using the / instruction set and GPUs available for the PC. With three major competitors (Nvidia, AMD and Intel).
The main competing factor was the price of hardware and raw performance in 3D computer games, which is greatly affected by the efficient translation of API calls into GPU opcodes. The display driver and the are inherent parts of the graphics card: hardware designed to assist in the calculations necessary for the decoding of video streams. As the market for PC hardware has dwindled, it seems unlikely that new competitors will enter this market and it is unclear how much more knowledge one company could gain by seeing the source code of other companies' drivers. The mobile sector presents a different situation.
The functional blocks (the display driver, 2- and 3D acceleration and video decoding and encoding) are separate (SIP) blocks on the chip, since hardware devices vary substantially; some require a display driver that accelerates video decoding, but do not require 3D acceleration. The development goal is not only raw 3D performance, but system integration, power consumption and 2D capabilities. There is also an approach which abandons the traditional method of updating the display and makes better use of technology to lower power consumption. During the second quarter of 2013 79.3 percent of sold worldwide were running a version of, and the Linux kernel dominates smartphones. Hardware developers have an incentive to deliver Linux drivers for their hardware but, due to competition, no incentive to make these drivers free and open-source. Additional problems are the Android-specific augmentations to the Linux kernel which have not been accepted in, such as the (ADF).
ADF is a feature of 3.10 AOSP kernels which provides a -centric framework between Android's hwcomposer and the kernel driver. ADF significantly overlaps with the - framework.
ADF has not been accepted into mainline, but a different set of solutions addressing the same problems (known as ) is under development. Projects such as harness Android device drivers to run on Linux platforms other than Android. Cue list. This section does not any. Unsourced material may be challenged and. (November 2017) Device drivers are the abstraction layer between software concepts and hardware circuitry.
They are a standard interface to peripherals, hiding the details of how the circuitry solves things from the programmer. Almost any system operation eventually maps to a physical device. The kernel embeds device drivers for every peripheral in the computer system.
Device drivers have seven times the bug rate of other. Performance comparisons. Glxgears is not well-suited for., which compares free drivers, is a source for real-world testing:.
19 March 2011. 31 March 2013.
A 29 April 2013 comparison of FOSS and proprietary drivers. A 27 October 2013 comparison of proprietary drivers on Windows 8.1 and Linux. A 25 January 2014 comparison of FOSS drivers on Linux.
A 27 January 2014 comparison of proprietary drivers on Linux. A 19 March 2014 comparison of with the Free and open-source graphics device driver distributed as part of, which outperforms 10.9.2 when playing -based on a 2013. A January 2017 comparison indicated a difference in power between the Mesa Nouveau and NVidia driver and Kepler and Maxwell. Reclocking is needed for Maxwell in Nouveau to increase level to Kepler. A gap to Mesa exists by 30 to 50% in basic efficiency of driver against Nvidia in all chips.
A February 2017 comparison indicated that Mesa 17.1dev was equal to or better than the AMD GPU driver 16.60 in OpenGL and 20-30 percent lower in. A March 2017 comparison indicated improvements in Mesa for RadeonSI between versions 11.1 and 17.1. A June 2017 Comparison Windows 10 Radeon Software vs. Ubuntu 17.04 + Linux 4.12 + Mesa 17.2-dev - Result mesa radeonsi at same level. A October 2017 Comparison RadeonSI/RADV Mesa 17.3 + AMDGPU DC vs. The proprietary NVIDIA 387.12 Linux Gaming Performance - Result: Nvidia clear in lead. 2018-02: Comparison Mesa 12 to 18 with AMD R580 and R9 Fury for OpenGL and Vulkan Tests It is uncommon for to report benchmark testing on Linux.
Benchmarks on Phoronix are limited in scope: primarily test games which are available on Linux and support automated benchmarking. Software architecture. An example matrix of the Gallium3D driver model. With the introduction of the Gallium3D tracker and WinSys interfaces, 18 modules are required instead of 36.
Each WinSys module can work with each Gallium3D device driver module and each State Tracker module. Free and open-source drivers are primarily developed on and for by Linux kernel developers, third-party programming enthusiasts and employees of companies such as. Each driver has five parts:. A Linux kernel component. A Linux kernel component (the driver). A libDRM user-space component (a wrapper library for DRM system calls, which should only be used by Mesa 3D).
A user-space component. This component is hardware-specific; it is executed on the CPU and translates OpenGL commands, for example, into machine code for the GPU. Because the device driver is split, is possible.
Mesa 3D is the only free and open-source implementation of, and. In July 2014, most of the components conformed to specifications. A fully functional State Tracker for version 9 is written in, and an unmaintained tracker for Direct3D versions 10 and 11 is written in. Has Direct3D version 9. Another Wine component translates Direct3D calls into OpenGL calls, working with OpenGL. (DDX), another 2D graphics device driver for The is -specific. A driver is generally available for any operating system.
The VESA driver supports most graphics cards without acceleration and at display resolutions limited to a set programmed in the video by the manufacturer. History The Linux graphics stack has evolved, detoured by the. Linux device drivers for AMD hardware in August 2016 proprietary driver, for their, is available for Microsoft Windows and Linux (formerly fglrx).
A current version can be downloaded from AMD's site, and some Linux distributions contain it in their repositories. It is in the process of being replaced with an AMDGPU-PRO hybrid driver combining the open-source kernel, X and Mesa multimedia drivers with closed-source OpenGL, OpenCL and Vulkan drivers derived from Catalyst.
The FOSS drivers for -AMD GPUs are being developed under the name Radeon (xf86-video-ati or xserver-xorg-video-radeon). They still must load proprietary microcode into the GPU to enable hardware acceleration. Radeon 3D code is split into six drivers, according to GPU technology: the radeon, r200 and r300 classic drivers and r300g, r600g and radeonsi drivers:. Radeon supports the series. R200 supports the series.
R300g supports pre- microarchitectures:, and. R600g supports all -based GPUs:, and. Radeonsi supports all -based GPUs:, and (Southern Islands, Sea Islands and Vulcanic Islands). An up-to-date feature matrix is available, and there is support for and.
The free and open-source Radeon graphics device drivers are not reverse-engineered, but are based on documentation released by AMD without the requirement to sign a (NDA). Documentation began to be gradually released in 2007. This is in contrast to AMD's main competitor in the graphics field, which has a proprietary driver similar to but provides no support to free-graphics initiatives. In addition to providing the necessary documentation, AMD employees contribute code to support their hardware and features. At the 2014, The company announced that they were exploring a strategy change to re-base the user-space part of Catalyst on a free and open-source kernel module instead of their proprietary kernel. All components of the Radeon graphics device driver are developed by core contributors and interested parties worldwide.
In 2011, the r300g outperformed Catalyst in some cases. Amdgpu The release of the amdgpu stack was announced on the dri-devel mailing list in April 2015. Although the driver is developed on GCN 1.1 graphics cards, it is enabled only for GCN 1.2 graphics cards; GCN 1.0 and 1.1 graphics cards are supported by the Radeon driver. Regarding the naming of the involved microarchitectures consult. A separate, libdrm-amdgpu, has been included since libdrm 2.4.63. Screenshot of REnouveau, a program which collects data for most of Nnouveau's reverse-engineering work 's proprietary driver, for, is available for - and later, x86-x86-64-, and later, x86-x86-64 and x86/x86-64.
A current version can be downloaded from the Internet, and some Linux distributions contain it in their repositories. The 4 October 2013 Nvidia GeForce driver 331.13 supports the interface, enabling support for in conjunction with this driver. Nvidia's free and open-source driver is named nv. It is limited (supporting only 2D acceleration), and, and others have called its source code confusing. Nvidia decided to deprecate nv, not adding support for or later GPUs and, in March 2010. In December 2009, Nvidia announced they would not support free graphics initiatives.
On 23 September 2013 The company announced that they would release some documentation of their GPUs. Nouveau is based almost entirely on information gained through.
This project aims to produce 3D acceleration for X.Org/ using. On March 26, 2012, Nouveau's component was marked stable and promoted from the staging area of the Linux kernel. Nouveau supports - (and earlier), -, - and -based GPUs. On 31 January 2014, Nvidia employee Alexandre Courbot committed an extensive patch set which adds initial support for the GK20A to Nouveau. In June 2014, Codethink reportedly ran a -based with 3.15, using and a '100% open-source graphics driver stack' on a. A feature matrix is available.
In July 2014, Nouveau was unable to outperform the Nvidia GeForce driver due to missing re-clocking support. Tegra-re is a project which is working to reverse-engineer nVidia's -based series of GPUs that predate Tegra K1. Nvidia distributes proprietary device drivers for Tegra through OEMs and as part of its Linux for Tegra (formerly L4T) development kit.
Nvidia and a partner, were working on submitting Grate (free and open-source drivers for Tegra) upstream of the mainline Linux kernel in April 2012. The company's co-founder and CEO laid out the Tegra processor roadmap with Ubuntu Unity at the 2013. Nvidia's Unified Memory driver (nvidia-uvm.ko), which implements memory management for Pascal and Volta GPUs on Linux, is MIT licensed. The source code is available in the Nvidia Linux driver downloads on systems that support nvidia-uvm.ko. Retrieved 2014-07-15. Archived from on 2014-02-01. Retrieved 2014-07-15.
INF Update Utility
Opposed to such obfuscated code. We do not regard this as free software according to our standards. (PDF). Retrieved 2014-07-15. Retrieved 2013-09-24. Mayo, Jon (2012-04-20).
Dri-devel (Mailing list). Retrieved 2012-08-21. Larabel, Michael (2012-04-11). Phoronix Media. Retrieved 2012-08-21.
Retrieved 2013-07-10. See also:, and has a history of producing (or commissioning) open-source drivers for its graphics chips, with the exception of their chips. Their 2D X.Org driver is called xf86-video-intel. The kernel mode-setting driver in the Linux kernel does not use the for switching; since some BIOSes have a limited range of modes, this provides more reliable access to those supported by Intel video cards.
Graphics Drivers
Unlike the Radeon and Nouveau drivers, Intel does not intend to utilize the framework for its graphics drivers. The company worked on optimizing their free drivers for performance approaching their counterparts, especially on and newer hardware (where performance optimizations have allowed the Intel driver to outperform their proprietary Windows drivers in certain tasks, in 2011. Some of the performance enhancements may also benefit users of older hardware. Support for Intel's LLC (Last Level Cache, L4-Cache, and Iris Pro) was added in Linux kernel 3.12, and the company has 20 to 30 full-time Linux graphics developers. Matrox develops and manufactures the, and.
Although the company provides free and open-source drivers for their chipsets which are older than the G550; chipsets newer than the G550 are supported by a closed-source driver. S3 Graphics develops the, and, supported by OpenChrome. Arm Holdings is a semiconductor company which licenses. Although they are known for the licensing the and based on it, they also develop and license the of GPUs. On January 21, 2012, reported that was driving a reverse-engineering attempt aimed at the Arm Holdings Mali series of GPUs (specifically, the Mali-200 and Mali-400 versions). The reverse-engineering project, known as Lima, was presented at on February 4, 2012.
On February 2, 2013, Verhaegen demonstrated in timedemo mode, running on top of the Lima driver. ARM has indicated no intention of providing support for their graphics acceleration hardware licensed under a free and open-source license.
However, ARM employees sent patches for the Linux kernel to support their ARM HDLCD and Mali DP500, DP550 and DP650 SIP blocks in December 2015 and April 2016. Imagination Technologies is a fabless semiconductor company which develops and licenses, among which are the GPUs. Intel has manufactured a number of GPUs. PowerVR GPUs are widely used in mobile. The company does not provide a FOSS driver or public documentation for the PowerVR.
Due to its wide use in embedded devices, the has put reverse-engineering of the PowerVR driver on its high-priority project list. See also: is a fabless semiconductor company which licenses and develops the GCxxxx series of GPUs.
A Vivante proprietary, closed-source Linux driver consists of kernel- and user-space parts. Although the kernel component is open-source , the user-space components—consisting of the GLES(2) implementations and a HAL library—are not; these contain the bulk of the driver logic. Van der Laan found and documented the state bits, command stream and ISA by studying how the blobs work, examining and manipulating command-stream dumps. The Etnaviv Gallium3D driver is being written based on this documentation. Van der Laan's work was inspired by the Lima driver, and the project has produced a functional-but-unoptimized Gallium3D LLVM driver.
The Etnaviv driver has performed better than Vivante's proprietary code in some benchmarks, and it supports Vivante's GC400, GC800, GC1000, GC2000, and GC3000 series. In January 2017, Etnaviv was added to with both OpenGL ES 2.0 and Desktop OpenGL 2.0 support. Qualcomm. See also: develops the (formerly ATI Imageon) GPU series, and includes it as part of their. And reported in 2012 that Rob Clark, inspired by the Lima driver, was working on reverse-engineering drivers for the Adreno GPU series. In a referenced blog post, Clark wrote that he was doing the project in his spare time and that the Qualcomm platform was his only viable target for working on open 3D graphics. His employers ( and ) were affiliated with the and cores, which would have been his primary targets; he had working command streams for 2D support, and 3D commands seemed to have the same characteristics.
The driver code was published on 'freedreno', and has been moved to Mesa. In 2012, a working shader assembler was completed; demonstration versions were developed for and, using the reverse-engineered shader compiler. Clark demonstrated Freedreno running desktop compositing, the media player and at on February 2, 2013. In August 2013, the kernel component of freedreno (MSM driver) was accepted into mainline and is available in Linux kernel 3.12 and later. The gained support for server-managed requiring version 1.16 and above in July 2014.
In January 2016, the Mesa Gallium3D-style driver gained support for Adreno 430; in November of that year, the driver added support for the Adreno 500 series. Freedreno can be used on devices such as and in traditional Linux distributions (like and ) and on. Broadcom. The Mesa driver for VideoCore4, VC4, was written from scratch by Broadcom's Eric Anholt. Develops and designs the GPU series as part of their. Since it is used by the, there has been considerable interest in a FOSS driver for VideoCore.
The Raspberry Pi Foundation, in co-operation with Broadcom, announced on October 24, 2012 that they open-sourced 'all the ARM (CPU) code that drives the GPU'. However, the announcement was misleading; according to the author of the reverse-engineered Lima driver, the newly open-sourced components only allowed message-passing between the ARM CPU and VideoCore but offered little insight into Videocore and little additional programability.
The Videocore GPU runs an which handles the processing; video acceleration is done with RTOS firmware coded for its proprietary GPU, and the firmware was not open-sourced on that date. Since there was neither a targeting the proprietary GPU nor a documented, no advantage could be taken if the firmware source code became available. The Videocoreiv project attempted to document the VideoCore GPUs. On February 28, 2014 (the Raspberry Pi's second anniversary), Broadcom and the Raspberry Pi Foundation announced the release of full documentation for the VideoCore IV graphics core and a complete source release of the graphics stack under a.
The free-license 3D graphics code was committed to Mesa on 29 August 2014, and first appeared on Mesa's 10.3 release. Open Graphics Project prototype Project VGA aims to create a low-budget, open-source -compatible video card. The aims to create an open-hardware GPU. The Open Graphics Device v1 has dual DVI-I outputs and a 100-pin IDC connector. In September 2010, the first 25 OGD1 boards were made available for grant application and purchase.
The, targeted at embedded graphics instead of desktop computers, supports a VGA output, a limited vertex shader and a 2D texturing unit. The Nyuzi, an experimental GPGPU processor, includes a synthesizable hardware design written in, an instruction set emulator, an -based C-C compiler, software libraries and tests and explores parallel software and hardware. It can run on a Terasic DE2-115 board. If a project uses FPGAs, it generally has a partially (or completely) closed-source toolchain. There are relatively few FPGAs with completely open-source toolchains. See also. (2006-12-03).
Presentation slides from OpenCON 2006. Retrieved 2007-02-01.
Retrieved November 14, 2017. Retrieved 2007-02-12.
Kroah-Hartman, Greg. Linux kernel monkey log. (2006-12-26). Retrieved 2007-01-28. (2006).
So, here's the simple answer to this issue: Closed source Linux kernel modules are illegal. That's it, it is very simple. I've had the misfortune of talking to a lot of different IP lawyers over the years about this topic, and every one that I've talked to all agree that there is no way that anyone can create a Linux kernel module, today, that can be closed source. It just violates the GPL due to fun things like derivative works and linking and other stuff. Again, it's very simple.
Now no lawyer will ever come out in public and say this, as lawyer really aren't allowed to make public statements like this at all. But if you hire one, and talk to them in the client/lawyer setting, they will advise you of this issue. Archived from on 2013-11-04. Retrieved 2014-03-04. Is glxgears an accurate measure of 3D performance?
No, it sucks in multiple ways. Retrieved 15 November 2017. Retrieved 15 November 2017.
Retrieved 15 November 2017. Retrieved 15 November 2017. Retrieved 15 November 2017. Retrieved 15 November 2017. Retrieved 2014-03-19.
Retrieved 15 November 2017. Retrieved 15 November 2017. Retrieved 15 November 2017. Retrieved 2016-06-04.
From the original on 20 July 2013. Retrieved 15 November 2017. Retrieved 15 November 2017. Debian.org. Retrieved 15 November 2017.
Retrieved 2016-04-26. Airlie (2006-07-19). Proceedings of the Linux Symposium Volume One. Archived from (PDF) on 2007-02-08.
Retrieved 2007-01-28. Retrieved 16 November 2017.
Retrieved 16 November 2017. Retrieved 16 November 2017. Ubuntu Gamer, January 10, 2011 (Article by Luke Benstead);. Retrieved 2010-10-26.
Retrieved 2011-03-23. Retrieved 2011-03-31. Retrieved 2011-05-23. Retrieved 2011-05-25. Retrieved 16 November 2017. phoronix (6 February 2012). – via YouTube.
Archived from on 2013-02-09. Michael Larabel (14 April 2012). Retrieved 15 April 2012. Soulskill (14 April 2012). Retrieved 15 April 2012. Rob Clark (14 April 2012). Retrieved 15 April 2012.
24 October 2012 at the. Rob Clark (29 July 2012). Retrieved 16 August 2012. Rob Clark (5 August 2012).
Retrieved 16 August 2012. Rob Clark (15 August 2012). Retrieved 16 August 2012. Retrieved 2014-07-15. Retrieved 2014-06-04. Retrieved 15 November 2017. Retrieved 15 November 2017.
(2008-07-26). Retrieved 2008-08-04. (2009-11-21). Retrieved 2009-12-30., January 06, 2011 (Article by ). Retrieved 16 November 2017. (Press release).
Retrieved 2009-05-15., December 11, 2010 (Article by )., February 22, 2011 (Article by ). 090503 wacco.mveas.com. Retrieved 2011-11-04. Bourdeauducq, Sebastien (June 2010). Archived from (PDF) on 2011-07-27. Retrieved 2010-11-05.
External links Wikibooks has a book on the topic of:. (Nouveau, amdgpu and Etnaviv) 2015.