diff options
Diffstat (limited to 'Documentation/video4linux')
| -rw-r--r-- | Documentation/video4linux/README.pvrusb2 | 2 | ||||
| -rw-r--r-- | Documentation/video4linux/Zoran | 2 | ||||
| -rw-r--r-- | Documentation/video4linux/cx2341x/fw-decoder-api.txt | 2 | ||||
| -rw-r--r-- | Documentation/video4linux/cx2341x/fw-encoder-api.txt | 2 | ||||
| -rw-r--r-- | Documentation/video4linux/cx2341x/fw-osd-api.txt | 2 | ||||
| -rw-r--r-- | Documentation/video4linux/cx88/hauppauge-wintv-cx88-ir.txt | 2 | ||||
| -rw-r--r-- | Documentation/video4linux/et61x251.txt | 4 | ||||
| -rw-r--r-- | Documentation/video4linux/hauppauge-wintv-cx88-ir.txt | 2 | ||||
| -rw-r--r-- | Documentation/video4linux/meye.txt | 2 | ||||
| -rw-r--r-- | Documentation/video4linux/sn9c102.txt | 4 | ||||
| -rw-r--r-- | Documentation/video4linux/w9968cf.txt | 2 | ||||
| -rw-r--r-- | Documentation/video4linux/zr36120.txt | 4 |
12 files changed, 15 insertions, 15 deletions
diff --git a/Documentation/video4linux/README.pvrusb2 b/Documentation/video4linux/README.pvrusb2 index c73a32c34528..a4b7ae800866 100644 --- a/Documentation/video4linux/README.pvrusb2 +++ b/Documentation/video4linux/README.pvrusb2 @@ -155,7 +155,7 @@ Source file list / functional overview: pvrusb2-i2c-core.[ch] - This module provides an implementation of a kernel-friendly I2C adaptor driver, through which other external I2C client drivers (e.g. msp3400, tuner, lirc) may connect and - operate corresponding chips within the the pvrusb2 device. It is + operate corresponding chips within the pvrusb2 device. It is through here that other V4L modules can reach into this driver to operate specific pieces (and those modules are in turn driven by glue logic which is coordinated by pvrusb2-hdw, doled out by diff --git a/Documentation/video4linux/Zoran b/Documentation/video4linux/Zoran index 040a2c841ae9..deb218f77adb 100644 --- a/Documentation/video4linux/Zoran +++ b/Documentation/video4linux/Zoran @@ -144,7 +144,7 @@ tv broadcast formats all aver the world. The CCIR defines parameters needed for broadcasting the signal. The CCIR has defined different standards: A,B,D,E,F,G,D,H,I,K,K1,L,M,N,... -The CCIR says not much about about the colorsystem used !!! +The CCIR says not much about the colorsystem used !!! And talking about a colorsystem says not to much about how it is broadcast. The CCIR standards A,E,F are not used any more. diff --git a/Documentation/video4linux/cx2341x/fw-decoder-api.txt b/Documentation/video4linux/cx2341x/fw-decoder-api.txt index 9df4fb3ea0f2..78bf5f21e513 100644 --- a/Documentation/video4linux/cx2341x/fw-decoder-api.txt +++ b/Documentation/video4linux/cx2341x/fw-decoder-api.txt @@ -102,7 +102,7 @@ Param[0] Name CX2341X_DEC_GET_XFER_INFO Enum 9/0x09 Description - This API call may be used to detect an end of stream condtion. + This API call may be used to detect an end of stream condition. Result[0] Stream type Result[1] diff --git a/Documentation/video4linux/cx2341x/fw-encoder-api.txt b/Documentation/video4linux/cx2341x/fw-encoder-api.txt index 001c68644b08..15df0df57ddd 100644 --- a/Documentation/video4linux/cx2341x/fw-encoder-api.txt +++ b/Documentation/video4linux/cx2341x/fw-encoder-api.txt @@ -280,7 +280,7 @@ Param[0] Param[1] Unknown, but leaving this to 0 seems to work best. Indications are that this might have to do with USB support, although passing anything but 0 - onl breaks things. + only breaks things. ------------------------------------------------------------------------------- diff --git a/Documentation/video4linux/cx2341x/fw-osd-api.txt b/Documentation/video4linux/cx2341x/fw-osd-api.txt index da98ae30a37a..0a602f3e601b 100644 --- a/Documentation/video4linux/cx2341x/fw-osd-api.txt +++ b/Documentation/video4linux/cx2341x/fw-osd-api.txt @@ -97,7 +97,7 @@ Result[0] Result[1] top left vertical offset Result[2] - bottom right hotizontal offset + bottom right horizontal offset Result[3] bottom right vertical offset diff --git a/Documentation/video4linux/cx88/hauppauge-wintv-cx88-ir.txt b/Documentation/video4linux/cx88/hauppauge-wintv-cx88-ir.txt index 93fec32a1188..faccee68f603 100644 --- a/Documentation/video4linux/cx88/hauppauge-wintv-cx88-ir.txt +++ b/Documentation/video4linux/cx88/hauppauge-wintv-cx88-ir.txt @@ -30,7 +30,7 @@ provide for a handler) GP_SAMPLE register is at 0x35C058 Bits are then right shifted into the GP_SAMPLE register at the specified -rate; you get an interrupt when a full DWORD is recieved. +rate; you get an interrupt when a full DWORD is received. You need to recover the actual RC5 bits out of the (oversampled) IR sensor bits. (Hint: look for the 0/1and 1/0 crossings of the RC5 bi-phase data) An actual raw RC5 code will span 2-3 DWORDS, depending on the actual alignment. diff --git a/Documentation/video4linux/et61x251.txt b/Documentation/video4linux/et61x251.txt index cd584f20a997..1bdee8f85b9a 100644 --- a/Documentation/video4linux/et61x251.txt +++ b/Documentation/video4linux/et61x251.txt @@ -80,7 +80,7 @@ Some of the features of the driver are: high compression quality (see also "Notes for V4L2 application developers" paragraph); - full support for the capabilities of every possible image sensors that can - be connected to the ET61X[12]51 bridges, including, for istance, red, green, + be connected to the ET61X[12]51 bridges, including, for instance, red, green, blue and global gain adjustments and exposure control (see "Supported devices" paragraph for details); - use of default color settings for sunlight conditions; @@ -222,7 +222,7 @@ identifier - of the camera registered as "/dev/video0": [root@localhost #] echo 1 > i2c_reg [root@localhost #] cat i2c_val -Note that if the sensor registers can not be read, "cat" will fail. +Note that if the sensor registers cannot be read, "cat" will fail. To avoid race conditions, all the I/O accesses to the files are serialized. diff --git a/Documentation/video4linux/hauppauge-wintv-cx88-ir.txt b/Documentation/video4linux/hauppauge-wintv-cx88-ir.txt index 93fec32a1188..faccee68f603 100644 --- a/Documentation/video4linux/hauppauge-wintv-cx88-ir.txt +++ b/Documentation/video4linux/hauppauge-wintv-cx88-ir.txt @@ -30,7 +30,7 @@ provide for a handler) GP_SAMPLE register is at 0x35C058 Bits are then right shifted into the GP_SAMPLE register at the specified -rate; you get an interrupt when a full DWORD is recieved. +rate; you get an interrupt when a full DWORD is received. You need to recover the actual RC5 bits out of the (oversampled) IR sensor bits. (Hint: look for the 0/1and 1/0 crossings of the RC5 bi-phase data) An actual raw RC5 code will span 2-3 DWORDS, depending on the actual alignment. diff --git a/Documentation/video4linux/meye.txt b/Documentation/video4linux/meye.txt index 2137da97552f..ecb34160e61d 100644 --- a/Documentation/video4linux/meye.txt +++ b/Documentation/video4linux/meye.txt @@ -29,7 +29,7 @@ driver (PCI vendor/device is 0x136b/0xff01) The third one, present in recent (more or less last year) Picturebooks (C1M* models), is not supported. The manufacturer has given the specs -to the developers under a NDA (which allows the develoment of a GPL +to the developers under a NDA (which allows the development of a GPL driver however), but things are not moving very fast (see http://r-engine.sourceforge.net/) (PCI vendor/device is 0x10cf/0x2011). diff --git a/Documentation/video4linux/sn9c102.txt b/Documentation/video4linux/sn9c102.txt index 1d20895b4354..8cda472db36d 100644 --- a/Documentation/video4linux/sn9c102.txt +++ b/Documentation/video4linux/sn9c102.txt @@ -60,7 +60,7 @@ It's worth to note that SONiX has never collaborated with the author during the development of this project, despite several requests for enough detailed specifications of the register tables, compression engine and video data format of the above chips. Nevertheless, these informations are no longer necessary, -becouse all the aspects related to these chips are known and have been +because all the aspects related to these chips are known and have been described in detail in this documentation. The driver relies on the Video4Linux2 and USB core modules. It has been @@ -85,7 +85,7 @@ Some of the features of the driver are: high compression quality (see also "Notes for V4L2 application developers" and "Video frame formats" paragraphs); - full support for the capabilities of many of the possible image sensors that - can be connected to the SN9C10x bridges, including, for istance, red, green, + can be connected to the SN9C10x bridges, including, for instance, red, green, blue and global gain adjustments and exposure (see "Supported devices" paragraph for details); - use of default color settings for sunlight conditions; diff --git a/Documentation/video4linux/w9968cf.txt b/Documentation/video4linux/w9968cf.txt index 0d53ce774b01..e0bba8393c77 100644 --- a/Documentation/video4linux/w9968cf.txt +++ b/Documentation/video4linux/w9968cf.txt @@ -15,7 +15,7 @@ Index 5. Supported devices 6. Module dependencies 7. Module loading -8. Module paramaters +8. Module parameters 9. Contact information 10. Credits diff --git a/Documentation/video4linux/zr36120.txt b/Documentation/video4linux/zr36120.txt index ac6d92d01944..1a1c2d03a5c8 100644 --- a/Documentation/video4linux/zr36120.txt +++ b/Documentation/video4linux/zr36120.txt @@ -118,9 +118,9 @@ card is not there, please try if any other card gives some response, and mail me if you got a working tvcard addition. PS. <TVCard editors behold!) - Dont forget to set video_input to the number of inputs + Don't forget to set video_input to the number of inputs you defined in the video_mux part of the tvcard definition. - Its a common error to add a channel but not incrementing + It's a common error to add a channel but not incrementing video_input and getting angry with me/v4l/linux/linus :( You are now ready to test the framegrabber with your favorite |