Searched full:framebuffer (Results 1 – 25 of 85) sorted by relevance
1234
| /Documentation/devicetree/bindings/display/ |
| D | simple-framebuffer.yaml | 4 $id: http://devicetree.org/schemas/display/simple-framebuffer.yaml#
7 title: Simple Framebuffer
20 framebuffer@<address>.
47 framebuffer nodes, so that the firmware only needs to update the
52 If pre-filled framebuffer nodes are used, the firmware may need
62 - apple,simple-framebuffer
63 - allwinner,simple-framebuffer
64 - amlogic,simple-framebuffer
65 - const: simple-framebuffer
66 - const: simple-framebuffer
[all …]
|
| D | via,vt8500-fb.txt | 1 VIA VT8500 Framebuffer
7 - interrupts : framebuffer controller interrupt
8 - bits-per-pixel : bit depth of framebuffer (16 or 32)
|
| D | google,goldfish-fb.txt | 1 Android Goldfish framebuffer
3 Android Goldfish framebuffer device used by Android emulator.
|
| D | atmel,lcdc.yaml | 7 title: Microchip's LCDC Framebuffer
14 The LCDC works with a framebuffer, which is a section of memory that contains
16 reads the pixel data from the framebuffer and sends it to the LCD panel to
|
| 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.
|
| D | wm,wm8505-fb.txt | 1 Wondermedia WM8505 Framebuffer
7 - bits-per-pixel : bit depth of framebuffer (16 or 32)
|
| D | cirrus,clps711x-fb.txt | 1 * Cirrus Logic CLPS711X Framebuffer
6 location and size of the framebuffer memory.
|
| D | ssd1289fb.txt | 1 * Solomon SSD1289 Framebuffer Driver
|
| D | arm,pl11x.yaml | 15 a framebuffer region in system memory, and creates timed signals for
70 Phandle to a node describing memory to be used for the framebuffer.
71 If not present, the framebuffer may be located anywhere in memory.
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-osd.rst | 11 Some video output devices can overlay a framebuffer image onto the
35 Framebuffer chapter
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.
[all …]
|
| D | vidioc-g-fbuf.rst | 39 to get and set the framebuffer parameters for a
62 :c:type:`v4l2_framebuffer`. Since the framebuffer is
66 framebuffer parameters as :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>` does, or it returns an error
72 the overlay and returns the framebuffer parameters as :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>`
90 :ref:`framebuffer-cap`.
95 :ref:`framebuffer-flags`
99 - Physical base address of the framebuffer, that is the address of
100 the pixel in the top left corner of the framebuffer.
105 find the corresponding Linux framebuffer device (see
123 - The pixel format of the framebuffer.
[all …]
|
| D | dev-overlay.rst | 9 **Also known as Framebuffer Overlay or Previewing.**
105 4. The framebuffer has an alpha channel that can be used to clip or
106 blend the framebuffer with the video.
108 5. A global alpha value can be specified to blend the framebuffer
184 same as the pixel format of the framebuffer (struct
245 The global alpha value used to blend the framebuffer with video
249 :ref:`framebuffer-flags`).
|
| /Documentation/fb/ |
| D | fbcon.rst | 2 The Framebuffer Console
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
24 Console display driver support->Framebuffer Console Support.
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
[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 | 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 | 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
112 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 | intel810.rst | 2 Intel 810/815 Framebuffer driver
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.
|
| D | sh7760fb.rst | 2 SH7760/SH7763 integrated LCDC Framebuffer driver
13 * Framebuffer memory must be a large chunk allocated at the top
56 get the framebuffer working on a 640x480 TFT::
69 * The linux framebuffer layer does not use the syncstart/synclen
|
| D | sisfb.rst | 5 sisfb is a framebuffer device driver for SiS (Silicon Integrated Systems)
13 Why do I need a framebuffer driver?
85 means 24bit color depth (but 32 bit framebuffer depth, which is not relevant
103 your system) and sisfb (for graphics mode). Under Linux 2.6, also "Framebuffer
126 SVGALib use the framebuffer device for mode switches and restoration.
|
| D | index.rst | 19 framebuffer
|
| /Documentation/arch/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
129 - Framebuffer is a memory area inside OMAP's SRAM/SDRAM that contains the
130 pixel data for the image. Framebuffer has width and height and color
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
[all …]
|
| /Documentation/userspace-api/media/ |
| D | videodev2.h.rst.exceptions | 243 # V4L2 framebuffer caps and flags
245 replace define V4L2_FBUF_CAP_EXTERNOVERLAY framebuffer-cap
246 replace define V4L2_FBUF_CAP_CHROMAKEY framebuffer-cap
247 replace define V4L2_FBUF_CAP_LIST_CLIPPING framebuffer-cap
248 replace define V4L2_FBUF_CAP_BITMAP_CLIPPING framebuffer-cap
249 replace define V4L2_FBUF_CAP_LOCAL_ALPHA framebuffer-cap
250 replace define V4L2_FBUF_CAP_GLOBAL_ALPHA framebuffer-cap
251 replace define V4L2_FBUF_CAP_LOCAL_INV_ALPHA framebuffer-cap
252 replace define V4L2_FBUF_CAP_SRC_CHROMAKEY framebuffer-cap
254 replace define V4L2_FBUF_FLAG_PRIMARY framebuffer-flags
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | xilinx.txt | 92 i) Xilinx ML300 Framebuffer
94 Simple framebuffer device from the ML300 reference design (also on the
98 - resolution = <xres yres> : pixel resolution of framebuffer. Some
101 - virt-resolution = <xvirt yvirt> : Size of framebuffer in memory.
|
| /Documentation/driver-api/ |
| D | aperture.rst | 3 Managing Ownership of the Framebuffer Aperture
|
1234