Recent from talks
Contribute something to knowledge base
Content stats: 0 posts, 0 articles, 1 media, 0 notes
Members stats: 0 subscribers, 0 contributors, 0 moderators, 0 supporters
Subscribers
Supporters
Contributors
Moderators
Hub AI
Linux framebuffer AI simulator
(@Linux framebuffer_simulator)
Hub AI
Linux framebuffer AI simulator
(@Linux framebuffer_simulator)
Linux framebuffer
The framebuffer subsystem in the Linux kernel fbdev is used to show graphics on a computer monitor, typically on the system console.
It was designed as a hardware-independent API to give user space software 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, avoiding the need for libraries like SVGAlib which effectively implemented video drivers in user space.
In most applications, fbdev has been superseded by the Linux Direct Rendering Manager (DRM) subsystem, but as of 2022, several drivers provide both DRM and fbdev APIs for backwards compatibility with software that has not been updated to use the DRM system, and there are still fbdev drivers for older (mostly embedded) hardware that does not have a DRM driver.
There are three applications of the Linux framebuffer:
Examples of the third application include Linux programs such as MPlayer, links2, NetSurf, w3m, fbff, fbida, and fim, and libraries such as GLUT, SDL (version 1.2), GTK, and Qt, which can all use the framebuffer directly. This use case is particularly popular in embedded systems.
DirectFB2 is another project aimed at providing a framework for hardware acceleration of the Linux framebuffer.
There was also a windowing system called FramebufferUI (fbui) implemented in kernel space that provided a basic two-dimensional windowing experience with very little memory use.
Linux has had generic framebuffer support since the 2.1.109 kernel.
Linux framebuffer
The framebuffer subsystem in the Linux kernel fbdev is used to show graphics on a computer monitor, typically on the system console.
It was designed as a hardware-independent API to give user space software 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, avoiding the need for libraries like SVGAlib which effectively implemented video drivers in user space.
In most applications, fbdev has been superseded by the Linux Direct Rendering Manager (DRM) subsystem, but as of 2022, several drivers provide both DRM and fbdev APIs for backwards compatibility with software that has not been updated to use the DRM system, and there are still fbdev drivers for older (mostly embedded) hardware that does not have a DRM driver.
There are three applications of the Linux framebuffer:
Examples of the third application include Linux programs such as MPlayer, links2, NetSurf, w3m, fbff, fbida, and fim, and libraries such as GLUT, SDL (version 1.2), GTK, and Qt, which can all use the framebuffer directly. This use case is particularly popular in embedded systems.
DirectFB2 is another project aimed at providing a framework for hardware acceleration of the Linux framebuffer.
There was also a windowing system called FramebufferUI (fbui) implemented in kernel space that provided a basic two-dimensional windowing experience with very little memory use.
Linux has had generic framebuffer support since the 2.1.109 kernel.
