| /linux-4.4.14/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"
26 framebuffer@0 {
27 compatible = "allwinner,simple-framebuffer", "simple-framebuffer";
|
| D | via,vt8500-fb.txt | 7 - interrupts : framebuffer controller interrupt
8 - bits-per-pixel : bit depth of framebuffer (16 or 32)
|
| D | atmel,lcdc.txt | 15 for fixed framebuffer memory. Useful for dedicated memories.
16 - interrupts : framebuffer controller interrupt
43 Example for fixed framebuffer memory:
|
| D | wm,wm8505-fb.txt | 7 - bits-per-pixel : bit depth of framebuffer (16 or 32)
|
| D | arm,pl11x.txt | 31 to be used for the framebuffer; if not present, the framebuffer
|
| D | marvell,pxa2xx-lcdc.txt | 10 - interrupts : framebuffer controller interrupt.
|
| D | cirrus,clps711x-fb.txt | 6 location and size of the framebuffer memory.
|
| /linux-4.4.14/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
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
40 framebuffer console. Depending on the driver, you may get a blanked or
[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.
|
| D | sm712fb.txt | 4 This is a graphics framebuffer driver for Silicon Motion SM712 based processors.
|
| D | sisfb.txt | 5 sisfb is a framebuffer device driver for SiS (Silicon Integrated Systems)
13 Why do I need a framebuffer driver?
84 means 24bit color depth (but 32 bit framebuffer depth, which is not relevant
125 SVGALib use the framebuffer device for mode switches and restoration.
|
| D | sh7760fb.txt | 53 get the framebuffer working on a 640x480 TFT:
68 * The linux framebuffer layer does not use the syncstart/synclen
|
| D | sa1100fb.txt | 6 This is a driver for a graphic framebuffer for the SA-1100 LCD
|
| D | gxfb.txt | 6 This is a graphics framebuffer driver for AMD Geode GX2 based processors.
|
| D | lxfb.txt | 6 This is a graphics framebuffer driver for AMD Geode LX based processors.
|
| D | vesafb.txt | 5 This is a generic driver for a graphic framebuffer on intel boxes.
8 of the BIOS, and use this as framebuffer device /dev/fb0, like the m68k
147 mtrr:n setup memory type range registers for the vesafb framebuffer
|
| D | metronomefb.txt | 12 host CPU generates the control information and the image in a framebuffer
|
| D | aty128fb.txt | 6 This is a driver for a graphic framebuffer for ATI Rage128 based devices
|
| D | tridentfb.txt | 1 Tridentfb is a framebuffer driver for some Trident chip based cards.
|
| D | matroxfb.txt | 6 This is a driver for a graphic framebuffer for Matrox devices on
203 displayed through putc/putcs. Direct accesses to framebuffer
295 + If you are using more than one framebuffer device, you must boot kernel
|
| D | modedb.txt | 84 From the framebuffer subsystem perspective, new formats need not be added
|
| D | uvesafb.txt | 82 mtrr:n Setup memory type range registers for the framebuffer
|
| D | viafb.txt | 6 The console framebuffer driver is for graphics chips of
|
| D | framebuffer.txt | 340 `X-framebuffer.README' by Roman Hodek and Martin Schaller. Section 6 was
|
| /linux-4.4.14/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-4.4.14/drivers/gpu/drm/tegra/ |
| D | fb.c | 28 struct tegra_bo *tegra_fb_get_plane(struct drm_framebuffer *framebuffer, in tegra_fb_get_plane() argument
31 struct tegra_fb *fb = to_tegra_fb(framebuffer); in tegra_fb_get_plane()
33 if (index >= drm_format_num_planes(framebuffer->pixel_format)) in tegra_fb_get_plane()
39 bool tegra_fb_is_bottom_up(struct drm_framebuffer *framebuffer) in tegra_fb_is_bottom_up() argument
41 struct tegra_fb *fb = to_tegra_fb(framebuffer); in tegra_fb_is_bottom_up()
49 int tegra_fb_get_tiling(struct drm_framebuffer *framebuffer, in tegra_fb_get_tiling() argument
52 struct tegra_fb *fb = to_tegra_fb(framebuffer); in tegra_fb_get_tiling()
60 static void tegra_fb_destroy(struct drm_framebuffer *framebuffer) in tegra_fb_destroy() argument
62 struct tegra_fb *fb = to_tegra_fb(framebuffer); in tegra_fb_destroy()
76 drm_framebuffer_cleanup(framebuffer); in tegra_fb_destroy()
[all …]
|
| D | drm.h | 264 struct tegra_bo *tegra_fb_get_plane(struct drm_framebuffer *framebuffer,
266 bool tegra_fb_is_bottom_up(struct drm_framebuffer *framebuffer);
267 int tegra_fb_get_tiling(struct drm_framebuffer *framebuffer,
|
| /linux-4.4.14/drivers/gpu/drm/imx/ |
| D | Kconfig | 14 tristate "provide legacy framebuffer /dev/fb0"
18 The DRM framework can provide a legacy /dev/fb0 framebuffer
19 for your device. This is necessary to get a framebuffer console
20 and also for applications using the legacy framebuffer API
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | sun5i-a10s.dtsi | 64 framebuffer@0 {
65 compatible = "allwinner,simple-framebuffer",
66 "simple-framebuffer";
73 framebuffer@1 {
74 compatible = "allwinner,simple-framebuffer",
75 "simple-framebuffer";
81 framebuffer@2 {
82 compatible = "allwinner,simple-framebuffer",
83 "simple-framebuffer";
|
| D | sun5i-r8.dtsi | 50 framebuffer@1 {
51 compatible = "allwinner,simple-framebuffer",
52 "simple-framebuffer";
|
| D | sun4i-a10.dtsi | 64 framebuffer@0 {
65 compatible = "allwinner,simple-framebuffer",
66 "simple-framebuffer";
73 framebuffer@1 {
74 compatible = "allwinner,simple-framebuffer",
75 "simple-framebuffer";
82 framebuffer@2 {
83 compatible = "allwinner,simple-framebuffer",
84 "simple-framebuffer";
91 framebuffer@3 {
[all …]
|
| D | sun5i-a13.dtsi | 60 framebuffer@0 {
61 compatible = "allwinner,simple-framebuffer",
62 "simple-framebuffer";
|
| D | sun7i-a20.dtsi | 66 framebuffer@0 {
67 compatible = "allwinner,simple-framebuffer",
68 "simple-framebuffer";
75 framebuffer@1 {
76 compatible = "allwinner,simple-framebuffer",
77 "simple-framebuffer";
83 framebuffer@2 {
84 compatible = "allwinner,simple-framebuffer",
85 "simple-framebuffer";
|
| D | sun6i-a31.dtsi | 64 simplefb_hdmi: framebuffer@0 {
65 compatible = "allwinner,simple-framebuffer",
66 "simple-framebuffer";
72 simplefb_lcd: framebuffer@1 {
73 compatible = "allwinner,simple-framebuffer",
74 "simple-framebuffer";
|
| D | sun8i-a23-a33.dtsi | 59 framebuffer@0 {
60 compatible = "allwinner,simple-framebuffer",
61 "simple-framebuffer";
|
| /linux-4.4.14/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-4.4.14/drivers/gpu/drm/vmwgfx/ |
| D | vmwgfx_kms.h | 213 struct vmw_framebuffer *framebuffer,
264 struct vmw_framebuffer *framebuffer,
279 struct vmw_framebuffer *framebuffer,
288 struct vmw_framebuffer *framebuffer,
306 struct vmw_framebuffer *framebuffer,
|
| D | vmwgfx_scrn.c | 689 struct vmw_framebuffer *framebuffer) in do_dmabuf_define_gmrfb() argument
692 container_of(framebuffer, struct vmw_framebuffer_dmabuf, in do_dmabuf_define_gmrfb()
694 int depth = framebuffer->base.depth; in do_dmabuf_define_gmrfb()
714 cmd->body.format.bitsPerPixel = framebuffer->base.bits_per_pixel; in do_dmabuf_define_gmrfb()
717 cmd->body.bytesPerLine = framebuffer->base.pitches[0]; in do_dmabuf_define_gmrfb()
832 struct vmw_framebuffer *framebuffer, in vmw_kms_sou_do_surface_dirty() argument
842 container_of(framebuffer, typeof(*vfbs), base); in vmw_kms_sou_do_surface_dirty()
865 ret = vmw_kms_helper_dirty(dev_priv, framebuffer, clips, vclips, in vmw_kms_sou_do_surface_dirty()
927 struct vmw_framebuffer *framebuffer, in vmw_kms_sou_do_dmabuf_dirty() argument
934 container_of(framebuffer, struct vmw_framebuffer_dmabuf, in vmw_kms_sou_do_dmabuf_dirty()
[all …]
|
| D | vmwgfx_kms.c | 406 static void vmw_framebuffer_surface_destroy(struct drm_framebuffer *framebuffer) in vmw_framebuffer_surface_destroy() argument
409 vmw_framebuffer_to_vfbs(framebuffer); in vmw_framebuffer_surface_destroy()
411 drm_framebuffer_cleanup(framebuffer); in vmw_framebuffer_surface_destroy()
419 static int vmw_framebuffer_surface_dirty(struct drm_framebuffer *framebuffer, in vmw_framebuffer_surface_dirty() argument
425 struct vmw_private *dev_priv = vmw_priv(framebuffer->dev); in vmw_framebuffer_surface_dirty()
427 vmw_framebuffer_to_vfbs(framebuffer); in vmw_framebuffer_surface_dirty()
447 norect.x2 = framebuffer->width; in vmw_framebuffer_surface_dirty()
448 norect.y2 = framebuffer->height; in vmw_framebuffer_surface_dirty()
614 static void vmw_framebuffer_dmabuf_destroy(struct drm_framebuffer *framebuffer) in vmw_framebuffer_dmabuf_destroy() argument
617 vmw_framebuffer_to_vfbd(framebuffer); in vmw_framebuffer_dmabuf_destroy()
[all …]
|
| D | Kconfig | 21 bool "Enable framebuffer console under vmwgfx by default"
|
| D | vmwgfx_stdu.c | 994 struct vmw_framebuffer *framebuffer, in vmw_kms_stdu_surface_dirty() argument
1004 container_of(framebuffer, typeof(*vfbs), base); in vmw_kms_stdu_surface_dirty()
1030 ret = vmw_kms_helper_dirty(dev_priv, framebuffer, clips, vclips, in vmw_kms_stdu_surface_dirty()
|
| D | vmwgfx_ldu.c | 457 struct vmw_framebuffer *framebuffer, in vmw_kms_ldu_do_dmabuf_dirty() argument
|
| /linux-4.4.14/drivers/video/console/ |
| D | Kconfig | 105 Low-level framebuffer-based console driver.
112 If this option is selected, the framebuffer console will
114 supports this feature). Otherwise, the framebuffer console will
115 always select the first framebuffer driver that is loaded. The latter
127 Enable display rotation for the framebuffer console. This is done
130 such that other users of the framebuffer will remain normally
|
| D | fbcon.c | 3300 con2fb->framebuffer, 1); in fbcon_event_notify()
3304 con2fb->framebuffer = con2fb_map[con2fb->console - 1]; in fbcon_event_notify()
|
| /linux-4.4.14/drivers/video/fbdev/ |
| D | Kconfig | 26 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
71 If true, at least one selected framebuffer driver can take advantage
117 (accelerated) version and the framebuffer is in system RAM.
126 version and the framebuffer is in system RAM.
135 (accelerated) version and the framebuffer is in system RAM.
142 non-native endianness (e.g. Little-Endian framebuffer on a
228 tristate "Aeroflex Gaisler framebuffer support"
234 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
290 This framebuffer device driver is for the ARM PrimeCell PL110
344 This is a framebuffer device for the SA-1100 LCD Controller.
[all …]
|
| /linux-4.4.14/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...
|
| /linux-4.4.14/arch/avr32/boards/hammerhead/ |
| D | Kconfig | 17 also add support for framebuffer devices (AT91/AT32 LCD Controller)
18 and framebuffer console support to get the most out of your LCD.
|
| /linux-4.4.14/Documentation/devicetree/bindings/reserved-memory/ |
| D | reserved-memory.txt | 27 reflect the purpose of the node (ie. "framebuffer" or "dma-pool"). Unit
82 one dedicated to the framebuffer device (named framebuffer@78000000, 8MiB), and
107 display_reserved: framebuffer@78000000 {
|
| /linux-4.4.14/drivers/media/pci/ivtv/ |
| D | Kconfig | 48 tristate "Conexant cx23415 framebuffer support"
54 This is a framebuffer driver for the Conexant cx23415 MPEG
|
| /linux-4.4.14/drivers/staging/sm750fb/ |
| D | Kconfig | 2 tristate "Silicon Motion SM750 framebuffer support"
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | as3711.txt | 14 - su1-dev : framebuffer phandle
19 - su2-dev : framebuffer phandle
|
| /linux-4.4.14/drivers/staging/media/lirc/ |
| D | TODO | 6 framebuffer driver (atyfb) and userland X driver (mach64). It can't
|
| /linux-4.4.14/drivers/gpu/drm/gma500/ |
| D | Makefile | 9 framebuffer.o \
|
| D | Kconfig | 15 Say yes for an experimental 2D KMS framebuffer driver for the
|
| /linux-4.4.14/drivers/video/fbdev/omap2/dss/ |
| D | Kconfig | 57 such as a display or a framebuffer chip.
102 processor and a peripheral, such as a display or a framebuffer chip.
|
| /linux-4.4.14/drivers/auxdisplay/ |
| D | Kconfig | 90 Depends on the x86 arch and the framebuffer support.
92 The LCD framebuffer driver can be attached to a console.
|
| /linux-4.4.14/Documentation/frv/ |
| D | configuring.txt | 88 Includes framebuffer driver.
117 framebuffer driver.
|
| /linux-4.4.14/lib/fonts/ |
| D | Kconfig | 52 framebuffer drivers don't support this one at all.
86 Medium-size console font. Suitable for framebuffer consoles on
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/imx/ |
| D | fsl,imx-fb.txt | 3 This framebuffer driver supports devices imx1, imx21, imx25, and imx27.
|
| /linux-4.4.14/arch/m68k/ |
| D | Kconfig.debug | 18 Where implemented, output goes to the framebuffer as well.
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | sysfs-bus-xen-backend | 7 'vif' (network), or 'vfb' (framebuffer).
|
| /linux-4.4.14/arch/sh/drivers/dma/ |
| D | Kconfig | 58 This is primarily used by the pvr2fb framebuffer driver for
|
| /linux-4.4.14/Documentation/devicetree/bindings/ |
| D | xilinx.txt | 237 Simple framebuffer device from the ML300 reference design (also on the
241 - resolution = <xres yres> : pixel resolution of framebuffer. Some
244 - virt-resolution = <xvirt yvirt> : Size of framebuffer in memory.
|
| /linux-4.4.14/Documentation/DocBook/ |
| D | gpu.xml.db | 142 API-drm-framebuffer-init
143 API-drm-framebuffer-lookup
144 API-drm-framebuffer-unreference
145 API-drm-framebuffer-reference
146 API-drm-framebuffer-unregister-private
147 API-drm-framebuffer-cleanup
148 API-drm-framebuffer-remove
|
| D | device-drivers.xml.db | 956 API-register-framebuffer
957 API-unregister-framebuffer
|
| /linux-4.4.14/Documentation/console/ |
| D | console.txt | 90 framebuffer console to VGA console and vice versa, this feature also makes
136 with the framebuffer console that suddenly lost all of its drivers.
|
| /linux-4.4.14/arch/openrisc/ |
| D | README.openrisc | 96 added opencores framebuffer driver.
|
| /linux-4.4.14/include/uapi/linux/ |
| D | fb.h | 291 __u32 framebuffer; member
|
| /linux-4.4.14/Documentation/devicetree/bindings/leds/ |
| D | common.txt | 24 "backlight" - LED will act as a back-light, controlled by the framebuffer
|
| /linux-4.4.14/Documentation/x86/ |
| D | mtrr.txt | 84 server, which tells you where the linear framebuffer address is. A
90 move the framebuffer base address, so the only value you can trust is
93 To find out the size of your framebuffer (what, you don't actually
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | README.ivtv | 38 * Provides a framebuffer (allowing X applications to appear on the video
62 support the framebuffer device /dev/fbx for OSD.
|
| D | vivid.txt | 6 defined radio receiver. In addition a simple framebuffer device is available for
1023 option the vivid driver will create a simple framebuffer device that can be
1038 In addition, the pixelformat of the capture format and that of the framebuffer
1043 instances: the first with a framebuffer enabled. You configure the capture
1044 overlay of the second instance to use the framebuffer of the first, then
1047 to see the blended framebuffer overlay that's being written to by the second
1052 /dev/fb1 is the framebuffer associated with base address 0x12800000
1096 pixelformat of the capture format and that of the framebuffer must be the
1100 framebuffer by setting flag 0x10000 in the node_types module option. The
1101 created framebuffer has a size of 720x576 and supports ARGB 1:5:5:5 and
|
| D | v4l2-framework.txt | 143 hardware. E.g. the ivtvfb driver is a framebuffer driver that uses the ivtv
|
| /linux-4.4.14/drivers/video/fbdev/core/ |
| D | fbmem.c | 1169 con2fb.framebuffer = -1; in do_fb_ioctl()
1183 if (con2fb.framebuffer >= FB_MAX) in do_fb_ioctl()
1185 if (!registered_fb[con2fb.framebuffer]) in do_fb_ioctl()
1186 request_module("fb%d", con2fb.framebuffer); in do_fb_ioctl()
1187 if (!registered_fb[con2fb.framebuffer]) { in do_fb_ioctl()
|
| /linux-4.4.14/Documentation/zh_CN/ |
| D | SubmittingPatches | 137 。其它的邮件列表为特定的子系统提供服务，比如 USB，framebuffer 设备，虚
|
| /linux-4.4.14/arch/arm64/boot/dts/arm/ |
| D | rtsm_ve-motherboard.dtsi | 188 arm,pl11x,framebuffer = <0x18000000 0x00180000>;
|
| /linux-4.4.14/drivers/staging/fbtft/ |
| D | Kconfig | 148 This enables generic framebuffer support for the Sitronix ST7789V
|
| /linux-4.4.14/include/drm/ |
| D | drm_crtc.h | 163 void (*destroy)(struct drm_framebuffer *framebuffer);
179 int (*dirty)(struct drm_framebuffer *framebuffer,
|
| /linux-4.4.14/arch/x86/ |
| D | Kconfig.debug | 59 bool "Early printk via the EFI framebuffer"
63 Write kernel log output directly into the EFI framebuffer.
|
| D | Kconfig | 2571 bool "Mark VGA/VBE/EFI FB as generic system framebuffer"
2579 framebuffers so the new generic system-framebuffer drivers can be
2580 used on x86. If the framebuffer is not compatible with the generic
2581 modes, it is adverticed as fallback platform framebuffer so legacy
2591 and others enabled as fallback if a system framebuffer is
|
| /linux-4.4.14/arch/arm/plat-samsung/ |
| D | Kconfig | 143 Compile in platform device definition for framebuffer
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | Insmod-options | 24 bigendian=n Set the endianness of the gfx framebuffer.
|
| /linux-4.4.14/arch/arm/mach-davinci/ |
| D | Kconfig | 153 Say Y here to use the LCD as a framebuffer or simple character
|
| /linux-4.4.14/Documentation/ |
| D | bus-virt-phys-mapping.txt | 155 * remap framebuffer PCI memory area at 0xFC000000,
|
| D | sysrq.txt | 116 'v' - Forcefully restores framebuffer console
|
| D | nommu-mmap.txt | 233 implement it. Such is the case for the framebuffer driver which attempts to
|
| D | kernel-parameters.txt | 2133 the TFT driver, and the framebuffer will be left
|
| /linux-4.4.14/drivers/tty/ |
| D | Kconfig | 91 drivers may be enabled, such as the framebuffer console. If more than
97 information. For framebuffer console users, please refer to
|
| /linux-4.4.14/arch/powerpc/ |
| D | Kconfig.debug | 89 framebuffer memory).
|
| /linux-4.4.14/ |
| D | CREDITS | 406 D: newport abscon driver, g364 framebuffer driver
1066 D: DECstation framebuffer drivers
1648 D: Generic 68k Macintosh framebuffer driver
1649 D: STI framebuffer tweaks
2019 D: NeoMagic framebuffer driver
2051 D: Arc monochrome LCD framebuffer driver, x86 reboot fixups
2460 D: DECstation framebuffer drivers
3693 D: Matrox framebuffer driver
|
| D | MAINTAINERS | 9710 F: Documentation/devicetree/bindings/display/simple-framebuffer.txt
|
| /linux-4.4.14/drivers/video/backlight/ |
| D | Kconfig | 21 Some framebuffer devices connect to platform-specific LCD modules
|
| /linux-4.4.14/Documentation/ioctl/ |
| D | botching-up-ioctls.txt | 182 framebuffer objects, which mostly are not shared at all. A separate
|
| /linux-4.4.14/arch/sparc/ |
| D | Kconfig | 234 Say Y here to enable a faster early framebuffer boot console.
|
| /linux-4.4.14/drivers/staging/unisys/Documentation/ |
| D | overview.txt | 44 * Because the s-Par back-end provides a standard EFI framebuffer to each
|
| /linux-4.4.14/drivers/tty/serial/ |
| D | Kconfig | 41 Even if you say Y here, the currently visible framebuffer console
69 Even if you say Y here, the currently visible framebuffer console
887 Even if you say Y here, the currently visible framebuffer console
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | mmu.txt | 23 and framebuffer-based displays
|
| /linux-4.4.14/drivers/hid/ |
| D | Kconfig | 621 framebuffer device.
|
| /linux-4.4.14/Documentation/m68k/ |
| D | kernel-options.txt | 519 If this option is given, the framebuffer device doesn't do any video
|