aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/networking/vortex.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/networking/vortex.txt')
-rw-r--r--Documentation/networking/vortex.txt28
1 files changed, 14 insertions, 14 deletions
diff --git a/Documentation/networking/vortex.txt b/Documentation/networking/vortex.txt
index 80e1cb19609..3759acf95b2 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>
11Don is no longer the prime maintainer of this version of the driver. 11Don is no longer the prime maintainer of this version of the driver.
12Please report problems to one or more of: 12Please 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
275Additional documentation is available at Don Becker's Linux Drivers site: 275Additional 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
279Donald Becker's driver development site: 279Donald Becker's driver development site:
280 280
281 http://www.scyld.com/network 281 http://www.scyld.com/network.html
282 282
283Donald's vortex-diag program is useful for inspecting the NIC's state: 283Donald'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
287Donald's mii-diag program may be used for inspecting and manipulating 287Donald's mii-diag program may be used for inspecting and manipulating
288the NIC's Media Independent Interface subsystem: 288the 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
292Donald's wake-on-LAN page: 292Donald'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
2963Com's documentation for many NICs, including the ones supported by 2963Com's documentation for many NICs, including the ones supported by
297this driver is available at 297this driver is available at
@@ -305,7 +305,7 @@ this driver is available at
305Driver updates and a detailed changelog for the modifications which 305Driver updates and a detailed changelog for the modifications which
306were made for the 2.3/2,4 series kernel is available at 306were 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
311Autonegotiation notes 311Autonegotiation 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
446Finally, please be patient and be prepared to do some work. You may end up working on 446Finally, please be patient and be prepared to do some work. You may
447this problem for a week or more as the maintainer asks more questions, asks for more 447end up working on this problem for a week or more as the maintainer
448tests, asks for patches to be applied, etc. At the end of it all, the problem may even 448asks more questions, asks for more tests, asks for patches to be
449remain unresolved. 449applied, etc. At the end of it all, the problem may even remain
450 450unresolved.