| /linux-3.3/Documentation/DocBook/media/v4l/ |
| D | dev-osd.xml | 11 <para>Some video output devices can overlay a framebuffer image onto
33 <title>Framebuffer</title>
36 interface the framebuffer is normally implemented on the TV card and
37 not the graphics card. On Linux it is accessible as a framebuffer
39 applications can find the corresponding framebuffer device by calling
41 physical address of the framebuffer in the
42 <structfield>base</structfield> field of &v4l2-framebuffer;. The
43 framebuffer device ioctl <constant>FBIOGET_FSCREENINFO</constant>
50 <para>The width and height of the framebuffer depends on the
52 the video standard (or any other ioctl which would imply a framebuffer
[all …]
|
| D | vidioc-g-fbuf.xml | 62 framebuffer parameters for a <link linkend="overlay">Video
85 <structname>v4l2_framebuffer</structname>. Since the framebuffer is
89 and returns the framebuffer parameters as
98 overlay and returns the framebuffer parameters as
111 <table pgwide="1" frame="none" id="v4l2-framebuffer">
121 <xref linkend="framebuffer-cap" />.</entry>
128 driver, see <xref linkend="framebuffer-flags" /></entry>
134 <entry>Physical base address of the framebuffer,
136 framebuffer.<footnote><para>A physical base address may not suit all
152 framebuffer device (see <xref linkend="osd" />).</entry>
[all …]
|
| /linux-3.3/drivers/video/geode/ |
| D | Kconfig | 2 # Geode family framebuffer configuration
5 bool "AMD Geode family framebuffer support (EXPERIMENTAL)"
8 Say 'Y' here to allow you to select framebuffer drivers for
12 tristate "AMD Geode LX framebuffer support (EXPERIMENTAL)"
18 Framebuffer driver for the display controller integrated into the
27 tristate "AMD Geode GX framebuffer support (EXPERIMENTAL)"
33 Framebuffer driver for the display controller integrated into the
42 tristate "AMD Geode GX1 framebuffer support (EXPERIMENTAL)"
48 Framebuffer driver for the display controller integrated into the
|
| /linux-3.3/drivers/video/ |
| D | Kconfig | 56 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
57 and the Framebuffer-HOWTO at
58 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
98 If true, at least one selected framebuffer driver can take advantage
144 (accelerated) version and the framebuffer is in system RAM.
153 version and the framebuffer is in system RAM.
162 (accelerated) version and the framebuffer is in system RAM.
165 bool "Framebuffer foreign endianness support"
169 non-native endianness (e.g. Little-Endian framebuffer on a
263 tristate "Aeroflex Gaisler framebuffer support"
[all …]
|
| D | s3c-fb.c | 8 * Samsung SoC Framebuffer driver
32 /* This driver will export a number of framebuffer interfaces depending
153 * struct s3c_fb_win - per window private data for each framebuffer.
156 * @fbinfo: Pointer pack to the framebuffer info for this window.
233 * s3c_fb_check_var() - framebuffer layer request to verify a given mode.
235 * @info: The framebuffer device.
237 * Framebuffer layer call to verify the given information and allow us to
447 * @sfb: The main framebuffer state.
460 /* see the note in the framebuffer datasheet about in s3c_fb_enable()
479 * s3c_fb_set_par() - framebuffer request to set new framebuffer state.
[all …]
|
| D | grvga.c | 2 * Driver for Aeroflex Gaisler SVGACTRL framebuffer device.
49 int fb_alloced; /* = 1 if framebuffer is allocated in main memory */
252 /* Set framebuffer base address */ in grvga_pan_display()
349 /* Expecting: "grvga: modestring, [addr:<framebuffer physical address>], [size:<framebuffer size>] in grvga_probe()
426 /* Got framebuffer base address from argument list */ in grvga_probe()
439 dev_err(&dev->dev, "error mapping framebuffer memory\n"); in grvga_probe()
451 "unable to allocate framebuffer memory (%lu bytes)\n", in grvga_probe()
480 "Aeroflex Gaisler framebuffer device (fb%d), %dx%d-%d, using %luK of video memory @ %p\n", in grvga_probe()
486 dev_err(&dev->dev, "failed to register framebuffer\n"); in grvga_probe()
491 __raw_writel(__raw_readl(&par->regs->status) | 1, /* Enable framebuffer */ in grvga_probe()
[all …]
|
| /linux-3.3/Documentation/fb/ |
| D | fbcon.txt | 1 The Framebuffer Console
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
22 framebuffer devices->Framebuffer Console Support. Select 'y' to compile
25 In order for fbcon to activate, at least one framebuffer driver is
39 GOTCHA: A common bug report is enabling the framebuffer without enabling the
[all …]
|
| D | 00-INDEX | 23 - intro to and usage guide for the framebuffer console (fbcon).
24 framebuffer.txt
27 - info on the framebuffer driver for AMD Geode GX2 based processors.
29 - documentation for the Intel 810/815 framebuffer driver.
35 - info on the framebuffer driver for AMD Geode LX based processors.
37 - info on the Matrox framebuffer driver for Alpha, Intel and PPC.
51 - info on the SH7760/SH7763 integrated LCDC Framebuffer driver.
53 - info on the framebuffer device driver for various SiS chips.
59 info on the framebuffer driver for some Trident chip based cards.
67 - 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 | 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 | 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 | intelfb.txt | 1 Intel 830M/845G/852GM/855GM/865G/915G/945G Framebuffer driver
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 | 1 Intel 810/815 Framebuffer driver
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.
|
| 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.
|
| /linux-3.3/Documentation/arm/OMAP/ |
| D | DSS | 41 The DSS driver does not itself have any support for Linux framebuffer, V4L or
75 From omapdss point of view the V4L2 drivers should be similar to framebuffer
83 - Framebuffer is a memory area inside OMAP's SRAM/SDRAM that contains the
84 pixel data for the image. Framebuffer has width and height and color
87 screen. The overlay may be smaller than framebuffer, thus displaying only
88 part of the framebuffer. The position of the overlay may be changed if
94 A framebuffer can be connected to multiple overlays to show the same pixel data
97 framebuffer can be connected to any overlay.
123 overlays List of overlay numbers to which framebuffer pixels go
124 phys_addr Physical address of the framebuffer
[all …]
|
| /linux-3.3/include/xen/interface/io/ |
| D | fbif.h | 38 * Framebuffer update notification event
53 * Framebuffer resize notification event
64 int32_t offset; /* start offset within framebuffer */
112 int32_t width; /* width of the framebuffer (in pixels) */
113 int32_t height; /* height of the framebuffer (in pixels) */
115 uint32_t mem_length; /* length of the framebuffer (in bytes) */
119 * Framebuffer page directory
122 * framebuffer pages, and can thus map up to PAGE_SIZE *
126 * Meg framebuffer with a max resolution of 12,800x10,240.
|
| /linux-3.3/drivers/video/console/ |
| D | Kconfig | 91 tristate "Framebuffer Console support"
95 Low-level framebuffer-based console driver.
102 If this option is selected, the framebuffer console will
104 supports this feature). Otherwise, the framebuffer console will
105 always select the first framebuffer driver that is loaded. The latter
114 bool "Framebuffer Console Rotation"
117 Enable display rotation for the framebuffer console. This is done
120 such that other users of the framebuffer will remain normally
175 framebuffer drivers don't support this one at all.
|
| /linux-3.3/include/linux/ |
| D | matroxfb.h | 26 /* connect these outputs to this framebuffer */
28 /* which outputs are connected to this framebuffer */
30 /* which outputs are available for this framebuffer */
32 /* which outputs exist on this framebuffer */
|
| D | xilinxfb.h | 2 * Platform device data for Xilinx Framebuffer device
16 /* ML300/403 reference design framebuffer driver platform data struct */
24 /* Physical address of framebuffer memory; If non-zero, driver
|
| /linux-3.3/drivers/gpu/drm/gma500/ |
| D | framebuffer.c | 40 #include "framebuffer.h"
267 * psb_framebuffer_init - initialize a framebuffer
269 * @fb: framebuffer to set up
299 dev_err(dev->dev, "framebuffer init failed: %d\n", ret); in psb_framebuffer_init()
308 * psb_framebuffer_create - create a framebuffer backed by gt
313 * Create a framebuffer object backed by the gt, and fill in the
350 * Re-address this as and if the framebuffer layer grows this ability.
367 * psbfb_create - create a framebuffer
368 * @fbdev: the framebuffer device
371 * Create a framebuffer to the specifications provided
[all …]
|
| /linux-3.3/drivers/gpu/drm/exynos/ |
| D | exynos_drm_gem.h | 55 * by user request or at framebuffer creation.
57 * or at framebuffer creation.
76 * that it is calculated with framebuffer information such as width,
99 /* create memory region for drm framebuffer. */
104 /* map memory region for drm framebuffer to user space. */
|
| D | exynos_drm_drv.h | 72 * @fb_x: offset x on a framebuffer to be displayed.
74 * @fb_y: offset y on a framebuffer to be displayed.
76 * @fb_width: width of a framebuffer.
77 * @fb_height: height of a framebuffer.
179 * @ops: pointer to callbacks for exynos drm specific framebuffer.
182 * @overlay_ops: pointer to callbacks for exynos drm specific framebuffer.
185 * @display: pointer to callbacks for exynos drm specific framebuffer.
|
| D | exynos_drm_fb.c | 41 * exynos specific framebuffer structure.
43 * @fb: drm framebuffer obejct.
103 DRM_ERROR("failed to allocate exynos drm framebuffer\n"); in exynos_drm_framebuffer_init()
109 DRM_ERROR("failed to initialize framebuffer\n"); in exynos_drm_framebuffer_init()
206 * this value would be used to check framebuffer size limitation in exynos_drm_mode_config_init()
|
| /linux-3.3/drivers/gpu/drm/vmwgfx/ |
| D | vmwgfx_kms.c | 373 * Generic framebuffer code
387 * Surface framebuffer code
401 void vmw_framebuffer_surface_destroy(struct drm_framebuffer *framebuffer) in vmw_framebuffer_surface_destroy() argument
404 vmw_framebuffer_to_vfbs(framebuffer); in vmw_framebuffer_surface_destroy()
413 drm_framebuffer_cleanup(framebuffer); in vmw_framebuffer_surface_destroy()
422 struct vmw_framebuffer *framebuffer, in do_surface_dirty_sou() argument
445 if (crtc->fb != &framebuffer->base) in do_surface_dirty_sou()
535 cmd->body.srcImage.sid = cpu_to_le32(framebuffer->user_handle); in do_surface_dirty_sou()
564 int vmw_framebuffer_surface_dirty(struct drm_framebuffer *framebuffer, in vmw_framebuffer_surface_dirty() argument
570 struct vmw_private *dev_priv = vmw_priv(framebuffer->dev); in vmw_framebuffer_surface_dirty()
[all …]
|
| /linux-3.3/arch/sh/include/asm/ |
| D | sh7760fb.h | 2 * sh7760fb.h -- platform data for SH7760/SH7763 LCDC framebuffer driver.
24 /* framebuffer registers and bits */
109 /* framebuffer color layout */
139 * be used by other framebuffer layer components.
157 /* LDDFR controls framebuffer image format (depth, organization)
|