aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/IPMI.txt2
-rw-r--r--Documentation/block/barrier.txt2
-rw-r--r--Documentation/cciss.txt2
-rw-r--r--Documentation/dell_rbu.txt2
-rw-r--r--Documentation/dvb/faq.txt2
-rw-r--r--Documentation/filesystems/befs.txt2
-rw-r--r--Documentation/filesystems/configfs/configfs.txt2
-rw-r--r--Documentation/input/atarikbd.txt2
-rw-r--r--Documentation/input/yealink.txt2
-rw-r--r--Documentation/networking/dl2k.txt2
-rw-r--r--Documentation/networking/packet_mmap.txt16
-rw-r--r--Documentation/powerpc/booting-without-of.txt12
-rw-r--r--Documentation/s390/Debugging390.txt16
-rw-r--r--Documentation/scsi/aic7xxx.txt2
-rw-r--r--Documentation/scsi/dpti.txt2
-rw-r--r--Documentation/sound/alsa/MIXART.txt2
-rw-r--r--Documentation/uml/UserModeLinux-HOWTO.txt2
-rw-r--r--Documentation/video4linux/cx2341x/fw-decoder-api.txt2
-rw-r--r--Documentation/video4linux/sn9c102.txt2
19 files changed, 38 insertions, 38 deletions
diff --git a/Documentation/IPMI.txt b/Documentation/IPMI.txt
index e5b93510e358..0e3924ecd76b 100644
--- a/Documentation/IPMI.txt
+++ b/Documentation/IPMI.txt
@@ -468,7 +468,7 @@ BMCs specified on the smb_addr line will be detected.
468Setting smb_dbg_probe to 1 will enable debugging of the probing and 468Setting smb_dbg_probe to 1 will enable debugging of the probing and
469detection process for BMCs on the SMBusses. 469detection process for BMCs on the SMBusses.
470 470
471Discovering the IPMI compilant BMC on the SMBus can cause devices 471Discovering the IPMI compliant BMC on the SMBus can cause devices
472on the I2C bus to fail. The SMBus driver writes a "Get Device ID" IPMI 472on the I2C bus to fail. The SMBus driver writes a "Get Device ID" IPMI
473message as a block write to the I2C bus and waits for a response. 473message as a block write to the I2C bus and waits for a response.
474This action can be detrimental to some I2C devices. It is highly recommended 474This action can be detrimental to some I2C devices. It is highly recommended
diff --git a/Documentation/block/barrier.txt b/Documentation/block/barrier.txt
index 03971518b222..761073eae103 100644
--- a/Documentation/block/barrier.txt
+++ b/Documentation/block/barrier.txt
@@ -25,7 +25,7 @@ of the following three ways.
25i. For devices which have queue depth greater than 1 (TCQ devices) and 25i. For devices which have queue depth greater than 1 (TCQ devices) and
26support ordered tags, block layer can just issue the barrier as an 26support ordered tags, block layer can just issue the barrier as an
27ordered request and the lower level driver, controller and drive 27ordered request and the lower level driver, controller and drive
28itself are responsible for making sure that the ordering contraint is 28itself are responsible for making sure that the ordering constraint is
29met. Most modern SCSI controllers/drives should support this. 29met. Most modern SCSI controllers/drives should support this.
30 30
31NOTE: SCSI ordered tag isn't currently used due to limitation in the 31NOTE: SCSI ordered tag isn't currently used due to limitation in the
diff --git a/Documentation/cciss.txt b/Documentation/cciss.txt
index 9c629ffa0e58..45a738b81501 100644
--- a/Documentation/cciss.txt
+++ b/Documentation/cciss.txt
@@ -152,7 +152,7 @@ side during the SCSI error recovery process, the cciss driver only
152implements the first two of these actions, aborting the command, and 152implements the first two of these actions, aborting the command, and
153resetting the device. Additionally, most tape drives will not oblige 153resetting the device. Additionally, most tape drives will not oblige
154in aborting commands, and sometimes it appears they will not even 154in aborting commands, and sometimes it appears they will not even
155obey a reset coommand, though in most circumstances they will. In 155obey a reset command, though in most circumstances they will. In
156the case that the command cannot be aborted and the device cannot be 156the case that the command cannot be aborted and the device cannot be
157reset, the device will be set offline. 157reset, the device will be set offline.
158 158
diff --git a/Documentation/dell_rbu.txt b/Documentation/dell_rbu.txt
index fb18c5dc8ab4..8c93d8813791 100644
--- a/Documentation/dell_rbu.txt
+++ b/Documentation/dell_rbu.txt
@@ -41,7 +41,7 @@ The driver supports two types of update mechanism; monolithic and packetized.
41These update mechanism depends upon the BIOS currently running on the system. 41These update mechanism depends upon the BIOS currently running on the system.
42Most of the Dell systems support a monolithic update where the BIOS image is 42Most of the Dell systems support a monolithic update where the BIOS image is
43copied to a single contiguous block of physical memory. 43copied to a single contiguous block of physical memory.
44In case of packet mechanism the single memory can be broken in smaller chuks 44In case of packet mechanism the single memory can be broken in smaller chunks
45of contiguous memory and the BIOS image is scattered in these packets. 45of contiguous memory and the BIOS image is scattered in these packets.
46 46
47By default the driver uses monolithic memory for the update type. This can be 47By default the driver uses monolithic memory for the update type. This can be
diff --git a/Documentation/dvb/faq.txt b/Documentation/dvb/faq.txt
index a42132d60dc8..0b2399e6b90d 100644
--- a/Documentation/dvb/faq.txt
+++ b/Documentation/dvb/faq.txt
@@ -138,7 +138,7 @@ Some very frequently asked questions about linuxtv-dvb
138 138
139 - v4l2-common: common functions for Video4Linux-2 drivers 139 - v4l2-common: common functions for Video4Linux-2 drivers
140 140
141 - v4l1-compat: backward compatiblity layer for Video4Linux-1 legacy 141 - v4l1-compat: backward compatibility layer for Video4Linux-1 legacy
142 applications 142 applications
143 143
144 - dvb-core: DVB core module. This provides you with the 144 - dvb-core: DVB core module. This provides you with the
diff --git a/Documentation/filesystems/befs.txt b/Documentation/filesystems/befs.txt
index 877a7b1d46ec..8b7d732bfb68 100644
--- a/Documentation/filesystems/befs.txt
+++ b/Documentation/filesystems/befs.txt
@@ -57,7 +57,7 @@ if the patching step fails (i.e. there are rejected hunks), you can try to
57figure it out yourself (it shouldn't be hard), or mail the maintainer 57figure it out yourself (it shouldn't be hard), or mail the maintainer
58(Will Dyson <will_dyson@pobox.com>) for help. 58(Will Dyson <will_dyson@pobox.com>) for help.
59 59
60step 2. Configuretion & make kernel 60step 2. Configuration & make kernel
61 61
62The linux kernel has many compile-time options. Most of them are beyond the 62The linux kernel has many compile-time options. Most of them are beyond the
63scope of this document. I suggest the Kernel-HOWTO document as a good general 63scope of this document. I suggest the Kernel-HOWTO document as a good general
diff --git a/Documentation/filesystems/configfs/configfs.txt b/Documentation/filesystems/configfs/configfs.txt
index e6e7526619bf..1a6d45930ebc 100644
--- a/Documentation/filesystems/configfs/configfs.txt
+++ b/Documentation/filesystems/configfs/configfs.txt
@@ -1,5 +1,5 @@
1 1
2configfs - Userspace-driven kernel object configuation. 2configfs - Userspace-driven kernel object configuration.
3 3
4Joel Becker <joel.becker@oracle.com> 4Joel Becker <joel.becker@oracle.com>
5 5
diff --git a/Documentation/input/atarikbd.txt b/Documentation/input/atarikbd.txt
index c16a5df2f1fa..c8f99a0a9077 100644
--- a/Documentation/input/atarikbd.txt
+++ b/Documentation/input/atarikbd.txt
@@ -522,7 +522,7 @@ controller memory. The time between data bytes must be less than 20ms.
522 0x20 ; memory access 522 0x20 ; memory access
523 { data } ; 6 data bytes starting at ADR 523 { data } ; 6 data bytes starting at ADR
524 524
525This comand permits the host to read from the ikbd controller memory. 525This command permits the host to read from the ikbd controller memory.
526 526
5279.26 CONTROLLER EXECUTE 5279.26 CONTROLLER EXECUTE
528 528
diff --git a/Documentation/input/yealink.txt b/Documentation/input/yealink.txt
index 0962c5c948be..8bf2addadb4b 100644
--- a/Documentation/input/yealink.txt
+++ b/Documentation/input/yealink.txt
@@ -93,7 +93,7 @@ Format description:
93 Format specifier 93 Format specifier
94 '8' : Generic 7 segment digit with individual addressable segments 94 '8' : Generic 7 segment digit with individual addressable segments
95 95
96 Reduced capabillity 7 segm digit, when segments are hard wired together. 96 Reduced capability 7 segm digit, when segments are hard wired together.
97 '1' : 2 segments digit only able to produce a 1. 97 '1' : 2 segments digit only able to produce a 1.
98 'e' : Most significant day of the month digit, 98 'e' : Most significant day of the month digit,
99 able to produce at least 1 2 3. 99 able to produce at least 1 2 3.
diff --git a/Documentation/networking/dl2k.txt b/Documentation/networking/dl2k.txt
index a3a3c6e08cee..10e8490fa406 100644
--- a/Documentation/networking/dl2k.txt
+++ b/Documentation/networking/dl2k.txt
@@ -222,7 +222,7 @@ rx_timeout=n - Rx DMA wait time for an interrupt.
222 reach timeout of n * 640 nano seconds. 222 reach timeout of n * 640 nano seconds.
223 Set proper rx_coalesce and rx_timeout can 223 Set proper rx_coalesce and rx_timeout can
224 reduce congestion collapse and overload which 224 reduce congestion collapse and overload which
225 has been a bottlenect for high speed network. 225 has been a bottleneck for high speed network.
226 226
227 For example, rx_coalesce=10 rx_timeout=800. 227 For example, rx_coalesce=10 rx_timeout=800.
228 that is, hardware assert only 1 interrupt 228 that is, hardware assert only 1 interrupt
diff --git a/Documentation/networking/packet_mmap.txt b/Documentation/networking/packet_mmap.txt
index 781626261e35..d1c5a4804bfc 100644
--- a/Documentation/networking/packet_mmap.txt
+++ b/Documentation/networking/packet_mmap.txt
@@ -66,7 +66,7 @@ the following process:
66 66
67[setup] socket() -------> creation of the capture socket 67[setup] socket() -------> creation of the capture socket
68 setsockopt() ---> allocation of the circular buffer (ring) 68 setsockopt() ---> allocation of the circular buffer (ring)
69 mmap() ---------> maping of the allocated buffer to the 69 mmap() ---------> mapping of the allocated buffer to the
70 user process 70 user process
71 71
72[capture] poll() ---------> to wait for incoming packets 72[capture] poll() ---------> to wait for incoming packets
@@ -93,7 +93,7 @@ The destruction of the socket and all associated resources
93is done by a simple call to close(fd). 93is done by a simple call to close(fd).
94 94
95Next I will describe PACKET_MMAP settings and it's constraints, 95Next I will describe PACKET_MMAP settings and it's constraints,
96also the maping of the circular buffer in the user process and 96also the mapping of the circular buffer in the user process and
97the use of this buffer. 97the use of this buffer.
98 98
99-------------------------------------------------------------------------------- 99--------------------------------------------------------------------------------
@@ -153,8 +153,8 @@ we will get the following buffer structure:
153 153
154A frame can be of any size with the only condition it can fit in a block. A block 154A frame can be of any size with the only condition it can fit in a block. A block
155can only hold an integer number of frames, or in other words, a frame cannot 155can only hold an integer number of frames, or in other words, a frame cannot
156be spawn accross two blocks so there are some datails you have to take into 156be spawned accross two blocks, so there are some details you have to take into
157account when choosing the frame_size. See "Maping and use of the circular 157account when choosing the frame_size. See "Mapping and use of the circular
158buffer (ring)". 158buffer (ring)".
159 159
160 160
@@ -262,7 +262,7 @@ i386 architecture:
262 <pagesize> = 4096 bytes 262 <pagesize> = 4096 bytes
263 <max-order> = 11 263 <max-order> = 11
264 264
265and a value for <frame size> of 2048 byteas. These parameters will yield 265and a value for <frame size> of 2048 bytes. These parameters will yield
266 266
267 <block number> = 131072/4 = 32768 blocks 267 <block number> = 131072/4 = 32768 blocks
268 <block size> = 4096 << 11 = 8 MiB. 268 <block size> = 4096 << 11 = 8 MiB.
@@ -311,14 +311,14 @@ the following (from include/linux/if_packet.h):
311 tp_frame_size must be a multiple of TPACKET_ALIGNMENT 311 tp_frame_size must be a multiple of TPACKET_ALIGNMENT
312 tp_frame_nr must be exactly frames_per_block*tp_block_nr 312 tp_frame_nr must be exactly frames_per_block*tp_block_nr
313 313
314Note that tp_block_size should be choosed to be a power of two or there will 314Note that tp_block_size should be chosen to be a power of two or there will
315be a waste of memory. 315be a waste of memory.
316 316
317-------------------------------------------------------------------------------- 317--------------------------------------------------------------------------------
318+ Maping and use of the circular buffer (ring) 318+ Mapping and use of the circular buffer (ring)
319-------------------------------------------------------------------------------- 319--------------------------------------------------------------------------------
320 320
321The maping of the buffer in the user process is done with the conventional 321The mapping of the buffer in the user process is done with the conventional
322mmap function. Even the circular buffer is compound of several physically 322mmap function. Even the circular buffer is compound of several physically
323discontiguous blocks of memory, they are contiguous to the user space, hence 323discontiguous blocks of memory, they are contiguous to the user space, hence
324just one call to mmap is needed: 324just one call to mmap is needed:
diff --git a/Documentation/powerpc/booting-without-of.txt b/Documentation/powerpc/booting-without-of.txt
index 5c0ba235f5a5..e80e03637a67 100644
--- a/Documentation/powerpc/booting-without-of.txt
+++ b/Documentation/powerpc/booting-without-of.txt
@@ -732,12 +732,12 @@ address which can extend beyond that limit.
732 that typically get driven by the same platform code in the 732 that typically get driven by the same platform code in the
733 kernel, you would use a different "model" property but put a 733 kernel, you would use a different "model" property but put a
734 value in "compatible". The kernel doesn't directly use that 734 value in "compatible". The kernel doesn't directly use that
735 value (see /chosen/linux,platform for how the kernel choses a 735 value (see /chosen/linux,platform for how the kernel chooses a
736 platform type) but it is generally useful. 736 platform type) but it is generally useful.
737 737
738 The root node is also generally where you add additional properties 738 The root node is also generally where you add additional properties
739 specific to your board like the serial number if any, that sort of 739 specific to your board like the serial number if any, that sort of
740 thing. it is recommended that if you add any "custom" property whose 740 thing. It is recommended that if you add any "custom" property whose
741 name may clash with standard defined ones, you prefix them with your 741 name may clash with standard defined ones, you prefix them with your
742 vendor name and a comma. 742 vendor name and a comma.
743 743
@@ -817,7 +817,7 @@ address which can extend beyond that limit.
817 your board. It's a list of addresses/sizes concatenated 817 your board. It's a list of addresses/sizes concatenated
818 together, with the number of cells of each defined by the 818 together, with the number of cells of each defined by the
819 #address-cells and #size-cells of the root node. For example, 819 #address-cells and #size-cells of the root node. For example,
820 with both of these properties beeing 2 like in the example given 820 with both of these properties being 2 like in the example given
821 earlier, a 970 based machine with 6Gb of RAM could typically 821 earlier, a 970 based machine with 6Gb of RAM could typically
822 have a "reg" property here that looks like: 822 have a "reg" property here that looks like:
823 823
@@ -970,7 +970,7 @@ device-tree in another format. The currently supported formats are:
970 - "asm": assembly language file. This is a file that can be 970 - "asm": assembly language file. This is a file that can be
971 sourced by gas to generate a device-tree "blob". That file can 971 sourced by gas to generate a device-tree "blob". That file can
972 then simply be added to your Makefile. Additionally, the 972 then simply be added to your Makefile. Additionally, the
973 assembly file exports some symbols that can be use 973 assembly file exports some symbols that can be used.
974 974
975 975
976The syntax of the dtc tool is 976The syntax of the dtc tool is
@@ -984,10 +984,10 @@ generated. Supported versions are 1,2,3 and 16. The default is
984currently version 3 but that may change in the future to version 16. 984currently version 3 but that may change in the future to version 16.
985 985
986Additionally, dtc performs various sanity checks on the tree, like the 986Additionally, dtc performs various sanity checks on the tree, like the
987uniqueness of linux,phandle properties, validity of strings, etc... 987uniqueness of linux, phandle properties, validity of strings, etc...
988 988
989The format of the .dts "source" file is "C" like, supports C and C++ 989The format of the .dts "source" file is "C" like, supports C and C++
990style commments. 990style comments.
991 991
992/ { 992/ {
993} 993}
diff --git a/Documentation/s390/Debugging390.txt b/Documentation/s390/Debugging390.txt
index 0bb4512e8a65..a6555dbfa081 100644
--- a/Documentation/s390/Debugging390.txt
+++ b/Documentation/s390/Debugging390.txt
@@ -163,7 +163,7 @@ s/390 z/Architecture
163 1 1 64 bit 163 1 1 64 bit
164 164
16532 1=31 bit addressing mode 0=24 bit addressing mode (for backward 16532 1=31 bit addressing mode 0=24 bit addressing mode (for backward
166 compatibility ), linux always runs with this bit set to 1 166 compatibility), linux always runs with this bit set to 1
167 167
16833-64 Instruction address. 16833-64 Instruction address.
169 33-63 Reserved must be 0 169 33-63 Reserved must be 0
@@ -239,7 +239,7 @@ they go to 64 Bit.
239 239
240On 390 our limitations & strengths make us slightly different. 240On 390 our limitations & strengths make us slightly different.
241For backward compatibility we are only allowed use 31 bits (2GB) 241For backward compatibility we are only allowed use 31 bits (2GB)
242of our 32 bit addresses,however, we use entirely separate address 242of our 32 bit addresses, however, we use entirely separate address
243spaces for the user & kernel. 243spaces for the user & kernel.
244 244
245This means we can support 2GB of non Extended RAM on s/390, & more 245This means we can support 2GB of non Extended RAM on s/390, & more
@@ -1311,7 +1311,7 @@ for finding out when a particular variable changes.
1311 1311
1312An alternative way of finding the STD of a currently running process 1312An alternative way of finding the STD of a currently running process
1313is to do the following, ( this method is more complex but 1313is to do the following, ( this method is more complex but
1314could be quite convient if you aren't updating the kernel much & 1314could be quite convenient if you aren't updating the kernel much &
1315so your kernel structures will stay constant for a reasonable period of 1315so your kernel structures will stay constant for a reasonable period of
1316time ). 1316time ).
1317 1317
@@ -2045,13 +2045,13 @@ what gdb does when the victim receives certain signals.
2045list: 2045list:
2046e.g. 2046e.g.
2047list lists current function source 2047list lists current function source
2048list 1,10 list first 10 lines of curret file. 2048list 1,10 list first 10 lines of current file.
2049list test.c:1,10 2049list test.c:1,10
2050 2050
2051 2051
2052directory: 2052directory:
2053Adds directories to be searched for source if gdb cannot find the source. 2053Adds directories to be searched for source if gdb cannot find the source.
2054(note it is a bit sensititive about slashes ) 2054(note it is a bit sensititive about slashes)
2055e.g. To add the root of the filesystem to the searchpath do 2055e.g. To add the root of the filesystem to the searchpath do
2056directory // 2056directory //
2057 2057
@@ -2123,9 +2123,9 @@ p/x (*(**$sp+56))&0x7fffffff
2123 2123
2124Disassembling instructions without debug info 2124Disassembling instructions without debug info
2125--------------------------------------------- 2125---------------------------------------------
2126gdb typically compains if there is a lack of debugging 2126gdb typically complains if there is a lack of debugging
2127symbols in the disassemble command with 2127symbols in the disassemble command with
2128"No function contains specified address." to get around 2128"No function contains specified address." To get around
2129this do 2129this do
2130x/<number lines to disassemble>xi <address> 2130x/<number lines to disassemble>xi <address>
2131e.g. 2131e.g.
diff --git a/Documentation/scsi/aic7xxx.txt b/Documentation/scsi/aic7xxx.txt
index 3481fcded4c2..9b894f116d95 100644
--- a/Documentation/scsi/aic7xxx.txt
+++ b/Documentation/scsi/aic7xxx.txt
@@ -160,7 +160,7 @@ The following information is available in this file:
160 160
161 6.2.34 (May 5th, 2003) 161 6.2.34 (May 5th, 2003)
162 - Fix locking regression instroduced in 6.2.29 that 162 - Fix locking regression instroduced in 6.2.29 that
163 could cuase a lock order reversal between the io_request_lock 163 could cause a lock order reversal between the io_request_lock
164 and our per-softc lock. This was only possible on RH9, 164 and our per-softc lock. This was only possible on RH9,
165 SuSE, and kernel.org 2.4.X kernels. 165 SuSE, and kernel.org 2.4.X kernels.
166 166
diff --git a/Documentation/scsi/dpti.txt b/Documentation/scsi/dpti.txt
index 6e45e70243e5..f36dc0e7c8da 100644
--- a/Documentation/scsi/dpti.txt
+++ b/Documentation/scsi/dpti.txt
@@ -48,7 +48,7 @@
48 * Implemented suggestions from Alan Cox 48 * Implemented suggestions from Alan Cox
49 * Added calculation of resid for sg layer 49 * Added calculation of resid for sg layer
50 * Better error handling 50 * Better error handling
51 * Added checking underflow condtions 51 * Added checking underflow conditions
52 * Added DATAPROTECT checking 52 * Added DATAPROTECT checking
53 * Changed error return codes 53 * Changed error return codes
54 * Fixed pointer bug in bus reset routine 54 * Fixed pointer bug in bus reset routine
diff --git a/Documentation/sound/alsa/MIXART.txt b/Documentation/sound/alsa/MIXART.txt
index 5cb970612870..0db6ca7db28a 100644
--- a/Documentation/sound/alsa/MIXART.txt
+++ b/Documentation/sound/alsa/MIXART.txt
@@ -31,7 +31,7 @@ With a miXart8AES/EBU there is in addition 1 stereo digital input
31Formats 31Formats
32------- 32-------
33U8, S16_LE, S16_BE, S24_3LE, S24_3BE, FLOAT_LE, FLOAT_BE 33U8, S16_LE, S16_BE, S24_3LE, S24_3BE, FLOAT_LE, FLOAT_BE
34Sample rates : 8000 - 48000 Hz continously 34Sample rates : 8000 - 48000 Hz continuously
35 35
36Playback 36Playback
37-------- 37--------
diff --git a/Documentation/uml/UserModeLinux-HOWTO.txt b/Documentation/uml/UserModeLinux-HOWTO.txt
index b7390000bf28..60e482bdf8fa 100644
--- a/Documentation/uml/UserModeLinux-HOWTO.txt
+++ b/Documentation/uml/UserModeLinux-HOWTO.txt
@@ -1020,7 +1020,7 @@
1020 1020
1021 Note that the IP address you assign to the host end of the tap device 1021 Note that the IP address you assign to the host end of the tap device
1022 must be different than the IP you assign to the eth device inside UML. 1022 must be different than the IP you assign to the eth device inside UML.
1023 If you are short on IPs and don't want to comsume two per UML, then 1023 If you are short on IPs and don't want to consume two per UML, then
1024 you can reuse the host's eth IP address for the host ends of the tap 1024 you can reuse the host's eth IP address for the host ends of the tap
1025 devices. Internally, the UMLs must still get unique IPs for their eth 1025 devices. Internally, the UMLs must still get unique IPs for their eth
1026 devices. You can also give the UMLs non-routable IPs (192.168.x.x or 1026 devices. You can also give the UMLs non-routable IPs (192.168.x.x or
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]
102Name CX2341X_DEC_GET_XFER_INFO 102Name CX2341X_DEC_GET_XFER_INFO
103Enum 9/0x09 103Enum 9/0x09
104Description 104Description
105 This API call may be used to detect an end of stream condtion. 105 This API call may be used to detect an end of stream condition.
106Result[0] 106Result[0]
107 Stream type 107 Stream type
108Result[1] 108Result[1]
diff --git a/Documentation/video4linux/sn9c102.txt b/Documentation/video4linux/sn9c102.txt
index 1d20895b4354..b737a865e86c 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
60development of this project, despite several requests for enough detailed 60development of this project, despite several requests for enough detailed
61specifications of the register tables, compression engine and video data format 61specifications of the register tables, compression engine and video data format
62of the above chips. Nevertheless, these informations are no longer necessary, 62of the above chips. Nevertheless, these informations are no longer necessary,
63becouse all the aspects related to these chips are known and have been 63because all the aspects related to these chips are known and have been
64described in detail in this documentation. 64described in detail in this documentation.
65 65
66The driver relies on the Video4Linux2 and USB core modules. It has been 66The driver relies on the Video4Linux2 and USB core modules. It has been