| /Linux-v5.15/Documentation/fb/ |
| D | ep93xx-fb.rst | 26 are in pixel clocks. See Documentation/fb/framebuffer.rst for further
39 The framebuffer device can be registered by adding the following to
68 The physical address of the framebuffer can be controlled using the
72 EP93XXFB_USE_SDCSN0 Use SDCSn[0] for the framebuffer. This
75 EP93XXFB_USE_SDCSN1 Use SDCSn[1] for the framebuffer.
77 EP93XXFB_USE_SDCSN2 Use SDCSn[2] for the framebuffer.
79 EP93XXFB_USE_SDCSN3 Use SDCSn[3] for the framebuffer.
86 The EP93xx framebuffer driver supports three optional platform
88 are called when the framebuffer driver is installed and removed
101 /* Board specific framebuffer setup */
[all …]
|
| D | fbcon.rst | 5 The framebuffer console (fbcon), as its name implies, is a text
6 console running on top of the framebuffer device. It has the functionality of
8 features that can be attributed to the graphical nature of the framebuffer.
10 In the x86 architecture, the framebuffer console is optional, and
14 What are the features of fbcon? The framebuffer console supports
22 The framebuffer console can be enabled by using your favorite kernel
28 In order for fbcon to activate, at least one framebuffer driver is
42 GOTCHA: A common bug report is enabling the framebuffer without enabling the
43 framebuffer console. Depending on the driver, you may get a blanked or
62 garbled display, as mentioned above. To get a framebuffer console,
[all …]
|
| D | deferred_io.rst | 10 - userspace app like Xfbdev mmaps framebuffer
20 completes the work associated with updating the framebuffer. this is
25 As can be seen from above, one benefit is roughly to allow bursty framebuffer
27 have gone quiet, we go and really update the framebuffer which would be
38 Another one may be if one has a device framebuffer that is in an usual format,
40 apps to pretend to have a normal framebuffer but reswizzle for the device
41 framebuffer at vsync time based on the touched pagelist.
45 No changes needed. mmap the framebuffer like normal and just use it.
|
| D | udlfb.rst | 8 pairing that with a hardware framebuffer (16MB) on the other end of the
9 USB wire. That hardware framebuffer is able to drive the VGA, DVI, or HDMI
13 result with a local shadow of the remote hardware framebuffer to identify
32 Advantages of supporting DisplayLink chips with kernel framebuffer interface:
44 * Fbdev's mmap interface assumes a real hardware framebuffer is mapped.
51 * Fbdev does not arbitrate client ownership of the framebuffer well.
52 * Fbcon assumes the first framebuffer it finds should be consumed for console.
67 to open and begin writing to the framebuffer of the DisplayLink device using
76 code. They write to the standard framebuffer interface and rely on udlfb
105 module to track changed areas of the framebuffer by page faults.
[all …]
|
| D | pxafb.rst | 88 base framebuffer (although under-neath the base is also possible). They
91 behave in a similar way as a framebuffer.
97 framebuffer, which means they have a start (x, y). This information
101 2. overlay framebuffer is allocated dynamically according to specified
134 framebuffer:
152 framebuffer framework, application has to take care of the offsets
153 and lengths of each component within the framebuffer.
|
| D | intelfb.rst | 8 This is a framebuffer driver for various Intel 8xx/9xx compatible
47 framebuffer memory. The intent is to avoid the memory blocks
70 enable MTRR. This allows data transfers to the framebuffer memory
101 This will initialize the framebuffer to 800x600 at 32bpp and 75Hz. The
102 framebuffer will use 8 MB of System RAM. hw acceleration of text and cursor
142 framebuffer driver code made this possible.
|
| D | intel810.rst | 17 This is a framebuffer driver for various Intel 810/815 compatible
31 Formula, or a framebuffer specific database to set the video mode
124 framebuffer memory. The intent is to avoid the memory blocks
127 avoid XFree86's usage and allows up to 7 MB/15 MB of framebuffer
143 enable MTRR. This allows data transfers to the framebuffer memory
194 This will initialize the framebuffer to 1024x768 at 8bpp. The framebuffer
254 f. If you want a framebuffer console, enable it under "Console
268 framebuffer driver code made this possible.
|
| /Linux-v5.15/Documentation/userspace-api/media/v4l/ |
| D | dev-osd.rst | 11 Some video output devices can overlay a framebuffer image onto the
38 Contrary to the *Video Overlay* interface the framebuffer is normally
40 accessible as a framebuffer device (``/dev/fbN``). Given a V4L2 device,
41 applications can find the corresponding framebuffer device by calling
43 other information, the physical address of the framebuffer in the
45 The framebuffer device ioctl ``FBIOGET_FSCREENINFO`` returns the same
51 The width and height of the framebuffer depends on the current video
53 (or any other ioctl which would imply a framebuffer size change) with an
54 ``EBUSY`` error code until all applications closed the framebuffer device.
56 Example: Finding a framebuffer device for OSD
[all …]
|
| D | vidioc-g-fbuf.rst | 39 to get and set the framebuffer parameters for a
59 :c:type:`v4l2_framebuffer`. Since the framebuffer is
63 framebuffer parameters as :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>` does, or it returns an error
69 the overlay and returns the framebuffer parameters as :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>`
93 :ref:`framebuffer-cap`.
98 :ref:`framebuffer-flags`
102 - Physical base address of the framebuffer, that is the address of
103 the pixel in the top left corner of the framebuffer. [#f1]_
112 find the corresponding Linux framebuffer device (see
129 - The pixel format of the framebuffer.
[all …]
|
| /Linux-v5.15/drivers/video/fbdev/geode/ |
| D | Kconfig | 3 # Geode family framebuffer configuration
6 bool "AMD Geode family framebuffer support"
9 Say 'Y' here to allow you to select framebuffer drivers for
13 tristate "AMD Geode LX framebuffer support"
28 tristate "AMD Geode GX framebuffer support"
43 tristate "AMD Geode GX1 framebuffer support"
|
| /Linux-v5.15/drivers/media/pci/ivtv/ |
| D | Kconfig | 49 tristate "Conexant cx23415 framebuffer support"
55 This is a framebuffer driver for the Conexant cx23415 MPEG
64 bool "force cx23415 framebuffer init with x86 PAT enabled"
67 With PAT enabled, the cx23415 framebuffer driver does not
68 utilize write-combined caching on the framebuffer memory.
77 With this setting enabled, the framebuffer will initialize on
78 PAT-enabled systems but the framebuffer memory will be uncached.
|
| /Linux-v5.15/arch/arm64/boot/dts/apple/ |
| D | t8103-j274.dts | 29 framebuffer0: framebuffer@0 {
30 compatible = "apple,simple-framebuffer", "simple-framebuffer";
|
| /Linux-v5.15/drivers/video/console/ |
| D | Kconfig | 79 Low-level framebuffer-based console driver.
86 If this option is selected, the framebuffer console will
88 supports this feature). Otherwise, the framebuffer console will
89 always select the first framebuffer driver that is loaded. The latter
101 Enable display rotation for the framebuffer console. This is done
104 such that other users of the framebuffer will remain normally
111 If enabled this defers the framebuffer console taking over the
114 commandline option to keep the framebuffer contents initially put up
|
| /Linux-v5.15/Documentation/arm/omap/ |
| D | dss.rst | 42 The DSS driver does not itself have any support for Linux framebuffer, V4L or
121 From omapdss point of view the V4L2 drivers should be similar to framebuffer
133 screen. The overlay may be smaller than framebuffer, thus displaying only
134 part of the framebuffer. The position of the overlay may be changed if
140 A framebuffer can be connected to multiple overlays to show the same pixel data
143 framebuffer can be connected to any overlay.
169 overlays List of overlay numbers to which framebuffer pixels go
170 phys_addr Physical address of the framebuffer
171 virt_addr Virtual address of the framebuffer
172 size Size of the framebuffer
[all …]
|
| /Linux-v5.15/Documentation/userspace-api/media/ |
| D | videodev2.h.rst.exceptions | 224 # V4L2 framebuffer caps and flags
226 replace define V4L2_FBUF_CAP_EXTERNOVERLAY framebuffer-cap
227 replace define V4L2_FBUF_CAP_CHROMAKEY framebuffer-cap
228 replace define V4L2_FBUF_CAP_LIST_CLIPPING framebuffer-cap
229 replace define V4L2_FBUF_CAP_BITMAP_CLIPPING framebuffer-cap
230 replace define V4L2_FBUF_CAP_LOCAL_ALPHA framebuffer-cap
231 replace define V4L2_FBUF_CAP_GLOBAL_ALPHA framebuffer-cap
232 replace define V4L2_FBUF_CAP_LOCAL_INV_ALPHA framebuffer-cap
233 replace define V4L2_FBUF_CAP_SRC_CHROMAKEY framebuffer-cap
235 replace define V4L2_FBUF_FLAG_PRIMARY framebuffer-flags
[all …]
|
| /Linux-v5.15/Documentation/devicetree/bindings/display/ |
| D | google,goldfish-fb.txt | 1 Android Goldfish framebuffer
3 Android Goldfish framebuffer device used by Android emulator.
|
| D | via,vt8500-fb.txt | 7 - interrupts : framebuffer controller interrupt
8 - bits-per-pixel : bit depth of framebuffer (16 or 32)
|
| D | arm,hdlcd.txt | 5 streamer that reads the data from a framebuffer and sends it to a single
27 used for the framebuffer; if not present, the framebuffer may be located
|
| D | atmel,lcdc.txt | 15 for fixed framebuffer memory. Useful for dedicated memories.
16 - interrupts : framebuffer controller interrupt
42 Example for fixed framebuffer memory:
|
| /Linux-v5.15/drivers/gpu/drm/tegra/ |
| D | fb.c | 26 struct tegra_bo *tegra_fb_get_plane(struct drm_framebuffer *framebuffer, in tegra_fb_get_plane() argument
29 return to_tegra_bo(drm_gem_fb_get_obj(framebuffer, index)); in tegra_fb_get_plane()
32 bool tegra_fb_is_bottom_up(struct drm_framebuffer *framebuffer) in tegra_fb_is_bottom_up() argument
34 struct tegra_bo *bo = tegra_fb_get_plane(framebuffer, 0); in tegra_fb_is_bottom_up()
42 int tegra_fb_get_tiling(struct drm_framebuffer *framebuffer, in tegra_fb_get_tiling() argument
45 uint64_t modifier = framebuffer->modifier; in tegra_fb_get_tiling()
|
| D | drm.h | 183 struct tegra_bo *tegra_fb_get_plane(struct drm_framebuffer *framebuffer,
185 bool tegra_fb_is_bottom_up(struct drm_framebuffer *framebuffer);
186 int tegra_fb_get_tiling(struct drm_framebuffer *framebuffer,
|
| /Linux-v5.15/drivers/video/fbdev/ |
| D | Kconfig | 34 buffer devices. Please read <file:Documentation/fb/framebuffer.rst>
73 If true, at least one selected framebuffer driver can take advantage
114 (accelerated) version and the framebuffer is in system RAM.
122 version and the framebuffer is in system RAM.
130 (accelerated) version and the framebuffer is in system RAM.
144 non-native endianness (e.g. Little-Endian framebuffer on a
223 tristate "Aeroflex Gaisler framebuffer support"
229 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
286 This framebuffer device driver is for the ARM PrimeCell PL110
326 This is a framebuffer device for the SA-1100 LCD Controller.
[all …]
|
| /Linux-v5.15/drivers/gpu/drm/vmwgfx/ |
| D | vmwgfx_kms.h | 416 struct vmw_framebuffer *framebuffer,
498 struct vmw_framebuffer *framebuffer,
512 struct vmw_framebuffer *framebuffer,
522 struct vmw_framebuffer *framebuffer,
542 struct vmw_framebuffer *framebuffer,
|
| D | vmwgfx_scrn.c | 977 struct vmw_framebuffer *framebuffer) in do_bo_define_gmrfb() argument
980 container_of(framebuffer, struct vmw_framebuffer_bo, in do_bo_define_gmrfb()
982 int depth = framebuffer->base.format->depth; in do_bo_define_gmrfb()
1000 cmd->body.format.bitsPerPixel = framebuffer->base.format->cpp[0] * 8; in do_bo_define_gmrfb()
1003 cmd->body.bytesPerLine = framebuffer->base.pitches[0]; in do_bo_define_gmrfb()
1124 struct vmw_framebuffer *framebuffer, in vmw_kms_sou_do_surface_dirty() argument
1135 container_of(framebuffer, typeof(*vfbs), base); in vmw_kms_sou_do_surface_dirty()
1165 ret = vmw_kms_helper_dirty(dev_priv, framebuffer, clips, vclips, in vmw_kms_sou_do_surface_dirty()
1240 struct vmw_framebuffer *framebuffer, in vmw_kms_sou_do_bo_dirty() argument
1249 container_of(framebuffer, struct vmw_framebuffer_bo, in vmw_kms_sou_do_bo_dirty()
[all …]
|
| /Linux-v5.15/Documentation/admin-guide/auxdisplay/ |
| D | cfag12864b.rst | 85 The cfag12864bfb describes a framebuffer device (/dev/fbX).
91 You can use the framebuffer as a file: fopen, fwrite, fclose...
94 Also, you can mmap the framebuffer: open & mmap, munmap & close...
|
