| /Linux-v4.19/Documentation/devicetree/bindings/display/ |
| D | simple-framebuffer.txt | 8 the chosen node (*). Simplefb nodes must be named "framebuffer@<address>".
28 It is advised that devicetree files contain pre-filled, disabled framebuffer
34 If pre-filled framebuffer nodes are used, the firmware may need extra
37 see e.g. simple-framebuffer-sunxi.txt .
40 - compatible: "simple-framebuffer"
41 - reg: Should contain the location and size of the framebuffer memory.
42 - width: The width of the framebuffer in pixels.
43 - height: The height of the framebuffer in pixels.
44 - stride: The number of bytes in each line of the framebuffer.
45 - format: The format of the framebuffer surface. Valid values are:
[all …]
|
| D | simple-framebuffer-sunxi.txt | 3 This binding documents sunxi specific extensions to the simple-framebuffer
12 - compatible: "allwinner,simple-framebuffer"
30 framebuffer@0 {
31 compatible = "allwinner,simple-framebuffer", "simple-framebuffer";
|
| 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-v4.19/Documentation/fb/ |
| D | 00-INDEX | 25 - intro to and usage guide for the framebuffer console (fbcon).
26 framebuffer.txt
29 - info on the framebuffer driver for AMD Geode GX2 based processors.
31 - documentation for the Intel 810/815 framebuffer driver.
37 - info on the framebuffer driver for AMD Geode LX based processors.
39 - info on the Matrox framebuffer driver for Alpha, Intel and PPC.
55 - info on the framebuffer device driver for various SiS chips.
57 - info on the framebuffer device driver for sm501 videoframebuffer.
63 info on the framebuffer driver for some Trident chip based cards.
73 - info on the VIA Integration Graphic Chip console framebuffer driver.
|
| D | ep93xx-fb.txt | 26 are in pixel clocks. See Documentation/fb/framebuffer.txt for further
39 The framebuffer device can be registered by adding the following to
66 The physical address of the framebuffer can be controlled using the
69 EP93XXFB_USE_SDCSN0 Use SDCSn[0] for the framebuffer. This
72 EP93XXFB_USE_SDCSN1 Use SDCSn[1] for the framebuffer.
74 EP93XXFB_USE_SDCSN2 Use SDCSn[2] for the framebuffer.
76 EP93XXFB_USE_SDCSN3 Use SDCSn[3] for the framebuffer.
82 The EP93xx framebuffer driver supports three optional platform
84 are called when the framebuffer driver is installed and removed
97 /* Board specific framebuffer setup */
[all …]
|
| D | fbcon.txt | 4 The framebuffer console (fbcon), as its name implies, is a text
5 console running on top of the framebuffer device. It has the functionality of
7 features that can be attributed to the graphical nature of the framebuffer.
9 In the x86 architecture, the framebuffer console is optional, and
13 What are the features of fbcon? The framebuffer console supports
20 The framebuffer console can be enabled by using your favorite kernel
26 In order for fbcon to activate, at least one framebuffer driver is
40 GOTCHA: A common bug report is enabling the framebuffer without enabling the
41 framebuffer console. Depending on the driver, you may get a blanked or
59 garbled display, as mentioned above. To get a framebuffer console,
[all …]
|
| D | deferred_io.txt | 9 - userspace app like Xfbdev mmaps framebuffer
19 completes the work associated with updating the framebuffer. this is
24 As can be seen from above, one benefit is roughly to allow bursty framebuffer
26 have gone quiet, we go and really update the framebuffer which would be
37 Another one may be if one has a device framebuffer that is in an usual format,
39 apps to pretend to have a normal framebuffer but reswizzle for the device
40 framebuffer at vsync time based on the touched pagelist.
44 No changes needed. mmap the framebuffer like normal and just use it.
|
| D | udlfb.txt | 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
104 module to track changed areas of the framebuffer by page faults.
[all …]
|
| D | pxafb.txt | 65 base framebuffer (although under-neath the base is also possible). They
68 behave in a similar way as a framebuffer.
74 framebuffer, which means they have a start (x, y). This information
78 2. overlay framebuffer is allocated dynamically according to specified
107 framebuffer:
123 framebuffer framework, application has to take care of the offsets
124 and lengths of each component within the framebuffer.
|
| D | intelfb.txt | 5 This is a framebuffer driver for various Intel 8xx/9xx compatible
43 framebuffer memory. The intent is to avoid the memory blocks
66 enable MTRR. This allows data transfers to the framebuffer memory
96 This will initialize the framebuffer to 800x600 at 32bpp and 75Hz. The
97 framebuffer will use 8 MB of System RAM. hw acceleration of text and cursor
135 framebuffer driver code made this possible.
|
| D | intel810.txt | 13 This is a framebuffer driver for various Intel 810/815 compatible
26 Formula, or a framebuffer specific database to set the video mode
118 framebuffer memory. The intent is to avoid the memory blocks
121 avoid XFree86's usage and allows up to 7 MB/15 MB of framebuffer
137 enable MTRR. This allows data transfers to the framebuffer memory
187 This will initialize the framebuffer to 1024x768 at 8bpp. The framebuffer
245 f. If you want a framebuffer console, enable it under "Console
258 framebuffer driver code made this possible.
|
| /Linux-v4.19/Documentation/media/uapi/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 struct :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>`
94 :ref:`framebuffer-cap`.
99 :ref:`framebuffer-flags`
103 - Physical base address of the framebuffer, that is the address of
104 the pixel in the top left corner of the framebuffer. [#f1]_
113 find the corresponding Linux framebuffer device (see
130 - The pixel format of the framebuffer.
[all …]
|
| /Linux-v4.19/drivers/video/fbdev/geode/ |
| D | Kconfig | 2 # Geode family framebuffer configuration
5 bool "AMD Geode family framebuffer support"
8 Say 'Y' here to allow you to select framebuffer drivers for
12 tristate "AMD Geode LX framebuffer support"
27 tristate "AMD Geode GX framebuffer support"
42 tristate "AMD Geode GX1 framebuffer support"
|
| /Linux-v4.19/Documentation/arm/OMAP/ |
| D | DSS | 41 The DSS driver does not itself have any support for Linux framebuffer, V4L or
120 From omapdss point of view the V4L2 drivers should be similar to framebuffer
132 screen. The overlay may be smaller than framebuffer, thus displaying only
133 part of the framebuffer. The position of the overlay may be changed if
139 A framebuffer can be connected to multiple overlays to show the same pixel data
142 framebuffer can be connected to any overlay.
168 overlays List of overlay numbers to which framebuffer pixels go
169 phys_addr Physical address of the framebuffer
170 virt_addr Virtual address of the framebuffer
171 size Size of the framebuffer
[all …]
|
| /Linux-v4.19/Documentation/media/ |
| D | videodev2.h.rst.exceptions | 192 # V4L2 framebuffer caps and flags
194 replace define V4L2_FBUF_CAP_EXTERNOVERLAY framebuffer-cap
195 replace define V4L2_FBUF_CAP_CHROMAKEY framebuffer-cap
196 replace define V4L2_FBUF_CAP_LIST_CLIPPING framebuffer-cap
197 replace define V4L2_FBUF_CAP_BITMAP_CLIPPING framebuffer-cap
198 replace define V4L2_FBUF_CAP_LOCAL_ALPHA framebuffer-cap
199 replace define V4L2_FBUF_CAP_GLOBAL_ALPHA framebuffer-cap
200 replace define V4L2_FBUF_CAP_LOCAL_INV_ALPHA framebuffer-cap
201 replace define V4L2_FBUF_CAP_SRC_CHROMAKEY framebuffer-cap
203 replace define V4L2_FBUF_FLAG_PRIMARY framebuffer-flags
[all …]
|
| /Linux-v4.19/drivers/video/console/ |
| D | Kconfig | 125 Low-level framebuffer-based console driver.
132 If this option is selected, the framebuffer console will
134 supports this feature). Otherwise, the framebuffer console will
135 always select the first framebuffer driver that is loaded. The latter
147 Enable display rotation for the framebuffer console. This is done
150 such that other users of the framebuffer will remain normally
157 If enabled this defers the framebuffer console taking over the
160 commandline option to keep the framebuffer contents initially put up
|
| /Linux-v4.19/drivers/video/fbdev/ |
| D | Kconfig | 27 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
75 If true, at least one selected framebuffer driver can take advantage
121 (accelerated) version and the framebuffer is in system RAM.
130 version and the framebuffer is in system RAM.
139 (accelerated) version and the framebuffer is in system RAM.
154 non-native endianness (e.g. Little-Endian framebuffer on a
240 tristate "Aeroflex Gaisler framebuffer support"
246 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
304 This framebuffer device driver is for the ARM PrimeCell PL110
360 This is a framebuffer device for the SA-1100 LCD Controller.
[all …]
|
| /Linux-v4.19/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()
|
| /Linux-v4.19/drivers/gpu/drm/vmwgfx/ |
| D | vmwgfx_kms.h | 303 struct vmw_framebuffer *framebuffer,
406 struct vmw_framebuffer *framebuffer,
420 struct vmw_framebuffer *framebuffer,
430 struct vmw_framebuffer *framebuffer,
450 struct vmw_framebuffer *framebuffer,
|
| D | vmwgfx_scrn.c | 787 struct vmw_framebuffer *framebuffer) in do_bo_define_gmrfb() argument
790 container_of(framebuffer, struct vmw_framebuffer_bo, in do_bo_define_gmrfb()
792 int depth = framebuffer->base.format->depth; in do_bo_define_gmrfb()
812 cmd->body.format.bitsPerPixel = framebuffer->base.format->cpp[0] * 8; in do_bo_define_gmrfb()
815 cmd->body.bytesPerLine = framebuffer->base.pitches[0]; in do_bo_define_gmrfb()
936 struct vmw_framebuffer *framebuffer, in vmw_kms_sou_do_surface_dirty() argument
947 container_of(framebuffer, typeof(*vfbs), base); in vmw_kms_sou_do_surface_dirty()
972 ret = vmw_kms_helper_dirty(dev_priv, framebuffer, clips, vclips, in vmw_kms_sou_do_surface_dirty()
1042 struct vmw_framebuffer *framebuffer, in vmw_kms_sou_do_bo_dirty() argument
1051 container_of(framebuffer, struct vmw_framebuffer_bo, in vmw_kms_sou_do_bo_dirty()
[all …]
|
| /Linux-v4.19/Documentation/auxdisplay/ |
| D | cfag12864b | 92 The cfag12864bfb describes a framebuffer device (/dev/fbX).
98 You can use the framebuffer as a file: fopen, fwrite, fclose...
101 Also, you can mmap the framebuffer: open & mmap, munmap & close...
|
