From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Problems decoding SDP in hcidump.
Date: Mon, 23 Feb 2004 19:09:34 +0000 [thread overview]
Message-ID: <403A4FEE.50909@superbug.demon.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
I attach a captured file using "hcidump -whcidump.cap".
Can anyone decode this.
hcidump -rhcidump.cap does not seem to like it.
The capture was done while running the following command: -
sdptool search --bdaddr 00:02:EE:C3:43:61 0x0100
That bdaddr is a Nokia 6310i mobile phone, so I assume that what it is
sending is valid.
Cheers
James
[-- Attachment #2: hcidump.cap --]
[-- Type: application/octet-stream, Size: 2263 bytes --]
reply other threads:[~2004-02-23 19:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=403A4FEE.50909@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--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