Framebuffer: Difference between revisions

Content deleted Content added
Monkbot (talk | contribs)
m Task 18 (cosmetic): eval 17 templates: hyphenate params (10×);
m Provided the hyper link for 'rasterizes' under Graphics Accelerators
Line 73:
{{See also|Video card}}
 
As the demand for better graphics increased, hardware manufacturers created a way to decrease the amount of [[CPU]] time required to fill the framebuffer. This is commonly called ''graphics acceleration''. Common graphics drawing commands (many of them geometric) are sent to the graphics accelerator in their raw form. The accelerator then ''[[Rasterisation|rasterizes'']] the results of the command to the framebuffer. This method frees the CPU to do other work.
 
Early accelerators focused on improving the performance of 2D [[Graphical user interface|GUI]] systems. While retaining these 2D capabilities, most modern accelerators focus on producing 3D imagery in real time. A common design uses a [[graphics library]] such as [[OpenGL]] or [[Direct3D]] which interfaces with the graphics driver to translate received commands to instructions for the accelerator's [[graphics processing unit]] (GPU). The GPU uses those instructions to compute the rasterized results and the results are [[bit blit]]ted to the framebuffer. The framebuffer's signal is then produced in combination with built-in video overlay devices (usually used to produce the mouse cursor without modifying the framebuffer's data) and any final special effects that are produced by modifying the output signal. An example of such final special effects was the [[spatial anti-aliasing]] technique used by the [[3dfx Voodoo]] cards. These cards add a slight blur to output signal that makes aliasing of the rasterized graphics much less obvious.