diff options
Diffstat (limited to 'Documentation/networking')
-rw-r--r-- | Documentation/networking/driver.txt | 5 | ||||
-rw-r--r-- | Documentation/networking/iphase.txt | 2 | ||||
-rw-r--r-- | Documentation/networking/irda.txt | 8 | ||||
-rw-r--r-- | Documentation/networking/ray_cs.txt | 3 | ||||
-rw-r--r-- | Documentation/networking/vortex.txt | 28 |
5 files changed, 19 insertions, 27 deletions
diff --git a/Documentation/networking/driver.txt b/Documentation/networking/driver.txt index 11fd0ef5ff57..a9ad58b49cc5 100644 --- a/Documentation/networking/driver.txt +++ b/Documentation/networking/driver.txt | |||
@@ -1,7 +1,4 @@ | |||
1 | Documents about softnet driver issues in general can be found | 1 | Document about softnet driver issues |
2 | at: | ||
3 | |||
4 | http://www.firstfloor.org/~andi/softnet/ | ||
5 | 2 | ||
6 | Transmit path guidelines: | 3 | Transmit path guidelines: |
7 | 4 | ||
diff --git a/Documentation/networking/iphase.txt b/Documentation/networking/iphase.txt index 39ccb8595bf1..493203a080a8 100644 --- a/Documentation/networking/iphase.txt +++ b/Documentation/networking/iphase.txt | |||
@@ -22,7 +22,7 @@ The features and limitations of this driver are as follows: | |||
22 | - All variants of Interphase ATM PCI (i)Chip adapter cards are supported, | 22 | - All variants of Interphase ATM PCI (i)Chip adapter cards are supported, |
23 | including x575 (OC3, control memory 128K , 512K and packet memory 128K, | 23 | including x575 (OC3, control memory 128K , 512K and packet memory 128K, |
24 | 512K and 1M), x525 (UTP25) and x531 (DS3 and E3). See | 24 | 512K and 1M), x525 (UTP25) and x531 (DS3 and E3). See |
25 | http://www.iphase.com/products/ClassSheet.cfm?ClassID=ATM | 25 | http://www.iphase.com/site/iphase-web/?epi_menuItemID=e196f04b4b3b40502f150882e21046a0 |
26 | for details. | 26 | for details. |
27 | - Only x86 platforms are supported. | 27 | - Only x86 platforms are supported. |
28 | - SMP is supported. | 28 | - SMP is supported. |
diff --git a/Documentation/networking/irda.txt b/Documentation/networking/irda.txt index 9e5b8e66d6a5..bff26c138be6 100644 --- a/Documentation/networking/irda.txt +++ b/Documentation/networking/irda.txt | |||
@@ -3,12 +3,8 @@ of the IrDA Utilities. More detailed information about these and associated | |||
3 | programs can be found on http://irda.sourceforge.net/ | 3 | programs can be found on http://irda.sourceforge.net/ |
4 | 4 | ||
5 | For more information about how to use the IrDA protocol stack, see the | 5 | For more information about how to use the IrDA protocol stack, see the |
6 | Linux Infared HOWTO (http://www.tuxmobil.org/Infrared-HOWTO/Infrared-HOWTO.html) | 6 | Linux Infrared HOWTO by Werner Heuser <wehe@tuxmobil.org>: |
7 | by Werner Heuser <wehe@tuxmobil.org> | 7 | <http://www.tuxmobil.org/Infrared-HOWTO/Infrared-HOWTO.html> |
8 | 8 | ||
9 | There is an active mailing list for discussing Linux-IrDA matters called | 9 | There is an active mailing list for discussing Linux-IrDA matters called |
10 | irda-users@lists.sourceforge.net | 10 | irda-users@lists.sourceforge.net |
11 | |||
12 | |||
13 | |||
14 | |||
diff --git a/Documentation/networking/ray_cs.txt b/Documentation/networking/ray_cs.txt index b1def00bc4a3..5427f8c7df95 100644 --- a/Documentation/networking/ray_cs.txt +++ b/Documentation/networking/ray_cs.txt | |||
@@ -29,8 +29,7 @@ with nondefault parameters, they can be edited in | |||
29 | will find them all. | 29 | will find them all. |
30 | 30 | ||
31 | Information on card services is available at: | 31 | Information on card services is available at: |
32 | ftp://hyper.stanford.edu/pub/pcmcia/doc | 32 | http://pcmcia-cs.sourceforge.net/ |
33 | http://hyper.stanford.edu/HyperNews/get/pcmcia/home.html | ||
34 | 33 | ||
35 | 34 | ||
36 | Card services user programs are still required for PCMCIA devices. | 35 | Card services user programs are still required for PCMCIA devices. |
diff --git a/Documentation/networking/vortex.txt b/Documentation/networking/vortex.txt index 80e1cb19609f..3759acf95b29 100644 --- a/Documentation/networking/vortex.txt +++ b/Documentation/networking/vortex.txt | |||
@@ -11,7 +11,7 @@ The driver was written by Donald Becker <becker@scyld.com> | |||
11 | Don is no longer the prime maintainer of this version of the driver. | 11 | Don is no longer the prime maintainer of this version of the driver. |
12 | Please report problems to one or more of: | 12 | Please report problems to one or more of: |
13 | 13 | ||
14 | Andrew Morton <andrewm@uow.edu.au> | 14 | Andrew Morton <akpm@osdl.org> |
15 | Netdev mailing list <netdev@vger.kernel.org> | 15 | Netdev mailing list <netdev@vger.kernel.org> |
16 | Linux kernel mailing list <linux-kernel@vger.kernel.org> | 16 | Linux kernel mailing list <linux-kernel@vger.kernel.org> |
17 | 17 | ||
@@ -274,24 +274,24 @@ Details of the device driver implementation are at the top of the source file. | |||
274 | 274 | ||
275 | Additional documentation is available at Don Becker's Linux Drivers site: | 275 | Additional documentation is available at Don Becker's Linux Drivers site: |
276 | 276 | ||
277 | http://www.scyld.com/network/vortex.html | 277 | http://www.scyld.com/vortex.html |
278 | 278 | ||
279 | Donald Becker's driver development site: | 279 | Donald Becker's driver development site: |
280 | 280 | ||
281 | http://www.scyld.com/network | 281 | http://www.scyld.com/network.html |
282 | 282 | ||
283 | Donald's vortex-diag program is useful for inspecting the NIC's state: | 283 | Donald's vortex-diag program is useful for inspecting the NIC's state: |
284 | 284 | ||
285 | http://www.scyld.com/diag/#pci-diags | 285 | http://www.scyld.com/ethercard_diag.html |
286 | 286 | ||
287 | Donald's mii-diag program may be used for inspecting and manipulating | 287 | Donald's mii-diag program may be used for inspecting and manipulating |
288 | the NIC's Media Independent Interface subsystem: | 288 | the NIC's Media Independent Interface subsystem: |
289 | 289 | ||
290 | http://www.scyld.com/diag/#mii-diag | 290 | http://www.scyld.com/ethercard_diag.html#mii-diag |
291 | 291 | ||
292 | Donald's wake-on-LAN page: | 292 | Donald's wake-on-LAN page: |
293 | 293 | ||
294 | http://www.scyld.com/expert/wake-on-lan.html | 294 | http://www.scyld.com/wakeonlan.html |
295 | 295 | ||
296 | 3Com's documentation for many NICs, including the ones supported by | 296 | 3Com's documentation for many NICs, including the ones supported by |
297 | this driver is available at | 297 | this driver is available at |
@@ -305,7 +305,7 @@ this driver is available at | |||
305 | Driver updates and a detailed changelog for the modifications which | 305 | Driver updates and a detailed changelog for the modifications which |
306 | were made for the 2.3/2,4 series kernel is available at | 306 | were made for the 2.3/2,4 series kernel is available at |
307 | 307 | ||
308 | http://www.uow.edu.au/~andrewm/linux/#3c59x-2.3 | 308 | http://www.zip.com.au/~akpm/linux/#3c59x-bc |
309 | 309 | ||
310 | 310 | ||
311 | Autonegotiation notes | 311 | Autonegotiation notes |
@@ -434,8 +434,8 @@ steps you should take: | |||
434 | send all logs to the maintainer. | 434 | send all logs to the maintainer. |
435 | 435 | ||
436 | 3) Download you card's diagnostic tool from Donald | 436 | 3) Download you card's diagnostic tool from Donald |
437 | Backer's website http://www.scyld.com/diag. Download | 437 | Becker's website <http://www.scyld.com/ethercard_diag.html>. |
438 | mii-diag.c as well. Build these. | 438 | Download mii-diag.c as well. Build these. |
439 | 439 | ||
440 | a) Run 'vortex-diag -aaee' and 'mii-diag -v' when the card is | 440 | a) Run 'vortex-diag -aaee' and 'mii-diag -v' when the card is |
441 | working correctly. Save the output. | 441 | working correctly. Save the output. |
@@ -443,8 +443,8 @@ steps you should take: | |||
443 | b) Run the above commands when the card is malfunctioning. Send | 443 | b) Run the above commands when the card is malfunctioning. Send |
444 | both sets of output. | 444 | both sets of output. |
445 | 445 | ||
446 | Finally, please be patient and be prepared to do some work. You may end up working on | 446 | Finally, please be patient and be prepared to do some work. You may |
447 | this problem for a week or more as the maintainer asks more questions, asks for more | 447 | end up working on this problem for a week or more as the maintainer |
448 | tests, asks for patches to be applied, etc. At the end of it all, the problem may even | 448 | asks more questions, asks for more tests, asks for patches to be |
449 | remain unresolved. | 449 | applied, etc. At the end of it all, the problem may even remain |
450 | 450 | unresolved. | |