path: root/Documentation/power/basic-pm-debugging.txt
diff options
authorLubomir Rintel <lkundrak@v3.sk>2013-12-22 11:31:41 +0100
committerStefan Richter <stefanr@s5r6.in-berlin.de>2014-01-12 18:54:38 +0100
commita9954ce769e2c8b450b00ab2a4e208f447996b2d (patch)
tree6305ff7464f03effbc8b3b1b2568b4cad4990aee /Documentation/power/basic-pm-debugging.txt
parent7e22e91102c6b9df7c4ae2168910e19d2bb14cd6 (diff)
Documentation/: update FireWire debugging documentation
The old firewire stack is long dead now and a new version firescope has been released with support for current kernels. Signed-off-by: Lubomir Rintel <lkundrak@v3.sk> Cc: Rob Landley <rob@landley.net> Cc: Justin P. Mattock <justinmattock@gmail.com> Cc: Bernhard Kaindl <bk@suse.de> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Diffstat (limited to 'Documentation/power/basic-pm-debugging.txt')
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/power/basic-pm-debugging.txt b/Documentation/power/basic-pm-debugging.txt
index e9b54de8fdf7..edeecd447d23 100644
--- a/Documentation/power/basic-pm-debugging.txt
+++ b/Documentation/power/basic-pm-debugging.txt
@@ -172,7 +172,7 @@ you can boot the kernel with the 'no_console_suspend' parameter and try to log
kernel messages using the serial console. This may provide you with some
information about the reasons of the suspend (resume) failure. Alternatively,
it may be possible to use a FireWire port for debugging with firescope
-(ftp://ftp.firstfloor.org/pub/ak/firescope/). On x86 it is also possible to
+(http://v3.sk/~lkundrak/firescope/). On x86 it is also possible to
use the PM_TRACE mechanism documented in Documentation/power/s2ram.txt .
2. Testing suspend to RAM (STR)