From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] device doesn't support
Date: Thu, 15 Nov 2007 18:58:31 +0100 [thread overview]
Message-ID: <1195149511.5175.118.camel@aeonflux> (raw)
In-Reply-To: <473BFAD7.6090107@omepet.es>
Hi,
> I want to know if my dongle supports the HCI_Write_Page_Timeout command,
> so I do:
>
> #hcitool -i hci0 cmd 0x04 0x0003 (informational commands, read supported
> commands)
>
> and I get:
>
> < HCI Command: ogf 0x04, ocf 0x0003, plen 0
> > HCI Event: 0x0e plen 12
> 01 03 10 00 FF FF 8F FE 9B F9 00 80
> ^
> According to this results, the dongle supports HCI_Write_Page_Timeout,
> but I am getting 12 octets instead of 16 (BT spec.), Why?
>
> Am I doing something wrong? Something related to bit-byte ordering?
> Is the information returned by hcitool correct? Please reply.
and another decoding question where you could simple let hcidump -X -V
do it for you. Also calling hciconfig hci0 pageto would tell you if the
command works or not. Including hciconfig hci0 commands if you wanna get
this specific list of supported commands.
There are manual pages available for every Bluetooth command. Please
read them first before posting.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-11-15 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 7:52 [Bluez-users] device doesn't support jm
2007-11-15 17:58 ` 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=1195149511.5175.118.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=bluez-users@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