aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorPaul Mackerras <paulus@samba.org>2008-01-23 18:07:21 -0500
committerPaul Mackerras <paulus@samba.org>2008-01-23 18:07:21 -0500
commit9156ad48338e0306e508ead5c0d9986050744475 (patch)
tree37f3a90e38190052ecf3cdf9171dfdddd37b56fd /Documentation
parentfa28237cfcc5827553044cbd6ee52e33692b0faa (diff)
parent8f7b3d156d348b6766833cd4e272d0d19b501e64 (diff)
Merge branch 'linux-2.6'
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/kernel-parameters.txt21
-rw-r--r--Documentation/local_ops.txt23
-rw-r--r--Documentation/networking/driver.txt5
-rw-r--r--Documentation/networking/wavelan.txt4
-rw-r--r--Documentation/nfsroot.txt6
-rw-r--r--Documentation/watchdog/watchdog-api.txt38
6 files changed, 44 insertions, 53 deletions
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index 2fc1fb896afc..db122df5e77d 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -527,29 +527,30 @@ and is between 256 and 4096 characters. It is defined in the file
527 Format: <area>[,<node>] 527 Format: <area>[,<node>]
528 See also Documentation/networking/decnet.txt. 528 See also Documentation/networking/decnet.txt.
529 529
530 default_blu= [VT] 530 vt.default_blu= [VT]
531 Format: <blue0>,<blue1>,<blue2>,...,<blue15> 531 Format: <blue0>,<blue1>,<blue2>,...,<blue15>
532 Change the default blue palette of the console. 532 Change the default blue palette of the console.
533 This is a 16-member array composed of values 533 This is a 16-member array composed of values
534 ranging from 0-255. 534 ranging from 0-255.
535 535
536 default_grn= [VT] 536 vt.default_grn= [VT]
537 Format: <green0>,<green1>,<green2>,...,<green15> 537 Format: <green0>,<green1>,<green2>,...,<green15>
538 Change the default green palette of the console. 538 Change the default green palette of the console.
539 This is a 16-member array composed of values 539 This is a 16-member array composed of values
540 ranging from 0-255. 540 ranging from 0-255.
541 541
542 default_red= [VT] 542 vt.default_red= [VT]
543 Format: <red0>,<red1>,<red2>,...,<red15> 543 Format: <red0>,<red1>,<red2>,...,<red15>
544 Change the default red palette of the console. 544 Change the default red palette of the console.
545 This is a 16-member array composed of values 545 This is a 16-member array composed of values
546 ranging from 0-255. 546 ranging from 0-255.
547 547
548 default_utf8= [VT] 548 vt.default_utf8=
549 [VT]
549 Format=<0|1> 550 Format=<0|1>
550 Set system-wide default UTF-8 mode for all tty's. 551 Set system-wide default UTF-8 mode for all tty's.
551 Default is 0 and by setting to 1, it enables UTF-8 552 Default is 1, i.e. UTF-8 mode is enabled for all
552 mode for all newly opened or allocated terminals. 553 newly opened terminals.
553 554
554 dhash_entries= [KNL] 555 dhash_entries= [KNL]
555 Set number of hash buckets for dentry cache. 556 Set number of hash buckets for dentry cache.
@@ -883,6 +884,14 @@ and is between 256 and 4096 characters. It is defined in the file
883 lapic_timer_c2_ok [X86-32,x86-64,APIC] trust the local apic timer in 884 lapic_timer_c2_ok [X86-32,x86-64,APIC] trust the local apic timer in
884 C2 power state. 885 C2 power state.
885 886
887 libata.dma= [LIBATA] DMA control
888 libata.dma=0 Disable all PATA and SATA DMA
889 libata.dma=1 PATA and SATA Disk DMA only
890 libata.dma=2 ATAPI (CDROM) DMA only
891 libata.dma=4 Compact Flash DMA only
892 Combinations also work, so libata.dma=3 enables DMA
893 for disks and CDROMs, but not CFs.
894
886 libata.noacpi [LIBATA] Disables use of ACPI in libata suspend/resume 895 libata.noacpi [LIBATA] Disables use of ACPI in libata suspend/resume
887 when set. 896 when set.
888 Format: <int> 897 Format: <int>
diff --git a/Documentation/local_ops.txt b/Documentation/local_ops.txt
index 1a45f11e645e..4269a1105b37 100644
--- a/Documentation/local_ops.txt
+++ b/Documentation/local_ops.txt
@@ -68,29 +68,6 @@ typedef struct { atomic_long_t a; } local_t;
68 variable can be read when reading some _other_ cpu's variables. 68 variable can be read when reading some _other_ cpu's variables.
69 69
70 70
71* Rules to follow when using local atomic operations
72
73- Variables touched by local ops must be per cpu variables.
74- _Only_ the CPU owner of these variables must write to them.
75- This CPU can use local ops from any context (process, irq, softirq, nmi, ...)
76 to update its local_t variables.
77- Preemption (or interrupts) must be disabled when using local ops in
78 process context to make sure the process won't be migrated to a
79 different CPU between getting the per-cpu variable and doing the
80 actual local op.
81- When using local ops in interrupt context, no special care must be
82 taken on a mainline kernel, since they will run on the local CPU with
83 preemption already disabled. I suggest, however, to explicitly
84 disable preemption anyway to make sure it will still work correctly on
85 -rt kernels.
86- Reading the local cpu variable will provide the current copy of the
87 variable.
88- Reads of these variables can be done from any CPU, because updates to
89 "long", aligned, variables are always atomic. Since no memory
90 synchronization is done by the writer CPU, an outdated copy of the
91 variable can be read when reading some _other_ cpu's variables.
92
93
94* How to use local atomic operations 71* How to use local atomic operations
95 72
96#include <linux/percpu.h> 73#include <linux/percpu.h>
diff --git a/Documentation/networking/driver.txt b/Documentation/networking/driver.txt
index 4f7da5a2bf4f..ea72d2e66ca8 100644
--- a/Documentation/networking/driver.txt
+++ b/Documentation/networking/driver.txt
@@ -61,7 +61,10 @@ Transmit path guidelines:
612) Do not forget to update netdev->trans_start to jiffies after 612) Do not forget to update netdev->trans_start to jiffies after
62 each new tx packet is given to the hardware. 62 each new tx packet is given to the hardware.
63 63
643) Do not forget that once you return 0 from your hard_start_xmit 643) A hard_start_xmit method must not modify the shared parts of a
65 cloned SKB.
66
674) Do not forget that once you return 0 from your hard_start_xmit
65 method, it is your driver's responsibility to free up the SKB 68 method, it is your driver's responsibility to free up the SKB
66 and in some finite amount of time. 69 and in some finite amount of time.
67 70
diff --git a/Documentation/networking/wavelan.txt b/Documentation/networking/wavelan.txt
index c1acf5eb3712..afa6e521c685 100644
--- a/Documentation/networking/wavelan.txt
+++ b/Documentation/networking/wavelan.txt
@@ -12,8 +12,8 @@ and many Linux driver to support it.
12"wavelan" driver (old ISA Wavelan) 12"wavelan" driver (old ISA Wavelan)
13---------------- 13----------------
14 o Config : Network device -> Wireless LAN -> AT&T WaveLAN 14 o Config : Network device -> Wireless LAN -> AT&T WaveLAN
15 o Location : .../drivers/net/wavelan* 15 o Location : .../drivers/net/wireless/wavelan*
16 o in-line doc : .../drivers/net/wavelan.p.h 16 o in-line doc : .../drivers/net/wireless/wavelan.p.h
17 o on-line doc : 17 o on-line doc :
18 http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Wavelan.html 18 http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Wavelan.html
19 19
diff --git a/Documentation/nfsroot.txt b/Documentation/nfsroot.txt
index 9b956a969362..31b329172343 100644
--- a/Documentation/nfsroot.txt
+++ b/Documentation/nfsroot.txt
@@ -97,10 +97,6 @@ ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>
97 autoconfiguration will take place. The most common way to use this 97 autoconfiguration will take place. The most common way to use this
98 is "ip=dhcp". 98 is "ip=dhcp".
99 99
100 Note that "ip=off" is not the same thing as "ip=::::::off", because in
101 the latter autoconfiguration will take place if any of DHCP, BOOTP or RARP
102 are compiled in the kernel.
103
104 <client-ip> IP address of the client. 100 <client-ip> IP address of the client.
105 101
106 Default: Determined using autoconfiguration. 102 Default: Determined using autoconfiguration.
@@ -149,7 +145,9 @@ ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>
149 this option. 145 this option.
150 146
151 off or none: don't use autoconfiguration 147 off or none: don't use autoconfiguration
148 (do static IP assignment instead)
152 on or any: use any protocol available in the kernel 149 on or any: use any protocol available in the kernel
150 (default)
153 dhcp: use DHCP 151 dhcp: use DHCP
154 bootp: use BOOTP 152 bootp: use BOOTP
155 rarp: use RARP 153 rarp: use RARP
diff --git a/Documentation/watchdog/watchdog-api.txt b/Documentation/watchdog/watchdog-api.txt
index bb7cb1d31ec7..4cc4ba9d7150 100644
--- a/Documentation/watchdog/watchdog-api.txt
+++ b/Documentation/watchdog/watchdog-api.txt
@@ -42,23 +42,27 @@ like this source file: see Documentation/watchdog/src/watchdog-simple.c
42A more advanced driver could for example check that a HTTP server is 42A more advanced driver could for example check that a HTTP server is
43still responding before doing the write call to ping the watchdog. 43still responding before doing the write call to ping the watchdog.
44 44
45When the device is closed, the watchdog is disabled. This is not 45When the device is closed, the watchdog is disabled, unless the "Magic
46always such a good idea, since if there is a bug in the watchdog 46Close" feature is supported (see below). This is not always such a
47daemon and it crashes the system will not reboot. Because of this, 47good idea, since if there is a bug in the watchdog daemon and it
48some of the drivers support the configuration option "Disable watchdog 48crashes the system will not reboot. Because of this, some of the
49shutdown on close", CONFIG_WATCHDOG_NOWAYOUT. If it is set to Y when 49drivers support the configuration option "Disable watchdog shutdown on
50compiling the kernel, there is no way of disabling the watchdog once 50close", CONFIG_WATCHDOG_NOWAYOUT. If it is set to Y when compiling
51it has been started. So, if the watchdog daemon crashes, the system 51the kernel, there is no way of disabling the watchdog once it has been
52will reboot after the timeout has passed. Watchdog devices also usually 52started. So, if the watchdog daemon crashes, the system will reboot
53support the nowayout module parameter so that this option can be controlled 53after the timeout has passed. Watchdog devices also usually support
54at runtime. 54the nowayout module parameter so that this option can be controlled at
55 55runtime.
56Drivers will not disable the watchdog, unless a specific magic character 'V' 56
57has been sent /dev/watchdog just before closing the file. If the userspace 57Magic Close feature:
58daemon closes the file without sending this special character, the driver 58
59will assume that the daemon (and userspace in general) died, and will stop 59If a driver supports "Magic Close", the driver will not disable the
60pinging the watchdog without disabling it first. This will then cause a 60watchdog unless a specific magic character 'V' has been sent to
61reboot if the watchdog is not re-opened in sufficient time. 61/dev/watchdog just before closing the file. If the userspace daemon
62closes the file without sending this special character, the driver
63will assume that the daemon (and userspace in general) died, and will
64stop pinging the watchdog without disabling it first. This will then
65cause a reboot if the watchdog is not re-opened in sufficient time.
62 66
63The ioctl API: 67The ioctl API:
64 68