| /linux-6.3-rc2/Documentation/devicetree/bindings/reserved-memory/ |
| A D | framebuffer.yaml | 4 $id: http://devicetree.org/schemas/reserved-memory/framebuffer.yaml#
7 title: /reserved-memory framebuffer node bindings
17 const: framebuffer
19 This indicates a region of memory meant to be used as a framebuffer for
21 the framebuffer from being overwritten and use it as the backing memory
22 for a display device (such as simple-framebuffer).
35 framebuffer {
36 compatible = "simple-framebuffer";
46 fb: framebuffer@80000000 {
47 compatible = "framebuffer";
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/display/ |
| A D | simple-framebuffer.yaml | 20 framebuffer@<address>.
57 - apple,simple-framebuffer
58 - allwinner,simple-framebuffer
59 - amlogic,simple-framebuffer
60 - const: simple-framebuffer
61 - const: simple-framebuffer
91 Format of the framebuffer:
159 const: allwinner,simple-framebuffer
169 const: amlogic,simple-framebuffer
189 framebuffer0: framebuffer@1d385000 {
[all …]
|
| A D | google,goldfish-fb.txt | 1 Android Goldfish framebuffer
3 Android Goldfish framebuffer device used by Android emulator.
|
| A D | arm,hdlcd.yaml | 16 RGB streamer that reads the data from a framebuffer and sends it to a single
39 Phandle to a node describing memory to be used for the framebuffer.
40 If not present, the framebuffer may be located anywhere in memory.
|
| A D | via,vt8500-fb.txt | 7 - interrupts : framebuffer controller interrupt
8 - bits-per-pixel : bit depth of framebuffer (16 or 32)
|
| /linux-6.3-rc2/Documentation/fb/ |
| A 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 …]
|
| A 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
78 The framebuffer console has several, largely unknown, boot options
109 Later on, when you want to map the console the to the framebuffer
144 use the framebuffer will remain at their 'normal' orientation.
[all …]
|
| A 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.
|
| A 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.
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
112 module to track changed areas of the framebuffer by page faults.
125 shadow Allocate a 2nd framebuffer to shadow what's currently across
[all …]
|
| A 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.
|
| A 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.
|
| A 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-6.3-rc2/Documentation/userspace-api/media/v4l/ |
| A 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
56 Example: Finding a framebuffer device for OSD
95 /* Apparently not a framebuffer device. */
102 /* fb_fd is the file descriptor of the framebuffer device
[all …]
|
| A D | vidioc-g-fbuf.rst | 39 to get and set the framebuffer parameters for a
59 :c:type:`v4l2_framebuffer`. Since the framebuffer is
93 :ref:`framebuffer-cap`.
98 :ref:`framebuffer-flags`
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.
198 Together with ``base`` it defines the framebuffer memory
303 framebuffer pixels with video images. The blend function is:
318 framebuffer to clip or blend framebuffer pixels with video images,
[all …]
|
| /linux-6.3-rc2/drivers/video/fbdev/geode/ |
| A D | Kconfig | 3 # Geode family framebuffer configuration
6 bool "AMD Geode family framebuffer support"
10 Say 'Y' here to allow you to select framebuffer drivers for
14 tristate "AMD Geode LX framebuffer support"
30 tristate "AMD Geode GX framebuffer support"
46 tristate "AMD Geode GX1 framebuffer support"
|
| /linux-6.3-rc2/drivers/media/pci/ivtv/ |
| A 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-6.3-rc2/drivers/video/console/ |
| A D | Kconfig | 80 Low-level framebuffer-based console driver.
88 This option enables the fbcon (framebuffer text-based) hardware
107 If this option is selected, the framebuffer console will
109 supports this feature). Otherwise, the framebuffer console will
110 always select the first framebuffer driver that is loaded. The latter
122 Enable display rotation for the framebuffer console. This is done
125 such that other users of the framebuffer will remain normally
132 If enabled this defers the framebuffer console taking over the
135 commandline option to keep the framebuffer contents initially put up
|
| /linux-6.3-rc2/Documentation/arm/omap/ |
| A D | dss.rst | 42 The DSS driver does not itself have any support for Linux framebuffer, V4L or
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
176 input_size width,height (ie. the framebuffer size)
310 framebuffer parameters.
322 - VRAM allocated for a framebuffer. Normally omapfb allocates vram
324 more or define the physical address of each framebuffer. For example,
[all …]
|
| /linux-6.3-rc2/drivers/gpu/drm/tegra/ |
| A D | fb.c | 27 struct tegra_bo *tegra_fb_get_plane(struct drm_framebuffer *framebuffer, in tegra_fb_get_plane() argument
30 return to_tegra_bo(drm_gem_fb_get_obj(framebuffer, index)); in tegra_fb_get_plane()
33 bool tegra_fb_is_bottom_up(struct drm_framebuffer *framebuffer) in tegra_fb_is_bottom_up() argument
35 struct tegra_bo *bo = tegra_fb_get_plane(framebuffer, 0); in tegra_fb_is_bottom_up()
43 int tegra_fb_get_tiling(struct drm_framebuffer *framebuffer, in tegra_fb_get_tiling() argument
46 uint64_t modifier = framebuffer->modifier; in tegra_fb_get_tiling()
|
| /linux-6.3-rc2/Documentation/userspace-api/media/ |
| A D | videodev2.h.rst.exceptions | 236 # V4L2 framebuffer caps and flags
238 replace define V4L2_FBUF_CAP_EXTERNOVERLAY framebuffer-cap
239 replace define V4L2_FBUF_CAP_CHROMAKEY framebuffer-cap
242 replace define V4L2_FBUF_CAP_LOCAL_ALPHA framebuffer-cap
243 replace define V4L2_FBUF_CAP_GLOBAL_ALPHA framebuffer-cap
247 replace define V4L2_FBUF_FLAG_PRIMARY framebuffer-flags
248 replace define V4L2_FBUF_FLAG_OVERLAY framebuffer-flags
249 replace define V4L2_FBUF_FLAG_CHROMAKEY framebuffer-flags
336 replace define V4L2_DV_BT_CAP_INTERLACED framebuffer-cap
337 replace define V4L2_DV_BT_CAP_PROGRESSIVE framebuffer-cap
[all …]
|
| /linux-6.3-rc2/arch/arm64/boot/dts/apple/ |
| A D | t8103-jxxx.dtsi | 27 framebuffer0: framebuffer@0 {
28 compatible = "apple,simple-framebuffer", "simple-framebuffer";
|
| A D | t600x-j314-j316.dtsi | 25 framebuffer0: framebuffer@0 {
26 compatible = "apple,simple-framebuffer", "simple-framebuffer";
|
| A D | t600x-j375.dtsi | 25 framebuffer0: framebuffer@0 {
26 compatible = "apple,simple-framebuffer", "simple-framebuffer";
|
| /linux-6.3-rc2/drivers/video/fbdev/ |
| A D | Kconfig | 115 version and the framebuffer is in system RAM.
586 tristate "TGA/SFB+ framebuffer support"
654 using the EFI framebuffer as your console.
794 completely dumb framebuffer device.
808 completely dumb framebuffer device.
1093 bool "DDC/I2C for Intel framebuffer support"
1664 bool "VIA VT8500 framebuffer support"
1781 tristate "PXA LCD framebuffer support"
1858 tristate "Samsung S3C framebuffer support"
1943 tristate "PS3 GPU framebuffer driver"
[all …]
|
| /linux-6.3-rc2/arch/arm64/boot/dts/qcom/ |
| A D | sdm845-lg-judyp.dts | 17 framebuffer@9d400000 {
18 compatible = "simple-framebuffer";
|