The Linux framebuffer (fbdev) is a graphic hardware-independent abstraction layer to show graphics on a computer monitor, typically on the system console. It allows direct access to the framebuffer (the part of a computer's video memory containing a current video frame) using only the Linux kernel's own basic facilities and its device file system interface. It does not rely on user space software like SVGALib.
There are three applications of the Linux framebuffer.
- An implementation of text Linux console that doesn't use hardware text mode (useful when that mode is unavailable, or to overcome its restrictions on glyph size, number of code points etc.). One popular aspect of this is the ability to have console show the Tux logo at boot up.
- A possible graphic output method for a display server, independent of video adapter hardware and its drivers.
- Graphic programs avoiding the overhead of the X Window System.
Examples of the third application include Linux programs such as MPlayer, links2, Netsurf, fbff, fbida, and fim and libraries such as GLUT, SDL, GTK+, and Qt, which can all use the framebuffer directly. This use case is particularly popular in embedded systems.
The now defunct DirectFB is another project aimed at providing a framework for hardware acceleration of the Linux framebuffer.
Linux has generic framebuffer support since 2.1.109 kernel. It was originally implemented to allow the kernel to emulate a text console on systems such as the Apple Macintosh that do not have a text-mode display, and was later expanded to Linux's originally supported IBM PC compatible platform.
- The Frame Buffer Device, Linux Kernel Documentation
- fbff media player repository, GitHub
- fbi/fbida image viewer homepage
- FIM (Fbi IMproved) image viewer homepage
- HiGFXback (History of graphics backends) project with the Linux Framebuffer graphics backend, GitHub
- DirectFB Is Back To Being Dormant
- Framebuffer UI (fbui) in-kernel Linux windowing system, GitHub
- Framebuffer HOWTO