| /linux-3.3/Documentation/fb/ |
| D | framebuffer.txt | 1 The Frame Buffer Device
2 -----------------------
4 Maintained by Geert Uytterhoeven <geert@linux-m68k.org>
9 ---------------
11 The frame buffer device provides an abstraction for the graphics hardware. It
12 represents the frame buffer of some video hardware and allows application
13 software to access the graphics hardware through a well-defined interface, so
14 the software doesn't need to know anything about the low-level (hardware
22 --------------------------
24 From the user's point of view, the frame buffer device looks just like any
[all …]
|
| D | 00-INDEX | 1 Index of files in Documentation/fb. If you think something about frame
2 buffer devices needs an entry here, needs correction or you've written one
4 Geert Uytterhoeven <geert@linux-m68k.org>
6 00-INDEX
7 - this file.
9 - info on the fbdev driver for ARK Logic chips.
11 - info on the ATI Rage128 frame buffer driver.
13 - info on the driver for Cirrus Logic chipsets.
15 - an introduction to fbdev's cmap structures.
17 - an introduction to deferred IO.
[all …]
|
| D | modedb.txt | 6 Currently all frame buffer device drivers have their own video mode databases,
9 - one routine to probe for video modes, which can be used by all frame buffer
11 - one generic video mode database with a fair amount of standard videomodes
13 - the possibility to supply your own mode database for graphics hardware that
14 needs non-standard modes, like amifb and Mac frame buffer drivers (which
17 When a frame buffer device receives a video= option it doesn't know, it should
18 consider that to be a video mode option. If no frame buffer device is specified
23 <xres>x<yres>[M][R][-<bpp>][@<refresh>][i][m][eDd]
24 <name>[-<bpp>][@<refresh>]
37 Sample usage: 1024x768M@60m - CVT timing with margins
[all …]
|
| D | api.txt | 1 The Frame Buffer Device API
2 ---------------------------
8 ---------------
10 This document describes the frame buffer API used by applications to interact
11 with frame buffer devices. In-kernel APIs between device drivers and the frame
12 buffer core are not described.
14 Due to a lack of documentation in the original frame buffer API, drivers
21 ---------------
35 - FB_CAP_FOURCC
43 --------------------
[all …]
|
| D | internals.txt | 2 This is a first start for some documentation about frame buffer device
5 Geert Uytterhoeven <geert@linux-m68k.org>, 21 July 1998
8 --------------------------------------------------------------------------------
10 *** STRUCTURES USED BY THE FRAME BUFFER DEVICE API ***
12 The following structures play a role in the game of frame buffer devices. They
17 - struct fb_fix_screeninfo
19 Device independent unchangeable information about a frame buffer device and
23 - struct fb_var_screeninfo
25 Device independent changeable information about a frame buffer device and a
30 - struct fb_cmap
[all …]
|
| /linux-3.3/drivers/video/ |
| D | Kconfig | 33 This framework adds support for low-level control of the video
37 tristate "Support for frame buffer devices"
38 ---help---
39 The frame buffer device provides an abstraction for the graphics
40 hardware. It represents the frame buffer of some video hardware and
42 a well-defined interface, so the software doesn't need to know
43 anything about the low-level (hardware register) stuff.
45 Frame buffer devices work identically across the different
48 server exists which uses the frame buffer device exclusively.
49 On several non-X86 architectures, the frame buffer device is the
[all …]
|
| D | skeletonfb.c | 2 * linux/drivers/video/skeletonfb.c -- Skeleton for a frame buffer device
60 * Even less warranty that it actually works :-)
106 * This allows when one display changes it video resolution (info->var)
137 * xxxfb_open - Optional function. Called when the framebuffer is
139 * @info: frame buffer structure that represents a single frame buffer
156 * xxxfb_release - Optional function. Called when the framebuffer
158 * @info: frame buffer structure that represents a single frame buffer
175 * xxxfb_check_var - Optional function. Validates a var passed in.
176 * @var: frame buffer variable screen structure
177 * @info: frame buffer structure that represents a single frame buffer
[all …]
|
| /linux-3.3/drivers/scsi/isci/ |
| D | unsolicited_frame_control.h | 7 * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
20 * Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
26 * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
64 * struct scu_unsolicited_frame_header -
66 * This structure delineates the format of an unsolicited frame header. The
83 * This field indicates if the frame is an address frame (IAF or OAF)
84 * or if it is a information unit frame.
89 * This field simply indicates the connection rate at which the frame
106 * enum unsolicited_frame_state -
108 * This enumeration represents the current unsolicited frame state. The
[all …]
|
| /linux-3.3/drivers/media/video/usbvision/ |
| D | usbvision-core.c | 2 * usbvision-core.c - driver for NT100x USB video capture devices
5 * Copyright (c) 1999-2005 Joerg Heckenbach <joerg@heckenbach-aw.de>
41 #include <media/v4l2-common.h>
56 /* To help people with Black and White output with using s-video input.
60 MODULE_PARM_DESC(switch_svideo_input, " Set the S-Video input. Some cables and input device are wi…
62 static unsigned int adjust_x_offset = -1;
66 static unsigned int adjust_y_offset = -1;
98 * is too slow. Larger buffers are memory-consuming and take longer
102 #define DEFAULT_SCRATCH_BUF_SIZE (0x20000) /* 128kB memory scratch buffer */
135 size -= PAGE_SIZE; in usbvision_rvmalloc()
[all …]
|
| /linux-3.3/Documentation/networking/ |
| D | packet_mmap.txt | 1 --------------------------------------------------------------------------------
3 --------------------------------------------------------------------------------
14 http://wiki.gnu-log.net (packet_mmap)
18 Johann Baudy <johann.baudy@gnu-log.net>
20 -------------------------------------------------------------------------------
22 --------------------------------------------------------------------------------
30 configurable circular buffer mapped in user space that can be used to either
35 By using a shared buffer between the kernel and the user also has the benefit
46 --------------------------------------------------------------------------------
48 --------------------------------------------------------------------------------
[all …]
|
| /linux-3.3/drivers/media/video/uvc/ |
| D | uvc_driver.c | 2 * uvc_driver.c -- USB Video Class driver
4 * Copyright (C) 2005-2010
20 * software. If your user-space application doesn't support YUYV or MJPEG, fix
21 * it :-). Please note that the MJPEG data have been stripped from their
38 #include <media/v4l2-common.h>
48 static unsigned int uvc_quirks_param = -1;
52 /* ------------------------------------------------------------------------
98 .name = "Greyscale (8-bit)",
103 .name = "Greyscale (16-bit)",
124 /* ------------------------------------------------------------------------
[all …]
|
| D | uvc_video.c | 2 * uvc_video.c -- USB Video Class driver - Video handling
4 * Copyright (C) 2005-2010
25 #include <media/v4l2-common.h>
29 /* ------------------------------------------------------------------------
40 pipe = (query & 0x80) ? usb_rcvctrlpipe(dev->udev, 0) in __uvc_query_ctrl()
41 : usb_sndctrlpipe(dev->udev, 0); in __uvc_query_ctrl()
44 return usb_control_msg(dev->udev, pipe, query, type, cs << 8, in __uvc_query_ctrl()
83 return -EIO; in uvc_query_ctrl()
93 struct uvc_frame *frame = NULL; in uvc_fixup_video_ctrl() local
96 for (i = 0; i < stream->nformats; ++i) { in uvc_fixup_video_ctrl()
[all …]
|
| /linux-3.3/drivers/tty/ |
| D | n_hdlc.c | 17 * tty device drivers that support bit-synchronous HDLC communications.
19 * All HDLC data is frame oriented which means:
21 * 1. tty write calls represent one complete transmit frame of data
22 * The device driver should accept the complete frame or none of
23 * the frame (busy) in the write method. Each write call should have
24 * a byte count in the range of 2-65535 bytes (2 is min HDLC frame
27 * CCITT CRC32, 4 crc bytes are required, so the maximum size frame
29 * CRC16, the maximum application frame size would be 65533.
33 * one received frame. The device driver should bypass
34 * the tty flip buffer and call the line discipline receive
[all …]
|
| /linux-3.3/Documentation/DocBook/media/v4l/ |
| D | io.xml | 14 &VIDIOC-REQBUFS; ioctl. The asynchronous I/O method is not defined
19 selected by initiating video overlay with the &VIDIOC-S-FMT; ioctl.
44 the <structfield>capabilities</structfield> field of &v4l2-capability;
45 returned by the &VIDIOC-QUERYCAP; ioctl is set.</para>
49 necessarily less efficient than other methods merely exchanging buffer
50 pointers. It is considered inferior though because no meta-information
51 like frame counters or timestamps are passed. This information is
52 necessary to recognize frame dropping and to synchronize with other
60 > vidctrl /dev/video --input=0 --format=YUYV --size=352x288
66 &func-read; function, to write the &func-write; function.
[all …]
|
| D | func-read.xml | 1 <refentry id="func-read">
8 <refname>v4l2-read</refname>
54 <parameter>fd</parameter> into the buffer starting at
55 <parameter>buf</parameter>. The layout of the data in the buffer is
61 <function>read()</function> call will provide at most one frame (two
66 given to the &func-open; function it
68 &func-select; or &func-poll; functions
79 buffer being filled. Using a single buffer the driver will stop
80 capturing when the application starts reading the buffer until the
83 the nominal frame rate of the video standard.</para>
[all …]
|
| D | dev-overlay.xml | 4 <para>Video overlay devices have the ability to genlock (TV-)video
5 into the (VGA-)video signal of a graphics card, or to store captured
16 calling the &VIDIOC-S-FMT; ioctl.</para>
20 the nominal frame rate of the video standard is not guaranteed. Frames
42 each logical stream. Hence as a complexity trade-off drivers
52 <structfield>capabilities</structfield> field of &v4l2-capability;
53 returned by the &VIDIOC-QUERYCAP; ioctl. The overlay I/O method specified
64 linkend="streaming-par">streaming parameter</link> ioctls as needed.
74 driver with frame buffer parameters, namely the address and size of
75 the frame buffer and the image format, for example RGB 5:6:5. The
[all …]
|
| /linux-3.3/drivers/net/ethernet/i825xx/ |
| D | ni52.h | 7 * copyrights (c) 1994 by Michael Hipp (hippm@informatik.uni-tuebingen.de)
10 * crynwr-packet-driver by Russ Nelson
11 * Garret A. Wollman's i82586-driver for BSD
17 #define NI52_TENA 3 /* 2-5 possibly wrong, Xmit enable */
24 #define NI52_MAGICVAL1 0x00 /* magic-values for ni5210 card */
44 u32 iscp; /* pointer to the iscp-block */
56 u32 scb_base; /* base-address of all 16-bit offsets */
69 u16 rfa_offset; /* pointeroffset, receive frame area */
70 u16 crc_errs; /* CRC-Error counter */
80 #define RUC_NOP 0x0000 /* NOP-command */
[all …]
|
| D | sun3_82586.h | 7 * copyrights (c) 1994 by Michael Hipp (hippm@informatik.uni-tuebingen.de)
10 * crynwr-packet-driver by Russ Nelson
11 * Garret A. Wollman's i82586-driver for BSD
52 char *iscp; /* pointer to the iscp-block */
64 char *scb_base; /* base-address of all 16-bit offsets */
77 unsigned short rfa_offset; /* pointeroffset, receive frame area */
78 unsigned short crc_errs; /* CRC-Error counter */
88 #define RUC_NOP 0x0000 /* NOP-command */
95 #define CUC_NOP 0x00 /* NOP-command */
112 #define STAT_FR 0x40 /* RU finished receiving a frame */
[all …]
|
| /linux-3.3/drivers/media/video/zoran/ |
| D | zoran.h | 2 * zoran - Iomega Buz driver
12 * bttv - Bt848 frame grabber driver
13 * Copyright (C) 1996,97,98 Ralph Metzler (rjkm@thp.uni-koeln.de)
14 * & Marcus Metzler (mocm@thp.uni-koeln.de)
34 #include <media/v4l2-device.h>
37 unsigned long frame; /* number of buffer that has been free'd */ member
38 unsigned long length; /* number of code bytes in buffer (capture only) */
39 unsigned long seq; /* frame sequence number */
46 #define ZR_DEVNAME(zr) ((zr)->name)
48 #define BUZ_MAX_WIDTH (zr->timing->Wa)
[all …]
|
| /linux-3.3/drivers/net/wireless/prism54/ |
| D | islpci_mgt.c | 16 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
49 display_buffer(char *buffer, int length) in display_buffer() argument
55 printk("[%02x]", *buffer & 255); in display_buffer()
56 length--; in display_buffer()
57 buffer++; in display_buffer()
69 * Helper function to create a PIMFOR management frame header.
74 h->version = PIMFOR_VERSION; in pimfor_encode_header()
75 h->operation = operation; in pimfor_encode_header()
76 h->device_id = PIMFOR_DEV_ID_MHLI_MIB; in pimfor_encode_header()
77 h->flags = 0; in pimfor_encode_header()
[all …]
|
| /linux-3.3/drivers/video/omap/ |
| D | Kconfig | 2 tristate "OMAP frame buffer support (EXPERIMENTAL)"
10 Frame buffer driver for OMAP based boards.
37 Say Y here, if your user-space applications are capable of
38 notifying the frame buffer driver when a change has occurred in
39 the frame buffer content and thus a reload of the image data to
40 the external frame buffer is required. If unsure, say N.
43 bool "MIPI DBI-C/DCS compatible LCD support"
47 the Mobile Industry Processor Interface DBI-C/DCS
|
| /linux-3.3/drivers/staging/line6/ |
| D | pcm.h | 2 * Line6 Linux USB driver - 0.9.1beta
4 * Copyright (C) 2004-2010 Markus Grabner (grabner@icg.tugraz.at)
31 with only one frame per packet.
46 (line6pcm->pcm->streams[stream].substream)
68 /* *INDENT-OFF* */
79 /* *INDENT-ON* */
135 Temporary buffer for playback.
136 Since the packet size is not known in advance, this buffer is
142 Temporary buffer for capture.
143 Since the packet size is not known in advance, this buffer is
[all …]
|
| /linux-3.3/drivers/scsi/ |
| D | osst.c | 16 Copyright 1992 - 2002 Kai Makisara / 2000 - 2006 Willem Riede
21 Microscopic alterations - Rik Ling, 2000/12/21
23 Some small formal changes - aeb, 950809
32 …D_POLL(x,d) ((x) >= OSST_FW_NEED_POLL_MIN && (x) <= OSST_FW_NEED_POLL_MAX && d->host->this_id != 7)
60 is defined and non-zero. */
90 MODULE_DESCRIPTION("OnStream {DI-|FW-|SC-|USB}{30|50} Tape Driver");
118 /* The buffer size should fit into the 24 bits for length in the
119 6-byte SCSI read and write commands. */
120 #if OSST_BUFFER_SIZE >= (2 << 24 - 1)
121 #error "Buffer size should not exceed (2 << 24 - 1) bytes!"
[all …]
|
| /linux-3.3/net/irda/ |
| D | wrapper.c | 14 * Copyright (c) 1998-2000 Dag Brattli <dagb@cs.uit.no>,
16 * Copyright (c) 2000-2002 Jean Tourrilhes <jt@hpl.hp.com>
25 * provided "AS-IS" and at no charge.
41 /************************** FRAME WRAPPING **************************/
52 * Byte stuff one single byte and put the result in buffer pointed to by
53 * buf. The buffer must at all times be able to have two bytes inserted.
56 * (2000 bytes on P6 200MHz, non-inlined ~370us, inline ~170us) - Jean II
70 /* Non-special value, no transparency required */ in stuff_byte()
80 * Makes a new buffer with wrapping and stuffing, should check that
81 * we don't get tx buffer overflow.
[all …]
|
| /linux-3.3/drivers/net/wireless/iwlwifi/ |
| D | iwl-fh.h | 8 * Copyright(c) 2005 - 2011 Intel Corporation. All rights reserved.
29 * Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497
33 * Copyright(c) 2005 - 2011 Intel Corporation. All rights reserved.
80 * Keep-Warm (KW) buffer base address.
82 * Driver must allocate a 4KByte buffer that is for keeping the
83 * host DRAM powered on (via dummy accesses to DRAM) to maintain low-latency
85 * from going into a power-savings mode that would cause higher DRAM latency,
86 * and possible data over/under-runs, before all Tx/Rx is complete.
89 * of the buffer, which must be 4K aligned. Once this is set up, the device
90 * automatically invokes keep-warm accesses when normal accesses might not
[all …]
|