Accelerated Graphic Cards

While it is nice to have some graphics on the screen, it would be even nicer to have the video card do the dirty work. Beware though, things are not always as easy as they seem. Alternative VESA BIOS Extension/Accelerator Functions

Cards with documentation

3Dfx

These are a sort of good news for 3dfx cards (those with a Voodoo chipset). These cards could be the only ones with relatively fast 3D support (Glide/OpenGL) and open specifications. Voodoo cards are still available from sources such as eBay.

Intel Integrated Graphics

The Intel video chipsets also have open standards (see www.intel.com). Some useful links:

• Intel 740 Graphics Accelerator
• Intel Graphics Documentations on X.org

ATI / AMD

AMD has recently started to open up the specifications for their recent video cards. The ones regarding a R630 or M56 chip can be downloaded from X.org.

NVIDIA

NVidia doesn't provide official specifications, but a lot of community effort is spent in the noveau project, which can be sourced for examples and documentation even though such reverse engineered specifications aren't complete nor guaranteed to be accurate. Marcin Kościelnicki has been writing down unofficial specs in his envytools repository. Although having missing bits here and there, they are certainly an interesting resource for learning about the internals of these graphic cards. These docs cover the entire range of NVIDIA hardware, from the first to the latest card, and might prove sufficient to write a native driver.

Where can I find low-level information about nVidia/Matrox/ATI/... 3D graphic cards?

Good question. Unless you find something else, there is virtually no information publicly available (for free or otherwise) about the internal workings of current 3D graphics cards. There are only small bits that are relevant to game programmers but nothing an OS developer could use.

Now, if you have a VIA graphics chip, things may be better since they recently released an open source driver for both 2D and 3D operations.

There are virtually no tutorials or datasheets for the 2D acceleration features either, but at least we have open-source code for them. Among other sources, the Xfree drivers, BeOS accelerants and FreeBE/AF. They may provide enough information to reverse-engineer and figure out a model that could be used to program/port for your environment. Some older cards with only 2D acceleration might be documented by the VGADoc.

Anyone who wishes to put time into that kind of research is welcome to post their results here.

What can 2D acceleration do for me?

• Hardware mouse cursor, drawn and managed (e.g. you provide coordinates, the card does the rest)
• Bitblt (for "BIT BLock Transfer") can be used for screen-to-screen memory copy like windows moving, scrolling, etc. You provide from and to boxes and the card does the rest. Some might know this as the "rasterop" or remember the hardware "blitter" in Amiga computers.
• Tiles. You enter a small NxN dataset (usually a bitmap of between 8x8 and 32x32), a foreground color and a mixing style plus some coordinates and the card "paints" the area with the given pattern. That can be handy to render Win95-like backgrounds (tiled ones) or even to draw fonts quickly.

How do 3D-accelerated programs talk to 3D-accelerating hardware?

I'll be assuming that you have a strong knowledge of OpenGL etc and that you don't need it covered here. If you take the example of nVidia's 3D driver for linux (if you have a correctly configured nVidia card, you can see almost all this by a simple "strace" on a 3D program in linux), things are organized this way:

• Two libraries libGL.so and libGLcore.so will be loaded by any program that wishes to do accelerated 3D operations. Upon startup, those libraries open "/dev/nvidiactl" and "/dev/nvidia0".
• The kernel module is made of an "obscure" file nv-kernel.o which contains only "anonymized" symbols and an "open source" part that mainly glues the nv-kernel (which is actually almost system transparent) to the linux kernel.
• The actual "conversation" between the library and the driver cannot be traced by conventional means: /dev/nvidia* only allows "ioctl" operations and mmap. The values you can observe in "/proc/XXXXX/maps" while the 3D program is running let me believe the driver actually exposes the hardware resources (e.g. texture space, vertex space, etc) directly to the library. Current linux kernels can however be compiled with the mmiotrace option which can then be used to log all individual accesses to mmapped space.

l /proc/pci
Bus  0, device   0, function  0:
    Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev 196).
      Prefetchable 32 bit memory at 0xfc000000 [0xfdffffff].

Bus  1, device   0, function  0:
    VGA compatible controller: nVidia Corporation RIVA TNT2 Model 64 (rev 21).
      IRQ 11.
      Master Capable.  Latency=248.  Min Gnt=5.Max Lat=1.
      Non-prefetchable 32 bit memory at 0xf7000000 [0xf7ffffff].
      Prefetchable 32 bit memory at 0xfa000000 [0xfbffffff].

cat /proc/XXXXX/maps
...
40019000-40029000 rw-s f7810000 03:06 54934      /dev/nvidia0
40029000-4002a000 rw-s 0ba98000 03:06 54934      /dev/nvidia0
...
40a9b000-42a9b000 rw-s fa000000 03:06 54934      /dev/nvidia0
42a9b000-42b79000 rw-p 00000000 00:00 0
42b79000-42c7a000 rw-s fc010000 03:06 54934      /dev/nvidia0
42c7a000-42d7c000 rw-p 00000000 00:00 0
42d7c000-42dfc000 rw-s fc111000 03:06 54934      /dev/nvidia0

External links

• A topic on duplicating/reverse engineering existing driver code