public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] Update l2ping man page for recent changes to l2ping.
@ 2009-01-20 20:51 Nick Pelly
  2009-01-21 11:18 ` Marcel Holtmann
  0 siblings, 1 reply; 2+ messages in thread
From: Nick Pelly @ 2009-01-20 20:51 UTC (permalink / raw)
  To: linux-bluetooth; +Cc: Nick Pelly

---
 tools/l2ping.1 |   17 +++++++++++++----
 1 files changed, 13 insertions(+), 4 deletions(-)

diff --git a/tools/l2ping.1 b/tools/l2ping.1
index 8f56fb5..4d09b05 100644
--- a/tools/l2ping.1
+++ b/tools/l2ping.1
@@ -11,12 +11,11 @@ l2ping \- Send L2CAP echo request and receive answer
 .IR count \|]
 .RB [\| \-t
 .IR timeout \|]
+.RB [\| \-d
+.IR delay \|]
 .RB [\| \-f \|]
 .RB [\| \-r \|]
-.I bd_addr
-
-.SH DESCRIPTION
-.LP
+.RB [\| \-v \|]
 .I bd_addr
 
 .SH DESCRIPTION
@@ -49,6 +48,11 @@ Wait
 .I timeout
 seconds for the response.
 .TP
+.BI \-d " delay"
+Wait
+.I delay
+seconds between pings.
+.TP
 .B \-f
 Kind of flood ping. Use with care! It reduces the delay time between packets
 to 0.
@@ -56,6 +60,11 @@ to 0.
 .B \-r
 Reverse ping (gnip?). Send echo response instead of echo request.
 .TP
+.B \-v
+Verify response payload is identical to request payload. It is not required for
+remote stacks to return the request payload, but most stacks do (including
+Bluez).
+.TP
 .I bd_addr
 The Bluetooth MAC address to be pinged in dotted hex notation like
 .B 01:02:03:ab:cd:ef
-- 
1.6.0.1


^ permalink raw reply related	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-01-21 11:18 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-20 20:51 [PATCH] Update l2ping man page for recent changes to l2ping Nick Pelly
2009-01-21 11:18 ` Marcel Holtmann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox