Home
last modified time | relevance | path

Searched refs:standards (Results 1 – 25 of 39) sorted by relevance

12

/linux-2.6.39/drivers/staging/easycap/
DREADME92 The following TV standards are natively supported by the hardware and are
101 In addition, the driver offers "custom" pseudo-standards with a framerate
102 which is 20% of the usual framerate. These pseudo-standards are named:
125 The driver is designed to support all the TV standards accepted by the
/linux-2.6.39/drivers/staging/brcm80211/
DTODO16 - Use proper kernel coding standards
/linux-2.6.39/drivers/staging/wlags49_h25/
DTODO21 - verify the code against the coding standards for a proper linux
/linux-2.6.39/drivers/staging/wlags49_h2/
DTODO21 - verify the code against the coding standards for a proper linux
/linux-2.6.39/drivers/media/video/
Dv4l2-ioctl.c62 static const struct std_descr standards[] = { variable
109 for (i = 0; standards[i].std; i++) in v4l2_norm_to_name()
110 if (myid == standards[i].std) in v4l2_norm_to_name()
112 return standards[i].descr; in v4l2_norm_to_name()
1232 while ((id & standards[j].std) != standards[j].std) in __video_do_ioctl()
1234 curr_id = standards[j].std; in __video_do_ioctl()
1235 descr = standards[j].descr; in __video_do_ioctl()
/linux-2.6.39/Documentation/video4linux/
DREADME.cx8818 at least for some standards.
DZoran139 The best know TV standards are NTSC/PAL/SECAM. but for decoding a frame that
140 information is not enough. There are several formats of the TV standards.
146 The CCIR has defined different standards: A,B,D,E,F,G,D,H,I,K,K1,L,M,N,...
150 The CCIR standards A,E,F are not used any more.
176 A rather good sites about the TV standards are:
/linux-2.6.39/Documentation/
Dunicode.txt105 http://www.evertype.com/standards/csur/klingon.html
167 http://www.evertype.com/standards/csur/
DHOWTO48 high standards for coding, style and procedure. These standards have
51 possible about these standards ahead of time, as they are well
/linux-2.6.39/Documentation/sound/alsa/soc/
Doverview.txt75 DAI.txt: Description of Digital Audio Interface standards and how to configure
/linux-2.6.39/net/irda/
DKconfig11 The Infrared Data Associations (tm) specifies standards for wireless
/linux-2.6.39/drivers/staging/
DKconfig33 kernel quality standards, are a bit crufty around the edges,
/linux-2.6.39/Documentation/networking/
Dx25-iface.txt10 standards. Most X.25 device drivers will be moderately similar to the
Dl2tp.txt28 pseudowires for L2TP are defined in separate RFC standards. Another
/linux-2.6.39/Documentation/hwmon/
Dsysfs-interface1 Naming and data format standards for sysfs files
27 files directly. This document briefly describes the standards that the
158 an arbitrary number, as not all standards have a version
Dasc7621123 the standards defined in "sysfs-interface".
/linux-2.6.39/Documentation/crypto/
Dapi-intro.txt96 standards) be included.
/linux-2.6.39/Documentation/ide/
Dide.txt240 The latest standards define some enhancements, known as the ATA-6 spec,
/linux-2.6.39/Documentation/development-process/
D3.Early-stage95 the kernel community's standards. Some examples include:
D6.Followthrough15 standards. A failure to participate in this process is quite likely to
/linux-2.6.39/Documentation/cdrom/
Dcdrom-standard.tex68 and the computer was not specified in the standards. As a result, many
510 errors should be according to the standards, whatever they are. When
610 interface and software standards. Before you protest, there are two
685 \subsection{And what about standards?}
/linux-2.6.39/Documentation/block/
Ddata-integrity.txt309 it. The format is standards body-type-variant.
/linux-2.6.39/Documentation/telephony/
Dixj.txt54 today's standards is available as a binary only module to those people
/linux-2.6.39/drivers/staging/go7007/
Dgo7007.txt145 information about the local TV standards be passed to the driver in order
/linux-2.6.39/Documentation/blockdev/
Dparide.txt66 The high-level drivers function according to the relevant standards.

12