FAIR and interactive data graphics from a scientific knowledge graph

A blitter is a circuit, sometimes as a coprocessor or a logic block on a microprocessor, dedicated to the rapid movement and modification of data within a computer's memory. A blitter can copy large quantities of data from one memory area to another relatively quickly, and in parallel with the CPU, while freeing up the CPU's more complex capabilities for other operations. A typical use for a blitter is the movement of a bitmap, such as windows and icons in a graphical user interface or images and backgrounds in a 2D video game. The name comes from the bit blit operation of the 1973 Xerox Alto,^[1] which stands for bit-block transfer.^[2] A blit operation is more than a memory copy, because it can involve data that's not byte aligned (hence the bit in bit blit), handling transparent pixels (pixels which should not overwrite the destination), and various ways of combining the source and destination data.

Blitters have largely been superseded by programmable graphics processing units.

In computers without hardware accelerated raster graphics, which includes most 1970s and 1980s home computers and IBM PC compatibles through the mid-1990s, the frame buffer is commonly stored in CPU-accessible memory. Drawing is accomplished by updating the frame buffer via software. For fundamental graphics routines, like compositing a smaller image into a larger one (such as for a video game) or drawing a filled rectangle, large amounts of memory need to be manipulated, and many cycles are spent fetching and decoding short loops of load/store instructions. For CPUs without caches, the bus requirement for instructions is as significant as data. To reduce the size of the frame buffer, a single byte may not necessarily correspond to a pixel, but contain 8 single-bit pixels, 4 two-bit pixels, or a pair of 4-bit pixels. Manipulating packed pixels requires extra shifting and masking operations on the CPU.

Blitters were developed to offload repetitive tasks of copying data or filling blocks of memory faster than possible by the CPU. This can be done in parallel with the CPU and also handle special cases which would be significantly slower if coded by hand, such as skipping over pixels marked as transparent or handling data that isn't byte-aligned.

1973: The Xerox Alto, where the term bit blit originated, has a bit block transfer instruction implemented in microcode, making it much faster than the same operation written on the CPU.^[1] The microcode was implemented by Dan Ingalls.^[1]

1978: The Bally Astrocade home console ships with primitive blitter hardware.^[3]

1982: In addition to drawing shape primitives, the NEC μPD7220 video display processor can transfer rectangular bitmaps to display memory via direct memory access and fill rectangular portions of the screen.^[4][5] The design was licensed by Intel and sold as the 82720 graphics display controller.

1982: The Robotron: 2084 arcade video game from Williams Electronics includes two blitter chips which allow the game to have up to 80 simultaneously moving objects.^[6] Performance was measured at roughly 910 KB/second.^[6] The blitter operates on 4-bit (16 color) pixels where color 0 is transparent, allowing for non-rectangular shapes.^[7] Williams used the same hardware in other games from the time period, including Sinistar and Joust.^[7]

1984: The MS-DOS compatible Mindset personal computer contains a custom VLSI chip to move rectangular sections of a bitmap. The hardware handles transparency and eight modes for combining the source and destination data.^[8] The Mindset was claimed to have graphics up to 50x faster than IBM PC compatibles of the time,^[9] but the system was not successful.

1985: One of the coprocessors in the Amiga personal computer is a blitter. The first US patent filing to use the term blitter was "Personal computer apparatus for block transfer of bit-mapped image data," assigned to Commodore-Amiga, Inc.^[10] The blitter performs an arbitrary boolean operation on three bit vectors of size 16:

destination := op(source A, source B, source C)

1986: The TMS34010 is a general purpose 32-bit processor with built-in instructions, including PIXBLT (Pixel Block Transfer), for manipulating bitmap data. It is optimized for cases that would take extra processing if implemented in software, such as handling transparent pixels, working with non-byte aligned data, and converting between bit depths. PIXBLT provides 22 ways of combining the source and destination data.^[11] The TMS34010 serves as both CPU and GPU for a number of arcade games starting in 1988 with Narc and including Hard Drivin', Smash TV, Mortal Kombat, and NBA Jam, ^[12] It was also used in graphics accelerator boards in the 1990s.

1987: The IBM 8514/A display adapter, introduced with the IBM Personal System/2 computers in April 1987, includes bit block transfer hardware.^[13]

1987: The Atari Mega ST 2 ships with a blitter chip.^[14] Officially called the "Atari ST Bit-Block Transfer Processor", stylized as BLiTTER, it provides 16 options for merging source and destination data.^[15] The blitter is supported on most subsequent ST machines.

1989: The short-lived Atari Transputer Workstation contains blitter hardware as part of its (Mega ST-based) "Blossom" video system.^[16]

1989: The Atari Lynx color handheld game system has a custom blitter with scaling and distortion effects.

1993: The Atari Jaguar game console has blitter hardware as part of the custom "Tom" chip.^[17]

1996: The VESA Group introduced a standardized way to access features like hardware Bit Block transfers with VBE/accelerator functions (VBE/AF) on IBM PC compatibles.

Typically, a computer program puts information into certain hardware registers describing what memory transfer needs to be completed and the logical operations to perform on the data. The CPU then triggers the blitter to begin operating. The CPU is free for other processing while the blitter is working, though the blit running in parallel uses memory bandwidth.

To copy data with fully transparent pixels—such as sprites—some hardware allows a specific pixel value to be ignored, such as color 0, during the blit. Those pixels are not written to the destination.

Another approach on some systems is to have a second 1 bit per pixel image used as a mask to indicate which pixels to transfer and which to leave untouched. The mask operates like a stencil. The logical operation is:

destination := (background AND NOT mask) OR sprite

Hardware sprites are small bitmaps which can be positioned independently and are composited together with the background on-the-fly by the video chip. The frame buffer is not modified.^[18] The downside of sprites is a limit of moving graphics per scanline, which can range from three (Atari 2600) to eight (Commodore 64 and Atari 8-bit computers) to significantly higher for 16-bit consoles and arcade hardware (the Neo Geo can display 96 sprites per line. The inability to update a permanent bitmap makes them unsuitable for general desktop GUI acceleration.

• Direct Memory Access (DMA)