From: Albert Huang <ashuang@gmail.com>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] l2ping manpage
Date: Tue, 29 Nov 2005 17:02:00 -0500 [thread overview]
Message-ID: <ef9938ec0511291401p2b10092cx74cc8354cff921e@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 59 bytes --]
the attached patch updates the l2ping manpage.
-albert
[-- Attachment #1.2: Type: text/html, Size: 71 bytes --]
[-- Attachment #2: 051129-albert-l2ping.1.diff --]
[-- Type: application/octet-stream, Size: 1262 bytes --]
Index: l2ping.1
===================================================================
RCS file: /cvsroot/bluez/utils/tools/l2ping.1,v
retrieving revision 1.2
diff -u -r1.2 l2ping.1
--- l2ping.1 11 Oct 2004 10:31:33 -0000 1.2
+++ l2ping.1 29 Nov 2005 22:00:24 -0000
@@ -4,7 +4,7 @@
.SH SYNOPSIS
.B l2ping
[
-.I -S source addr
+.I -i <hciX>
] [
.I -s size
] [
@@ -23,8 +23,13 @@
given in dotted hex notation.
.SH OPTIONS
.TP
-.I -S source addr
-Select address to be used as source address for the request.
+.I -i " <hciX>"
+The command is applied to device
+.I
+hciX
+, which must be the name of an installed Bluetooth device (X = 0, 1, 2, ...)
+If not specified, the command will be sent to the first available Bluetooth
+device.
.TP
.I -s size
The
@@ -36,10 +41,10 @@
.B count
number of packets then exit.
.TP
-.I -c timeout
+.I -c \fBtimeout\fP
Wait
-.B timeout
-for the response.
+.B \fBtimeout\fP
+seconds for the response.
.TP
.I -f
Kind of flood ping. Use with care! It reduces the delay time between packets
@@ -53,4 +58,4 @@
.SH AUTHORS
Written by Maxim Krasnyansky <maxk@qualcomm.com> and Marcel Holtmann <marcel@holtmann.org>
.PP
-man page by Nils Faerber <nils@kernelconcepts.de>
+man page by Nils Faerber <nils@kernelconcepts.de>.
next reply other threads:[~2005-11-29 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 22:02 Albert Huang [this message]
2005-11-30 3:28 ` [Bluez-devel] l2ping manpage Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ef9938ec0511291401p2b10092cx74cc8354cff921e@mail.gmail.com \
--to=ashuang@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).