All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert Huang <ashuang@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] help
Date: Sun, 10 Jul 2005 17:17:49 -0400	[thread overview]
Message-ID: <ef9938ec05071014177f92578@mail.gmail.com> (raw)
In-Reply-To: <1120982496.18553.135.camel@pegasus>

[-- Attachment #1: Type: text/plain, Size: 287 bytes --]

Hi Marcel,

I have to admit that I've had trouble reading the sdptool
documentation before.  Attached is a patch for sdptool.1 that I think
explains how to use it a little better.

-albert

> what about actually reading the manual page for sdptool.
> 
> Regards
> 
> Marcel

[-- Attachment #2: albert-sdptool-patch.txt --]
[-- Type: text/plain, Size: 1025 bytes --]

Index: sdptool.1
===================================================================
RCS file: /cvsroot/bluez/utils/tools/sdptool.1,v
retrieving revision 1.4
diff -u -r1.4 sdptool.1
--- sdptool.1	6 May 2005 16:10:26 -0000	1.4
+++ sdptool.1	10 Jul 2005 21:15:07 -0000
@@ -64,8 +64,14 @@
 local \fBsdpd\fR. 
 .SH "COMMANDS" 
 .PP 
-The following commands are available. 
-.IP "\fBsearch [--bdaddr bdaddr] [--tree] [--raw] service\fP" 10 
+The following commands are available.  In all cases \fBbdaddr\fR 
+specifies the device to search or browse.  If \fIlocal\fP is used
+for \fBbdaddr\fP, then the local \fBsdpd\fR is searched.
+.PP
+Services are identified and manipulated with a 4-byte \fBrecord_handle\fP 
+(NOT the service name).  To find a service's \fBrecord_handle\fP, look for the 
+"Service RecHandle" line in the \fBsearch\fP or \fBbrowse\fP results
+.IP "\fBsearch [--bdaddr bdaddr] [--tree] [--raw] service_name\fP" 10 
 Search for services.. 
 .IP "" 10 
 Known service names are DID, SP, DUN, LAN, FAX, OPUSH, 

  reply	other threads:[~2005-07-10 21:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-09 23:09 [Bluez-devel] help Serkan FAHRIOGLU
2005-07-10  8:01 ` Marcel Holtmann
2005-07-10 21:17   ` Albert Huang [this message]
2005-07-11 17:20     ` 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=ef9938ec05071014177f92578@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.