Commit 40e47125 authored by Masanari Iida's avatar Masanari Iida Committed by Jiri Kosina

Documentation: Fix multiple typo in Documentation

Signed-off-by: default avatarMasanari Iida <standby24x7@gmail.com>
Acked-by: default avatarRandy Dunlap <rdunlap@xenotime.net>
Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
parent 4e70daaf
...@@ -7,7 +7,7 @@ Date: 09-Jul-2007 ...@@ -7,7 +7,7 @@ Date: 09-Jul-2007
KernelVersion v2.6.22 KernelVersion v2.6.22
Contact: linux-wireless@vger.kernel.org Contact: linux-wireless@vger.kernel.org
Description: Current state of the transmitter. Description: Current state of the transmitter.
This file is deprecated and sheduled to be removed in 2014, This file is deprecated and scheduled to be removed in 2014,
because its not possible to express the 'soft and hard block' because its not possible to express the 'soft and hard block'
state of the rfkill driver. state of the rfkill driver.
Values: A numeric value. Values: A numeric value.
......
...@@ -6,7 +6,7 @@ Description: ...@@ -6,7 +6,7 @@ Description:
The name of the module that is in the kernel. This The name of the module that is in the kernel. This
module name will show up either if the module is built module name will show up either if the module is built
directly into the kernel, or if it is loaded as a directly into the kernel, or if it is loaded as a
dyanmic module. dynamic module.
/sys/module/MODULENAME/parameters /sys/module/MODULENAME/parameters
This directory contains individual files that are each This directory contains individual files that are each
......
...@@ -945,7 +945,7 @@ and other resources, etc. ...@@ -945,7 +945,7 @@ and other resources, etc.
<listitem> <listitem>
<para> <para>
!BSY &amp;&amp; ERR after CDB tranfer starts but before the !BSY &amp;&amp; ERR after CDB transfer starts but before the
last byte of CDB is transferred. ATA/ATAPI standard states last byte of CDB is transferred. ATA/ATAPI standard states
that &quot;The device shall not terminate the PACKET command that &quot;The device shall not terminate the PACKET command
with an error before the last byte of the command packet has with an error before the last byte of the command packet has
...@@ -1050,7 +1050,7 @@ and other resources, etc. ...@@ -1050,7 +1050,7 @@ and other resources, etc.
to complete a command. Combined with the fact that MWDMA to complete a command. Combined with the fact that MWDMA
and PIO transfer errors aren't allowed to use ICRC bit up to and PIO transfer errors aren't allowed to use ICRC bit up to
ATA/ATAPI-7, it seems to imply that ABRT bit alone could ATA/ATAPI-7, it seems to imply that ABRT bit alone could
indicate tranfer errors. indicate transfer errors.
</para> </para>
<para> <para>
However, ATA/ATAPI-8 draft revision 1f removes the part However, ATA/ATAPI-8 draft revision 1f removes the part
......
...@@ -444,7 +444,7 @@ linkend="pixfmt-rgb"><constant>V4L2_PIX_FMT_BGR24</constant></link></para></entr ...@@ -444,7 +444,7 @@ linkend="pixfmt-rgb"><constant>V4L2_PIX_FMT_BGR24</constant></link></para></entr
<entry><para><link <entry><para><link
linkend="pixfmt-rgb"><constant>V4L2_PIX_FMT_BGR32</constant></link><footnote> linkend="pixfmt-rgb"><constant>V4L2_PIX_FMT_BGR32</constant></link><footnote>
<para>Presumably all V4L RGB formats are <para>Presumably all V4L RGB formats are
little-endian, although some drivers might interpret them according to machine endianess. V4L2 defines little-endian, big-endian and red/blue little-endian, although some drivers might interpret them according to machine endianness. V4L2 defines little-endian, big-endian and red/blue
swapped variants. For details see <xref linkend="pixfmt-rgb" />.</para> swapped variants. For details see <xref linkend="pixfmt-rgb" />.</para>
</footnote></para></entry> </footnote></para></entry>
</row> </row>
...@@ -823,7 +823,7 @@ standard); 35468950&nbsp;Hz PAL and SECAM (625-line standards)</entry> ...@@ -823,7 +823,7 @@ standard); 35468950&nbsp;Hz PAL and SECAM (625-line standards)</entry>
<row> <row>
<entry>sample_format</entry> <entry>sample_format</entry>
<entry>V4L2_PIX_FMT_GREY. The last four bytes (a <entry>V4L2_PIX_FMT_GREY. The last four bytes (a
machine endianess integer) contain a frame counter.</entry> machine endianness integer) contain a frame counter.</entry>
</row> </row>
<row> <row>
<entry>start[]</entry> <entry>start[]</entry>
......
...@@ -25,7 +25,7 @@ inline (either in the code emitted directly by the compiler, or part of ...@@ -25,7 +25,7 @@ inline (either in the code emitted directly by the compiler, or part of
the implementation of a library call) when optimizing for a recent enough the implementation of a library call) when optimizing for a recent enough
processor that has the necessary native support, but only if resulting processor that has the necessary native support, but only if resulting
binaries are already to be incompatible with earlier ARM processors due to binaries are already to be incompatible with earlier ARM processors due to
useage of similar native instructions for other things. In other words usage of similar native instructions for other things. In other words
don't make binaries unable to run on earlier processors just for the sake don't make binaries unable to run on earlier processors just for the sake
of not using these kernel helpers if your compiled code is not going to of not using these kernel helpers if your compiled code is not going to
use new instructions for other purpose. use new instructions for other purpose.
......
...@@ -94,11 +94,11 @@ Throttling/Upper Limit policy ...@@ -94,11 +94,11 @@ Throttling/Upper Limit policy
Hierarchical Cgroups Hierarchical Cgroups
==================== ====================
- Currently none of the IO control policy supports hierarhical groups. But - Currently none of the IO control policy supports hierarchical groups. But
cgroup interface does allow creation of hierarhical cgroups and internally cgroup interface does allow creation of hierarchical cgroups and internally
IO policies treat them as flat hierarchy. IO policies treat them as flat hierarchy.
So this patch will allow creation of cgroup hierarhcy but at the backend So this patch will allow creation of cgroup hierarchcy but at the backend
everything will be treated as flat. So if somebody created a hierarchy like everything will be treated as flat. So if somebody created a hierarchy like
as follows. as follows.
...@@ -266,7 +266,7 @@ Proportional weight policy files ...@@ -266,7 +266,7 @@ Proportional weight policy files
- blkio.idle_time - blkio.idle_time
- Debugging aid only enabled if CONFIG_DEBUG_BLK_CGROUP=y. - Debugging aid only enabled if CONFIG_DEBUG_BLK_CGROUP=y.
This is the amount of time spent by the IO scheduler idling for a This is the amount of time spent by the IO scheduler idling for a
given cgroup in anticipation of a better request than the exising ones given cgroup in anticipation of a better request than the existing ones
from other queues/cgroups. This is in nanoseconds. If this is read from other queues/cgroups. This is in nanoseconds. If this is read
when the cgroup is in an idling state, the stat will only report the when the cgroup is in an idling state, the stat will only report the
idle_time accumulated till the last idle period and will not include idle_time accumulated till the last idle period and will not include
...@@ -283,34 +283,34 @@ Throttling/Upper limit policy files ...@@ -283,34 +283,34 @@ Throttling/Upper limit policy files
----------------------------------- -----------------------------------
- blkio.throttle.read_bps_device - blkio.throttle.read_bps_device
- Specifies upper limit on READ rate from the device. IO rate is - Specifies upper limit on READ rate from the device. IO rate is
specified in bytes per second. Rules are per deivce. Following is specified in bytes per second. Rules are per device. Following is
the format. the format.
echo "<major>:<minor> <rate_bytes_per_second>" > /cgrp/blkio.throttle.read_bps_device echo "<major>:<minor> <rate_bytes_per_second>" > /cgrp/blkio.throttle.read_bps_device
- blkio.throttle.write_bps_device - blkio.throttle.write_bps_device
- Specifies upper limit on WRITE rate to the device. IO rate is - Specifies upper limit on WRITE rate to the device. IO rate is
specified in bytes per second. Rules are per deivce. Following is specified in bytes per second. Rules are per device. Following is
the format. the format.
echo "<major>:<minor> <rate_bytes_per_second>" > /cgrp/blkio.throttle.write_bps_device echo "<major>:<minor> <rate_bytes_per_second>" > /cgrp/blkio.throttle.write_bps_device
- blkio.throttle.read_iops_device - blkio.throttle.read_iops_device
- Specifies upper limit on READ rate from the device. IO rate is - Specifies upper limit on READ rate from the device. IO rate is
specified in IO per second. Rules are per deivce. Following is specified in IO per second. Rules are per device. Following is
the format. the format.
echo "<major>:<minor> <rate_io_per_second>" > /cgrp/blkio.throttle.read_iops_device echo "<major>:<minor> <rate_io_per_second>" > /cgrp/blkio.throttle.read_iops_device
- blkio.throttle.write_iops_device - blkio.throttle.write_iops_device
- Specifies upper limit on WRITE rate to the device. IO rate is - Specifies upper limit on WRITE rate to the device. IO rate is
specified in io per second. Rules are per deivce. Following is specified in io per second. Rules are per device. Following is
the format. the format.
echo "<major>:<minor> <rate_io_per_second>" > /cgrp/blkio.throttle.write_iops_device echo "<major>:<minor> <rate_io_per_second>" > /cgrp/blkio.throttle.write_iops_device
Note: If both BW and IOPS rules are specified for a device, then IO is Note: If both BW and IOPS rules are specified for a device, then IO is
subjectd to both the constraints. subjected to both the constraints.
- blkio.throttle.io_serviced - blkio.throttle.io_serviced
- Number of IOs (bio) completed to/from the disk by the group (as - Number of IOs (bio) completed to/from the disk by the group (as
......
...@@ -28,7 +28,7 @@ The target is named "raid" and it accepts the following parameters: ...@@ -28,7 +28,7 @@ The target is named "raid" and it accepts the following parameters:
raid6_nc RAID6 N continue raid6_nc RAID6 N continue
- rotating parity N (right-to-left) with data continuation - rotating parity N (right-to-left) with data continuation
Refererence: Chapter 4 of Reference: Chapter 4 of
http://www.snia.org/sites/default/files/SNIA_DDF_Technical_Position_v2.0.pdf http://www.snia.org/sites/default/files/SNIA_DDF_Technical_Position_v2.0.pdf
<#raid_params>: The number of parameters that follow. <#raid_params>: The number of parameters that follow.
......
...@@ -3,7 +3,7 @@ Introduction ...@@ -3,7 +3,7 @@ Introduction
The more-sophisticated device-mapper targets require complex metadata The more-sophisticated device-mapper targets require complex metadata
that is managed in kernel. In late 2010 we were seeing that various that is managed in kernel. In late 2010 we were seeing that various
different targets were rolling their own data strutures, for example: different targets were rolling their own data structures, for example:
- Mikulas Patocka's multisnap implementation - Mikulas Patocka's multisnap implementation
- Heinz Mauelshagen's thin provisioning target - Heinz Mauelshagen's thin provisioning target
......
...@@ -5,7 +5,7 @@ IPs present in the SoC. ...@@ -5,7 +5,7 @@ IPs present in the SoC.
On top of that an omap_device is created to extend the platform_device On top of that an omap_device is created to extend the platform_device
capabilities and to allow binding with one or several hwmods. capabilities and to allow binding with one or several hwmods.
The hwmods will contain all the information to build the device: The hwmods will contain all the information to build the device:
adresse range, irq lines, dma lines, interconnect, PRCM register, address range, irq lines, dma lines, interconnect, PRCM register,
clock domain, input clocks. clock domain, input clocks.
For the moment just point to the existing hwmod, the next step will be For the moment just point to the existing hwmod, the next step will be
to move data from hwmod to device-tree representation. to move data from hwmod to device-tree representation.
......
prima2 "cb" evalutation board prima2 "cb" evaluation board
Required root node properties: Required root node properties:
- compatible = "sirf,prima2-cb", "sirf,prima2"; - compatible = "sirf,prima2-cb", "sirf,prima2";
...@@ -169,7 +169,7 @@ it with special cases. ...@@ -169,7 +169,7 @@ it with special cases.
b) Entry with a flattened device-tree block. Firmware loads the b) Entry with a flattened device-tree block. Firmware loads the
physical address of the flattened device tree block (dtb) into r2, physical address of the flattened device tree block (dtb) into r2,
r1 is not used, but it is considered good practise to use a valid r1 is not used, but it is considered good practice to use a valid
machine number as described in Documentation/arm/Booting. machine number as described in Documentation/arm/Booting.
r0 : 0 r0 : 0
......
...@@ -63,7 +63,7 @@ The slave DMA usage consists of following steps: ...@@ -63,7 +63,7 @@ The slave DMA usage consists of following steps:
struct dma_slave_config *config) struct dma_slave_config *config)
Please see the dma_slave_config structure definition in dmaengine.h Please see the dma_slave_config structure definition in dmaengine.h
for a detailed explaination of the struct members. Please note for a detailed explanation of the struct members. Please note
that the 'direction' member will be going away as it duplicates the that the 'direction' member will be going away as it duplicates the
direction given in the prepare call. direction given in the prepare call.
......
...@@ -177,8 +177,8 @@ sgram - tells to driver that you have Gxx0 with SGRAM memory. It has no ...@@ -177,8 +177,8 @@ sgram - tells to driver that you have Gxx0 with SGRAM memory. It has no
effect without `init'. effect without `init'.
sdram - tells to driver that you have Gxx0 with SDRAM memory. sdram - tells to driver that you have Gxx0 with SDRAM memory.
It is a default. It is a default.
inv24 - change timings parameters for 24bpp modes on Millenium and inv24 - change timings parameters for 24bpp modes on Millennium and
Millenium II. Specify this if you see strange color shadows around Millennium II. Specify this if you see strange color shadows around
characters. characters.
noinv24 - use standard timings. It is the default. noinv24 - use standard timings. It is the default.
inverse - invert colors on screen (for LCD displays) inverse - invert colors on screen (for LCD displays)
...@@ -204,9 +204,9 @@ grayscale - enable grayscale summing. It works in PSEUDOCOLOR modes (text, ...@@ -204,9 +204,9 @@ grayscale - enable grayscale summing. It works in PSEUDOCOLOR modes (text,
can paint colors. can paint colors.
nograyscale - disable grayscale summing. It is default. nograyscale - disable grayscale summing. It is default.
cross4MB - enables that pixel line can cross 4MB boundary. It is default for cross4MB - enables that pixel line can cross 4MB boundary. It is default for
non-Millenium. non-Millennium.
nocross4MB - pixel line must not cross 4MB boundary. It is default for nocross4MB - pixel line must not cross 4MB boundary. It is default for
Millenium I or II, because of these devices have hardware Millennium I or II, because of these devices have hardware
limitations which do not allow this. But this option is limitations which do not allow this. But this option is
incompatible with some (if not all yet released) versions of incompatible with some (if not all yet released) versions of
XF86_FBDev. XF86_FBDev.
......
...@@ -308,7 +308,7 @@ min_batch_time=usec This parameter sets the commit time (as ...@@ -308,7 +308,7 @@ min_batch_time=usec This parameter sets the commit time (as
fast disks, at the cost of increasing latency. fast disks, at the cost of increasing latency.
journal_ioprio=prio The I/O priority (from 0 to 7, where 0 is the journal_ioprio=prio The I/O priority (from 0 to 7, where 0 is the
highest priorty) which should be used for I/O highest priority) which should be used for I/O
operations submitted by kjournald2 during a operations submitted by kjournald2 during a
commit operation. This defaults to 3, which is commit operation. This defaults to 3, which is
a slightly higher priority than the default I/O a slightly higher priority than the default I/O
...@@ -343,7 +343,7 @@ noinit_itable Do not initialize any uninitialized inode table ...@@ -343,7 +343,7 @@ noinit_itable Do not initialize any uninitialized inode table
init_itable=n The lazy itable init code will wait n times the init_itable=n The lazy itable init code will wait n times the
number of milliseconds it took to zero out the number of milliseconds it took to zero out the
previous block group's inode table. This previous block group's inode table. This
minimizes the impact on the systme performance minimizes the impact on the system performance
while file system's inode table is being initialized. while file system's inode table is being initialized.
discard Controls whether ext4 should issue discard/TRIM discard Controls whether ext4 should issue discard/TRIM
......
...@@ -62,7 +62,7 @@ be fixed. ...@@ -62,7 +62,7 @@ be fixed.
The REMOVE uevent is generated at the end of an unsuccessful mount The REMOVE uevent is generated at the end of an unsuccessful mount
or at the end of a umount of the filesystem. All REMOVE uevents will or at the end of a umount of the filesystem. All REMOVE uevents will
have been preceded by at least an ADD uevent for the same fileystem, have been preceded by at least an ADD uevent for the same filesystem,
and unlike the other uevents is generated automatically by the kernel's and unlike the other uevents is generated automatically by the kernel's
kobject subsystem. kobject subsystem.
......
...@@ -20,7 +20,7 @@ Commands can be embedded into transaction command (which in turn has own command ...@@ -20,7 +20,7 @@ Commands can be embedded into transaction command (which in turn has own command
so one can extend protocol as needed without breaking backward compatibility as long so one can extend protocol as needed without breaking backward compatibility as long
as old commands are supported. All string lengths include tail 0 byte. as old commands are supported. All string lengths include tail 0 byte.
All commands are transferred over the network in big-endian. CPU endianess is used at the end peers. All commands are transferred over the network in big-endian. CPU endianness is used at the end peers.
@cmd - command number, which specifies command to be processed. Following @cmd - command number, which specifies command to be processed. Following
commands are used currently: commands are used currently:
......
...@@ -993,7 +993,7 @@ struct dentry_operations { ...@@ -993,7 +993,7 @@ struct dentry_operations {
If the 'rcu_walk' parameter is true, then the caller is doing a If the 'rcu_walk' parameter is true, then the caller is doing a
pathwalk in RCU-walk mode. Sleeping is not permitted in this mode, pathwalk in RCU-walk mode. Sleeping is not permitted in this mode,
and the caller can be asked to leave it and call again by returing and the caller can be asked to leave it and call again by returning
-ECHILD. -ECHILD.
This function is only used if DCACHE_MANAGE_TRANSIT is set on the This function is only used if DCACHE_MANAGE_TRANSIT is set on the
......
...@@ -53,7 +53,7 @@ attributes are write-only, all other attributes are read-only. ...@@ -53,7 +53,7 @@ attributes are write-only, all other attributes are read-only.
in1_label "vin1" or "vout1" depending on chip variant and in1_label "vin1" or "vout1" depending on chip variant and
configuration. configuration.
in1_input Measured voltage. in1_input Measured voltage.
in1_min Minumum Voltage. in1_min Minimum Voltage.
in1_max Maximum voltage. in1_max Maximum voltage.
in1_min_alarm Voltage low alarm. in1_min_alarm Voltage low alarm.
in1_max_alarm Voltage high alarm. in1_max_alarm Voltage high alarm.
......
...@@ -42,9 +42,9 @@ attributes are read-only. ...@@ -42,9 +42,9 @@ attributes are read-only.
in[1-4]_label "vout[1-4]" in[1-4]_label "vout[1-4]"
in[1-4]_input Measured voltage. From READ_VOUT register. in[1-4]_input Measured voltage. From READ_VOUT register.
in[1-4]_min Minumum Voltage. From VOUT_UV_WARN_LIMIT register. in[1-4]_min Minimum Voltage. From VOUT_UV_WARN_LIMIT register.
in[1-4]_max Maximum voltage. From VOUT_OV_WARN_LIMIT register. in[1-4]_max Maximum voltage. From VOUT_OV_WARN_LIMIT register.
in[1-4]_lcrit Critical minumum Voltage. VOUT_UV_FAULT_LIMIT register. in[1-4]_lcrit Critical minimum Voltage. VOUT_UV_FAULT_LIMIT register.
in[1-4]_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT register. in[1-4]_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT register.
in[1-4]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status. in[1-4]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
in[1-4]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status. in[1-4]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
......
...@@ -48,9 +48,9 @@ attributes are read-only. ...@@ -48,9 +48,9 @@ attributes are read-only.
in[1-6]_label "vout[1-6]". in[1-6]_label "vout[1-6]".
in[1-6]_input Measured voltage. From READ_VOUT register. in[1-6]_input Measured voltage. From READ_VOUT register.
in[1-6]_min Minumum Voltage. From VOUT_UV_WARN_LIMIT register. in[1-6]_min Minimum Voltage. From VOUT_UV_WARN_LIMIT register.
in[1-6]_max Maximum voltage. From VOUT_OV_WARN_LIMIT register. in[1-6]_max Maximum voltage. From VOUT_OV_WARN_LIMIT register.
in[1-6]_lcrit Critical minumum Voltage. VOUT_UV_FAULT_LIMIT register. in[1-6]_lcrit Critical minimum Voltage. VOUT_UV_FAULT_LIMIT register.
in[1-6]_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT register. in[1-6]_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT register.
in[1-6]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status. in[1-6]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
in[1-6]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status. in[1-6]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
......
...@@ -42,9 +42,9 @@ attributes are read-only. ...@@ -42,9 +42,9 @@ attributes are read-only.
in1_label "vout1" in1_label "vout1"
in1_input Measured voltage. From READ_VOUT register. in1_input Measured voltage. From READ_VOUT register.
in1_min Minumum Voltage. From VOUT_UV_WARN_LIMIT register. in1_min Minimum Voltage. From VOUT_UV_WARN_LIMIT register.
in1_max Maximum voltage. From VOUT_OV_WARN_LIMIT register. in1_max Maximum voltage. From VOUT_OV_WARN_LIMIT register.
in1_lcrit Critical minumum Voltage. VOUT_UV_FAULT_LIMIT register. in1_lcrit Critical minimum Voltage. VOUT_UV_FAULT_LIMIT register.
in1_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT register. in1_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT register.
in1_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status. in1_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
in1_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status. in1_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
......
...@@ -70,9 +70,9 @@ attributes are read-only. ...@@ -70,9 +70,9 @@ attributes are read-only.
in[1-12]_label "vout[1-12]". in[1-12]_label "vout[1-12]".
in[1-12]_input Measured voltage. From READ_VOUT register. in[1-12]_input Measured voltage. From READ_VOUT register.
in[1-12]_min Minumum Voltage. From VOUT_UV_WARN_LIMIT register. in[1-12]_min Minimum Voltage. From VOUT_UV_WARN_LIMIT register.
in[1-12]_max Maximum voltage. From VOUT_OV_WARN_LIMIT register. in[1-12]_max Maximum voltage. From VOUT_OV_WARN_LIMIT register.
in[1-12]_lcrit Critical minumum Voltage. VOUT_UV_FAULT_LIMIT register. in[1-12]_lcrit Critical minimum Voltage. VOUT_UV_FAULT_LIMIT register.
in[1-12]_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT register. in[1-12]_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT register.
in[1-12]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status. in[1-12]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
in[1-12]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status. in[1-12]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
...@@ -82,7 +82,7 @@ in[1-12]_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT status. ...@@ -82,7 +82,7 @@ in[1-12]_crit_alarm Voltage critical high alarm. From VOLTAGE_OV_FAULT status.
curr[1-12]_label "iout[1-12]". curr[1-12]_label "iout[1-12]".
curr[1-12]_input Measured current. From READ_IOUT register. curr[1-12]_input Measured current. From READ_IOUT register.
curr[1-12]_max Maximum current. From IOUT_OC_WARN_LIMIT register. curr[1-12]_max Maximum current. From IOUT_OC_WARN_LIMIT register.
curr[1-12]_lcrit Critical minumum output current. From IOUT_UC_FAULT_LIMIT curr[1-12]_lcrit Critical minimum output current. From IOUT_UC_FAULT_LIMIT
register. register.
curr[1-12]_crit Critical maximum current. From IOUT_OC_FAULT_LIMIT register. curr[1-12]_crit Critical maximum current. From IOUT_OC_FAULT_LIMIT register.
curr[1-12]_max_alarm Current high alarm. From IOUT_OC_WARNING status. curr[1-12]_max_alarm Current high alarm. From IOUT_OC_WARNING status.
......
...@@ -54,9 +54,9 @@ attributes are read-only. ...@@ -54,9 +54,9 @@ attributes are read-only.
in1_label "vin". in1_label "vin".
in1_input Measured voltage. From READ_VIN register. in1_input Measured voltage. From READ_VIN register.
in1_min Minumum Voltage. From VIN_UV_WARN_LIMIT register. in1_min Minimum Voltage. From VIN_UV_WARN_LIMIT register.
in1_max Maximum voltage. From VIN_OV_WARN_LIMIT register. in1_max Maximum voltage. From VIN_OV_WARN_LIMIT register.
in1_lcrit Critical minumum Voltage. VIN_UV_FAULT_LIMIT register. in1_lcrit Critical minimum Voltage. VIN_UV_FAULT_LIMIT register.
in1_crit Critical maximum voltage. From VIN_OV_FAULT_LIMIT register. in1_crit Critical maximum voltage. From VIN_OV_FAULT_LIMIT register.
in1_min_alarm Voltage low alarm. From VIN_UV_WARNING status. in1_min_alarm Voltage low alarm. From VIN_UV_WARNING status.
in1_max_alarm Voltage high alarm. From VIN_OV_WARNING status. in1_max_alarm Voltage high alarm. From VIN_OV_WARNING status.
...@@ -65,9 +65,9 @@ in1_crit_alarm Voltage critical high alarm. From VIN_OV_FAULT status. ...@@ -65,9 +65,9 @@ in1_crit_alarm Voltage critical high alarm. From VIN_OV_FAULT status.
in[2-5]_label "vout[1-4]". in[2-5]_label "vout[1-4]".
in[2-5]_input Measured voltage. From READ_VOUT register. in[2-5]_input Measured voltage. From READ_VOUT register.
in[2-5]_min Minumum Voltage. From VOUT_UV_WARN_LIMIT register. in[2-5]_min Minimum Voltage. From VOUT_UV_WARN_LIMIT register.
in[2-5]_max Maximum voltage. From VOUT_OV_WARN_LIMIT register. in[2-5]_max Maximum voltage. From VOUT_OV_WARN_LIMIT register.
in[2-5]_lcrit Critical minumum Voltage. VOUT_UV_FAULT_LIMIT register. in[2-5]_lcrit Critical minimum Voltage. VOUT_UV_FAULT_LIMIT register.
in[2-5]_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT register. in[2-5]_crit Critical maximum voltage. From VOUT_OV_FAULT_LIMIT register.
in[2-5]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status. in[2-5]_min_alarm Voltage low alarm. From VOLTAGE_UV_WARNING status.
in[2-5]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status. in[2-5]_max_alarm Voltage high alarm. From VOLTAGE_OV_WARNING status.
...@@ -80,7 +80,7 @@ curr1_input Measured current. From READ_IIN register. ...@@ -80,7 +80,7 @@ curr1_input Measured current. From READ_IIN register.
curr[2-5]_label "iout[1-4]". curr[2-5]_label "iout[1-4]".
curr[2-5]_input Measured current. From READ_IOUT register. curr[2-5]_input Measured current. From READ_IOUT register.
curr[2-5]_max Maximum current. From IOUT_OC_WARN_LIMIT register. curr[2-5]_max Maximum current. From IOUT_OC_WARN_LIMIT register.
curr[2-5]_lcrit Critical minumum output current. From IOUT_UC_FAULT_LIMIT curr[2-5]_lcrit Critical minimum output current. From IOUT_UC_FAULT_LIMIT
register. register.
curr[2-5]_crit Critical maximum current. From IOUT_OC_FAULT_LIMIT register. curr[2-5]_crit Critical maximum current. From IOUT_OC_FAULT_LIMIT register.
curr[2-5]_max_alarm Current high alarm. From IOUT_OC_WARNING status. curr[2-5]_max_alarm Current high alarm. From IOUT_OC_WARNING status.
......
...@@ -108,7 +108,7 @@ in1_label "vin" ...@@ -108,7 +108,7 @@ in1_label "vin"
in1_input Measured input voltage. in1_input Measured input voltage.
in1_min Minimum input voltage. in1_min Minimum input voltage.
in1_max Maximum input voltage. in1_max Maximum input voltage.
in1_lcrit Critical minumum input voltage. in1_lcrit Critical minimum input voltage.
in1_crit Critical maximum input voltage. in1_crit Critical maximum input voltage.
in1_min_alarm Input voltage low alarm. in1_min_alarm Input voltage low alarm.
in1_max_alarm Input voltage high alarm. in1_max_alarm Input voltage high alarm.
...@@ -117,7 +117,7 @@ in1_crit_alarm Input voltage critical high alarm. ...@@ -117,7 +117,7 @@ in1_crit_alarm Input voltage critical high alarm.
in2_label "vout1" in2_label "vout1"
in2_input Measured output voltage. in2_input Measured output voltage.
in2_lcrit Critical minumum output Voltage. in2_lcrit Critical minimum output Voltage.
in2_crit Critical maximum output voltage. in2_crit Critical maximum output voltage.
in2_lcrit_alarm Critical output voltage critical low alarm. in2_lcrit_alarm Critical output voltage critical low alarm.
in2_crit_alarm Critical output voltage critical high alarm. in2_crit_alarm Critical output voltage critical high alarm.
......
...@@ -138,7 +138,7 @@ VI. Setting Parameters ...@@ -138,7 +138,7 @@ VI. Setting Parameters
The return value is the size in bytes of the data written into The return value is the size in bytes of the data written into
ops->resbuf if no errors occur. If an error occurs, -1 is returned ops->resbuf if no errors occur. If an error occurs, -1 is returned
and errno is set appropriatly: and errno is set appropriately:
EFAULT Invalid user space pointer was passed EFAULT Invalid user space pointer was passed
ENXIO Invalid IOP number ENXIO Invalid IOP number
...@@ -222,7 +222,7 @@ VIII. Downloading Software ...@@ -222,7 +222,7 @@ VIII. Downloading Software
RETURNS RETURNS
This function returns 0 no errors occur. If an error occurs, -1 This function returns 0 no errors occur. If an error occurs, -1
is returned and errno is set appropriatly: is returned and errno is set appropriately:
EFAULT Invalid user space pointer was passed EFAULT Invalid user space pointer was passed
ENXIO Invalid IOP number ENXIO Invalid IOP number
...@@ -264,7 +264,7 @@ IX. Uploading Software ...@@ -264,7 +264,7 @@ IX. Uploading Software
RETURNS RETURNS
This function returns 0 if no errors occur. If an error occurs, -1 This function returns 0 if no errors occur. If an error occurs, -1
is returned and errno is set appropriatly: is returned and errno is set appropriately:
EFAULT Invalid user space pointer was passed EFAULT Invalid user space pointer was passed
ENXIO Invalid IOP number ENXIO Invalid IOP number
...@@ -301,7 +301,7 @@ X. Removing Software ...@@ -301,7 +301,7 @@ X. Removing Software
RETURNS RETURNS
This function returns 0 if no errors occur. If an error occurs, -1 This function returns 0 if no errors occur. If an error occurs, -1
is returned and errno is set appropriatly: is returned and errno is set appropriately:
EFAULT Invalid user space pointer was passed EFAULT Invalid user space pointer was passed
ENXIO Invalid IOP number ENXIO Invalid IOP number
...@@ -325,7 +325,7 @@ X. Validating Configuration ...@@ -325,7 +325,7 @@ X. Validating Configuration
RETURNS RETURNS
This function returns 0 if no erro occur. If an error occurs, -1 is This function returns 0 if no erro occur. If an error occurs, -1 is
returned and errno is set appropriatly: returned and errno is set appropriately:
ETIMEDOUT Timeout waiting for reply message ETIMEDOUT Timeout waiting for reply message
ENXIO Invalid IOP number ENXIO Invalid IOP number
...@@ -360,7 +360,7 @@ XI. Configuration Dialog ...@@ -360,7 +360,7 @@ XI. Configuration Dialog
RETURNS RETURNS
This function returns 0 if no error occur. If an error occurs, -1 This function returns 0 if no error occur. If an error occurs, -1
is returned and errno is set appropriatly: is returned and errno is set appropriately:
EFAULT Invalid user space pointer was passed EFAULT Invalid user space pointer was passed
ENXIO Invalid IOP number ENXIO Invalid IOP number
......
...@@ -175,7 +175,7 @@ ...@@ -175,7 +175,7 @@
* since the .pdf version doesn't seem to work... * since the .pdf version doesn't seem to work...
* -- Updated the TODO list to something more current. * -- Updated the TODO list to something more current.
* *
* 4.15 Aug 25, 1998 -- Updated ide-cd.h to respect mechine endianess, * 4.15 Aug 25, 1998 -- Updated ide-cd.h to respect machine endianness,
* patch thanks to "Eddie C. Dost" <ecd@skynet.be> * patch thanks to "Eddie C. Dost" <ecd@skynet.be>
* *
* 4.50 Oct 19, 1998 -- New maintainers! * 4.50 Oct 19, 1998 -- New maintainers!
......
...@@ -131,8 +131,8 @@ number of contacts (f1 and f0 in the table below). ...@@ -131,8 +131,8 @@ number of contacts (f1 and f0 in the table below).
byte 5: 0 1 ? ? ? ? f1 f0 byte 5: 0 1 ? ? ? ? f1 f0
This packet only appears after a position packet with the mt bit set, and This packet only appears after a position packet with the mt bit set, and
ususally only appears when there are two or more contacts (although usually only appears when there are two or more contacts (although
ocassionally it's seen with only a single contact). occassionally it's seen with only a single contact).
The final v3 packet type is the trackstick packet. The final v3 packet type is the trackstick packet.
......
...@@ -330,7 +330,7 @@ the USB documentation for how to setup an USB mouse. ...@@ -330,7 +330,7 @@ the USB documentation for how to setup an USB mouse.
The TM DirectConnect (BSP) protocol is supported by the tmdc.c The TM DirectConnect (BSP) protocol is supported by the tmdc.c
module. This includes, but is not limited to: module. This includes, but is not limited to:
* ThrustMaster Millenium 3D Inceptor * ThrustMaster Millennium 3D Interceptor
* ThrustMaster 3D Rage Pad * ThrustMaster 3D Rage Pad
* ThrustMaster Fusion Digital Game Pad * ThrustMaster Fusion Digital Game Pad
......
...@@ -596,7 +596,7 @@ HDIO_DRIVE_TASKFILE execute raw taskfile ...@@ -596,7 +596,7 @@ HDIO_DRIVE_TASKFILE execute raw taskfile
if CHS/LBA28 if CHS/LBA28
The association between in_flags.all and each enable The association between in_flags.all and each enable
bitfield flips depending on endianess; fortunately, TASKFILE bitfield flips depending on endianness; fortunately, TASKFILE
only uses inflags.b.data bit and ignores all other bits. only uses inflags.b.data bit and ignores all other bits.
The end result is that, on any endian machines, it has no The end result is that, on any endian machines, it has no
effect other than modifying in_flags on completion. effect other than modifying in_flags on completion.
...@@ -720,7 +720,7 @@ HDIO_DRIVE_TASKFILE execute raw taskfile ...@@ -720,7 +720,7 @@ HDIO_DRIVE_TASKFILE execute raw taskfile
[6] Do not access {in|out}_flags->all except for resetting [6] Do not access {in|out}_flags->all except for resetting
all the bits. Always access individual bit fields. ->all all the bits. Always access individual bit fields. ->all
value will flip depending on endianess. For the same value will flip depending on endianness. For the same
reason, do not use IDE_{TASKFILE|HOB}_STD_{OUT|IN}_FLAGS reason, do not use IDE_{TASKFILE|HOB}_STD_{OUT|IN}_FLAGS
constants defined in hdreg.h. constants defined in hdreg.h.
......
...@@ -117,7 +117,7 @@ applicable everywhere (see syntax). ...@@ -117,7 +117,7 @@ applicable everywhere (see syntax).
This attribute is only applicable to menu blocks, if the condition is This attribute is only applicable to menu blocks, if the condition is
false, the menu block is not displayed to the user (the symbols false, the menu block is not displayed to the user (the symbols
contained there can still be selected by other symbols, though). It is contained there can still be selected by other symbols, though). It is
similar to a conditional "prompt" attribude for individual menu similar to a conditional "prompt" attribute for individual menu
entries. Default value of "visible" is true. entries. Default value of "visible" is true.
- numerical ranges: "range" <symbol> <symbol> ["if" <expr>] - numerical ranges: "range" <symbol> <symbol> ["if" <expr>]
......
...@@ -44,7 +44,7 @@ the 'software updates' pages. The firmware binaries are part of ...@@ -44,7 +44,7 @@ the 'software updates' pages. The firmware binaries are part of
the various ForeThought software distributions. the various ForeThought software distributions.
Notice that different versions of the PCA-200E firmware exist, depending Notice that different versions of the PCA-200E firmware exist, depending
on the endianess of the host architecture. The driver is shipped with on the endianness of the host architecture. The driver is shipped with
both little and big endian PCA firmware images. both little and big endian PCA firmware images.
Name and location of the new firmware images can be set at kernel Name and location of the new firmware images can be set at kernel
......