Graphic Hardware

Most of the graphic hardware is compatible with ArtistX. Anyway, remember that for better performances you should install it to your hard drive and also install the proprietary drivers if you have an ATI or Nvidia card.

Free and open source software (FOSS) can be used with a variety of graphics hardware, largely via the X.Org project. There are varying levels of support, ranging from completely working drivers to unsupported hardware. Some manufacturers do not provide open source drivers or technical documentation suitable for independent developers to write accelerated 3D device drivers; support for products from these companies can be limited: they may provide only binary drivers (known as binary blobs) or lack of documentation may leave developers of open source drivers toreverse engineer their products or not support them at all. In the case of binary drivers there are also objections due to free software philosophy, software quality and security concerns.[1] There are also concerns that the redistribution of closed source Linux kernel modules may be illegal.[2]

GLX demo included with X11

A widely known source for performance information is the free3d.org site,[3] which collects 3D performance information—specifically glxgears frame rates—submitted by users. On the basis of what it concedes is an inadequate benchmark,[4] the site currently lists ATI’s Radeon HD 4670 as recommended for “best 3D performance.” Additionally, Phoronix routinely runs benchmarks comparing free driver performance.[edit]Free software support

In general, the vesa driver supports most graphics cards without acceleration and with display resolutions limited to a set of resolutions programmed in the video BIOS by the manufacturer.

ATI/AMD

Currently[when?] support for ATI hardware is provided by the radeon driver, with the majority of cards being supported by either the R300g or R600gGallium 3D drivers. R300g supports the R300, R400, and R500 series of cards, while R600g supports the R600, R700, R800, and the R900series.[5] Older Radeon cards such as the R100 and R200 series still use a classic Mesa driver. The radeon drivers provide 2D and Xv acceleration, with 3D support available for almost all supported cards. However, proprietary firmware is still required for hardware acceleration.[6] FullModesetting support is also available.

Feature matrices are available for radeon from Freedesktop.org. In addition, they also host the RadeonProgram, which aims to have a community maintained application compatibility database similar to the Wine project’s AppDB.

ATI released programming specifications for a number of chipsets and features in 2007, 2008 and 2009.[7][8][9][10][11]AMD also does some active development and support for the radeon driver.[12] This is in direct contrast to AMD’s main competitor in the graphics field Nvidia, which does offer its own proprietary driver similar to AMD Catalyst, but does not provide any support or assistance to any free graphics initiatives.[13] AMD had just two engineers working full-time on the free drivers, namely Alex Deucher and Richard Li, although they decided to work to expand their free graphics team.[14] They recently hired three more developers, with one of the developers going to be working on the desktop graphics stack and the other two on embedded open-source priorities.[15] The developers in question have now been confirmed to be veteran graphics coders Michel Dänzer (taking over from Richard) and Christian König,[16] as well as Tom Stellard.

Recently, work on performance optimizations has greatly enhanced the 3D performance of the radeon driver, especially for users of R300g.[17] In some select cases, the R300g driver can even outperform a legacy Catalyst driver in terms of 3D performance.[18] Various options and tweaks can also be enabled to optimize the free driver’s speed and offer more competitive performance.[19]

Nvidia

A screenshot of REnouveau, which is a program that collects data for most of nouveau’s reverse engineering work

Nvidia, in the past, provided documentation for the older RIVA TNT series chipsets and maintained the partially open source but partially obfuscated 2D-only nv driver for X.Org.[20] However, this features neither 3D acceleration nor motion compensation.[21][22] On March 26, 2010, Nvidia announced that it would stop supporting new technologies and GPUs in nv, stating that

Nvidia will continue to support the existing functionality and existing level of acceleration in the nv driver for existing GPUs, on existing, and (within reason) future, X server versions.

Nvidia will not support the xf86-video-nv driver on Fermi or later GPUs.

Nvidia will not support DisplayPort, on any GPU, in the xf86-video-nv driver.

The nouveau driver project aims to reverse engineer Nvidia’s cards to produce 3D acceleration for X.Org utilizing Gallium 3D. While still at an early stage of development, several distributions of Linux, starting with Fedora,[25] have chosen to usenouveau as the default open-source driver for Nvidia cards.[26][27] The nouveau driver can already manage to offer competitive 3D performance on lower end Nvidia graphics hardware, when compared to the official binary driver.[28][29] On March 26, 2012, the Nouveau driver was marked as stable and promoted from the staging area of the Linux kernel.[30]

A feature matrix of Nouveau’s current capabilities is available at the project’s website.[31]

Intel

Intel has a long history of producing or commissioning open source drivers for its graphics chips, with the notable exception of their latest GMA 500 and GMA 3600/GMA 3650 chips that severely lacks documentation.[12] The driver development is outsourced to Tungsten Graphics.

There are currently two versions of the Intel X.Org driver, the xorg-video-i810 driver which supports the i810 and a number of more recent chipsets[32] and the updated xorg-video-intel driver that supports the same hardware, with the recent versions 2.0 and 2.1 adding support for later chips, including the G33, Q33 and Q35.[33]

In addition, the xorg-video-intel driver (sometimes known as the “modesetting driver”) does not use the video BIOS for switching video modes; as some BIOSes include only a limited range of modes, this provides more reliable access to those supported by Intel video cards.

Unlike the radeon and nouveau drivers, Intel does not intend to utilize the Gallium 3D framework for its graphics drivers.[34] Intel has also recently put work into optimizing their free Linux drivers to have closer performance to their Windows counterparts, especially on Sandy Bridge hardware where various performance optimizations have now allowed the free Intel driver to be able to outperform their proprietary Windows drivers at certain tasks.[35][36][37] Some of these performance enhancements can also benefit users of older hardware.[38]

S3 Graphics

ARM

ARM Holdings develops the Mali series GPUs and sells soft IP or hard IP to licensees. On January 21, 2012, Phoronix reported that Luc Verhaegen 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 was presented at FOSDEM, February 4, 2012.[39][40] On February 2nd 2013, Verhaegen demonstrated Quake III Arena in timedemo mode, running on top of the Lima driver.[41]

Imagination Technologies

Imagination Technologies develops the PowerVR series of GPUs and sells them as IP core (Intellectual Property), e.g. there are a couple of PowerVR based-Intel GPUs but mostly used in mobile SoCs. Imagination Technologies do not provide a FOSS driver nor any documentation for their products. The Free Software Foundation has put reverse-engineering of the PowerVR driver on a high-priority project list.[42]

Broadcom

Broadcom develops and manufactures the VideoCore GPU series. E.g. the Raspberry Pi uses it. There were no FOSS drivers available for VideoCore.[52] However on October 24, 2012 the Raspberry Pi Foundation, in co-operation with Broadcom, open sourced, (using the 3-clause BSD FOSS licence) all the ARM (CPU) code that drives the GPU, through “letterbox” software interfaces. But on the Videocore GPU most of the actual video acceleration is done using firmware coded for its proprietary GPU, and this firmware wasn’t open sourced.[53] Also, as there is neither toolchain available that could target this proprietary GPU, nor its ISA is documented, no possible advantage could be taken in case if the firmware source code would be made available.

Other vendors

SiS and VIA have both shown limited interest and communication regarding open source drivers; however, both have released source code which has later been integrated into X.Org by FOSS developers.[21] In July 2008, VIA opened up documentation for their products to improve its image within the Linux and open-source communities.[54] Although, so far VIA has failed to work with the open source community to provide documentation and a working DRM driver, leaving expectations for supporting the Linux operating system unfulfilled.[55] On January 6, 2011 it was announced that VIA was no longer interested in supporting free graphics initiatives.[56]

DisplayLink have announced an open source project called libdlo with the goal of bringing support for their USB graphics technology to Linux and other platforms. The code is available under the LGPL license.[57] It has not yet been integrated into an X.Org driver. DisplayLink graphics support is available through the kernel udlfb driver (with fbdev) in mainline, and udl/drm driver, which as of March 2012 is only available in the drm-next tree.

Often other non-hardware related vendors may also lend a hand to free graphics initiatives. Red Hat has some employees working full-time on several free and open source software projects, such as two full-time employees working on the free software radeon (David Airlie and Jérôme Glisse[58]) and one full-time employee working on the free software nouveau graphic drivers.[citation needed] In addition, the Fedora Project runs a “Fedora Graphics Test Week” event before the launch of their new Linux distribution versions in order to provide rigorous testing to free graphics drivers.[59] Other companies that have provided development or support include Novell and VMware.

Problems with binary drivers

There are a number of objections to binary-only drivers. These may be philosophical, with some feeling that drivers distributed without source code are against the beliefs of the free software movement, or pragmatic copyright, security or reliability concerns. As part of a wider campaign against binary blobs, OpenBSD lead developer Theo de Raadt has pointed out that with a binary driver there is “no way to fix it when it breaks (and it will break)” and that once a product which relies on binary drivers is declared to be end-of-life by the manufacturer, it is effectively “broken forever.”[60] The project has also asserted that binary drivers “hide bugs and workarounds for bugs,”[61] a comment that has been somewhat vindicated by flaws found in binary drivers, including in October 2006 an exploitablebug in Nvidia’s 3D drivers discovered by Rapid7. It is speculated that this bug has existed since 2004, although Nvidia have denied this, asserting that the issue was only communicated to them in July 2006 and that the 2004 bug was a bug in X.Org, not in Nvidia’s driver.[62] Another problem with binary drivers is that they often do not work with current versions of open source software, and almost never support development snapshots of open source software – e.g. 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.

In the Linux kernel development community, Linus Torvalds has made strong statements on the issue of binary-only modules, asserting: “I refuse to even consider tying my hands over some binary-only module”, and continuing: “I want people to know that when they use binary-only modules, it’s THEIR problem”.[63] Another kernel developer, Greg Kroah-Hartman, has commented that a binary-only kernel module does not comply with the kernel’s license—the GNU General Public License—it “just violates the GPL due to fun things like derivative works and linking and other stuff.”[64]

Writer and computer scientist Peter Gutmann has expressed concerns that the digital rights management scheme in Microsoft’s Windows Vista operating system may limit the availability of the documentation required to write open drivers as it “requires that the operational details of the device be kept confidential.”[65]

References

^Greg Kroah-Hartman (2006). “Myths, Lies, and Truths about the Linux kernel”. Linux Symposium. “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.”