From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] sdptool get <service record> output incomplete?
Date: Wed, 02 Mar 2005 15:11:15 +0100 [thread overview]
Message-ID: <1109772675.8284.5.camel@pegasus> (raw)
In-Reply-To: <C70061B183DE09419568AB2060C52A9518EE80@arion.intra.local>
Hi Victor,
> Is it the case that not all the attribute records are reported by
> sdptool? Below are the outputs: first of hcidump for the request from
> the phone for services supported (cut version showing only HF part)
> and the second one of =B4spdtool get <HF service record>=A1, attribute
> 0x311 is missing from sdptool output (marked unknown, but in reality
> it is SUPPORTED_FEATURES )?
maybe this is simply unknown at the moment. Do you use the latest utils
version? What about using the --tree option?
If it is missing, send in a patch for it.
> hcidump gives:
>=20
> =20
>=20
> HCI sniffer - Bluetooth packet analyzer ver 1.18
>=20
> device: hci0 snap_len: 1028 filter: 0xffffffff
>=20
> > ACL data: handle 41 flags 0x02 dlen 17
Please stop posting HTML emails to the mailing list. The newlines got
messed up and it makes everything hard to read. Good old plain ASCII is
just enough.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-03-02 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 8:40 [Bluez-devel] sdptool get <service record> output incomplete? Victor Shcherbatyuk
2005-03-02 14:11 ` Marcel Holtmann [this message]
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=1109772675.8284.5.camel@pegasus \
--to=marcel@holtmann.org \
--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