Content deleted Content added
GreenC bot (talk | contribs) Rescued 3 archive links. Wayback Medic 2.5 |
m grammar |
||
| (46 intermediate revisions by 24 users not shown) | |||
Line 1:
{{short description|Portion of random-access memory containing a bitmap that drives a video display}}
{{Use American English|date=November 2024}}
[[File:Sun sbus cgsix framebuffer.jpg|thumb|Sun TGX Framebuffer]]
A '''framebuffer''' ('''frame buffer''', or sometimes '''framestore''') is a portion of [[
In [[computing]], a '''screen buffer''' is a part of [[computer memory]] used by a computer application for the representation of the content to be shown on the [[computer display]].<ref name="google">{{cite book|title=.NET Framework Solutions: In Search of the Lost Win32 API|author=Mueller, J.|date=2002|publisher=Wiley|isbn=9780782141344|url=https://books.google.com/books?id=XYQruTc6_44C|page=160|
The information in the buffer typically consists of color values for every
== History ==
[[File:SWAC 003.jpg|thumb|Memory pattern on [[SWAC (computer)|SWAC]] Williams tube CRT in 1951]]
Computer researchers{{who|date=July 2017}} had long discussed the theoretical advantages of a framebuffer
A color
In
In 1974, [[Evans & Sutherland]] released the first commercial framebuffer, the Picture System,<ref>{{citation |title=Picture System |url=http://s3data.computerhistory.org/brochures/evanssutherland.3d.1974.102646288.pdf |publisher=Evans & Sutherland |access-date=2017-12-31}}</ref> costing about $15,000. It was capable of producing resolutions of up to 512 by 512 pixels in 8-bit [[grayscale]], and became a boon for graphics researchers who did not have the resources to build their own framebuffer. The [[New York Institute of Technology]] would later create the first 24-bit color system using three of the Evans & Sutherland framebuffers.<ref name="NYIT-History">{{cite web |url=
In 1975, the UK company [[Quantel]] produced the first commercial full-color broadcast framebuffer, the Quantel DFS 3000. It was first used in TV coverage of the [[
The rapid improvement of integrated-circuit technology made it possible for many of the home computers of the late 1970s to contain low-color-depth framebuffers. Today, nearly all computers with graphical capabilities utilize a framebuffer for generating the video signal. [[Amiga]] computers, created in the 1980s, featured special design attention to graphics performance and included a unique [[Hold-And-Modify]] framebuffer capable of displaying 4096 colors.
Line 27 ⟶ 30:
Framebuffers used in personal and home computing often had sets of defined ''modes'' under which the framebuffer can operate. These modes reconfigure the hardware to output different resolutions, color depths, memory layouts and [[refresh rate]] timings.
In the world of [[Unix]] machines and operating systems, such conveniences were usually eschewed in favor of directly manipulating the hardware settings. This manipulation was far more flexible in that any resolution, color depth and refresh rate was attainable
An unfortunate side-effect of this method was that the [[display device]] could be driven beyond its capabilities. In some cases, this resulted in hardware damage to the display.<ref>http://tldp.org/HOWTO/XFree86-Video-Timings-HOWTO/overd.html XFree86 Video Timings HOWTO: Overdriving Your Monitor</ref> More commonly, it simply produced garbled and unusable output. Modern CRT monitors fix this problem through the introduction of protection circuitry. When the display mode is changed, the monitor attempts to obtain a signal lock on the new refresh frequency. If the monitor is unable to obtain a signal lock
LCD monitors tend to contain similar protection circuitry, but for different reasons. Since the LCD must digitally sample the display signal (thereby emulating an electron beam), any signal that is out of range cannot be physically displayed on the monitor.
== Color palette ==
Framebuffers have traditionally supported a wide variety of color modes. Due to the expense of memory, most early framebuffers used 1-bit (2
Here is a typical indexed 256-color image and its own palette (shown as a rectangle of swatches):
:{| style="border-style: none" border="0" cellpadding="0"
Line 46 ⟶ 48:
|}
In some designs it was also possible to write data to the
== Memory access ==
Line 58 ⟶ 60:
== RAM on the video card ==
{{see also|Video memory}}
Video cards always have a certain amount of RAM.
The CPU sends image updates to the video card. The video processor on the card forms a picture of the screen image and stores it in the frame buffer as a large bitmap in RAM. The bitmap in RAM is used by the card to continually refresh the screen image.<ref>{{cite web|url=http://karbosguide.com/hardware/module7b1.htm|title=An illustrated Guide to the Video Cards|work=karbosguide.com}}</ref>
Line 66 ⟶ 68:
== Page flipping ==
A frame buffer may be designed with enough memory to store two frames' worth of video data. In a technique known generally as [[double buffering]] or more specifically as [[page flipping]], the framebuffer uses half of its memory to display the current frame. While that memory is being displayed, the other half of memory is filled with data for the next frame. Once the secondary buffer is filled, the framebuffer is instructed to display the secondary buffer instead. The primary buffer becomes the secondary buffer, and the secondary buffer becomes the primary. This switch is often done after the [[vertical blanking interval]] to avoid [[screen tearing]] where half the old frame and half the new frame is shown together.
Page flipping has become a standard technique used by PC [[game programmer]]s.
== Graphics accelerators ==
{{See also|Video card|Graphics processing unit}}
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
Early accelerators focused on improving the performance of 2D [[
▲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 ''rasterizes'' the results of the command to the framebuffer. This method frees the CPU to do other work.
At one time there were many manufacturers of graphics accelerators, including: [[3dfx Interactive]]; [[ATI Technologies|ATI]]; [[Hercules Computer Technology|Hercules]]; [[Trident Microsystems|Trident]]; [[Nvidia]]; [[Radius (hardware company)|Radius]]; [[S3 Graphics]]; [[Silicon Integrated Systems|SiS]] and [[Silicon Graphics]]. {{as of|2015}} the market for graphics accelerators for x86-based systems is dominated by Nvidia (acquired 3dfx in 2002), [[AMD]] (who acquired ATI in 2006), and [[Intel]]
▲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.
==Comparisons==
▲At one time there were many manufacturers of graphics accelerators, including: [[3dfx Interactive]]; [[ATI Technologies|ATI]]; [[Hercules Computer Technology|Hercules]]; [[Trident Microsystems|Trident]]; [[Nvidia]]; [[Radius (hardware company)|Radius]]; [[S3 Graphics]]; [[Silicon Integrated Systems|SiS]] and [[Silicon Graphics]]. {{as of|2015}} the market for graphics accelerators for x86-based systems is dominated by Nvidia (acquired 3dfx in 2002), [[AMD]] (who acquired ATI in 2006), and [[Intel]] (which currently produces only [[Graphics processing unit#Integrated graphics solutions|integrated GPUs]] rather than discrete video cards).<!--[[User:Kvng/RTH]]-->
With a framebuffer, the electron beam (if the display technology uses one) is commanded to perform a [[raster scan]], the way a [[television]] renders a broadcast signal. The color information for each point thus displayed on the screen is pulled directly from the framebuffer during the scan, creating a set of discrete picture elements, i.e., pixels.
Framebuffers differ significantly from the [[vector display]]s that were common prior to the advent of raster graphics (and, consequently, to the concept of a framebuffer). With a vector display, only the [[vertex (geometry)|vertices]] of the graphics primitives are stored. The [[
▲Framebuffers differ significantly from the [[vector display]]s that were common prior to the advent of raster graphics (and, consequently, to the concept of a framebuffer). With a vector display, only the [[vertex (geometry)|vertices]] of the graphics primitives are stored. The [[Cathode ray|electron beam]] of the output display is then commanded to move from vertex to vertex, tracing an analog line across the area between these points. With a framebuffer, the electron beam (if the display technology uses one) is commanded to trace a left-to-right, top-to-bottom path across the entire screen, the way a [[television]] renders a broadcast signal. The color information for each point thus displayed on the screen is pulled from the framebuffer, creating a set of discrete picture elements, i.e. pixels.
Likewise, framebuffers differ from the technology used in early [[text mode]] displays, where a buffer holds codes for characters, not individual pixels. The video display device
== See also ==
*[[Bit plane]]
*[[Scanline rendering]]
*[[Swap chain]]
*[[Tile-based video game]]
*[[Tiled rendering]]
*[[Tektronix 4050]] used a [[storage tube]] to eliminate the need for framebuffer memory
== References ==
{{Reflist}}
{{Refbegin}}
* {{cite web |url=http://accad.osu.edu/~waynec/history/PDFs/14_paint.pdf |title=Digital Paint Systems: Historical Overview |author=Alvy Ray Smith |work=Microsoft Tech Memo 14 |date=May 30, 1997 |
* {{cite web |url=http://accad.osu.edu/~waynec/history/lesson15.html |title=Hardware advancements |work=A Critical History of Computer Graphics and Animation |publisher=The Ohio State University |author=Wayne Carlson |year=2003 |
* {{cite web |url=http://accad.osu.edu/~waynec/history/PDFs/paint.pdf |title=Digital Paint Systems: An Anecdotal and Historical Overview |author=Alvy Ray Smith |publisher=IEEE Annals of the History of Computing |year=2001 |
{{Refend}}
== External links ==
* [https://web.archive.org/web/20060211051810/http://www.acid.org/radio/arts-ep05-transcript.txt Interview with NYIT researcher discussing the 24-bit system]
* [http://www.sunhelp.org/faq/FrameBufferHistory.html History of Sun Microsystems' Framebuffers]
{{Graphics Processing Unit}}
| |||