From: Roel Huybrechts <lists@rulus.be>
To: linux-bluetooth@vger.kernel.org
Subject: Setting Inquiry Transmit Power Level
Date: Mon, 18 Oct 2010 18:54:10 +0200 [thread overview]
Message-ID: <20101018165410.GA5788@titan> (raw)
[-- Attachment #1: Type: text/plain, Size: 1727 bytes --]
Dear list,
I'm facing the same problem that Natale Vinto mentioned nearly a
year ago [1] on this list. I'm trying to set the Inquiry Transmit
Power Level of a Belkin USB Bluetooth adapter, unfortunately
without much of success.
It is a Bluetooth 2.1 capable device as mentioned by hciconfig:
# hciconfig hci0 version
hci0: Type: BR/EDR Bus: USB
BD Address: 00:19:0E:08:62:EC ACL MTU: 1021:8 SCO MTU: 64:1
HCI Version: 2.1 (0x4) Revision: 0x5184
LMP Version: 2.1 (0x4) Subversion: 0x420e
Manufacturer: Broadcom Corporation (15)
# hciconfig hci0 revision
hci0: Type: BR/EDR Bus: USB
BD Address: 00:19:0E:08:62:EC ACL MTU: 1021:8 SCO MTU: 64:1
Firmware 132.66 / 14
Writing the inqtpl is supported, as shown by 'hciconfig hci0
commands'.
However:
# hciconfig hci0 inqtpl
hci0: Type: BR/EDR Bus: USB
BD Address: 00:19:0E:08:62:EC ACL MTU: 1021:8 SCO MTU: 64:1
Inquiry transmit power level: 0
# hciconfig hci0 inqtpl 4
# hciconfig hci0 inqtpl
hci0: Type: BR/EDR Bus: USB
BD Address: 00:19:0E:08:62:EC ACL MTU: 1021:8 SCO
MTU: 64:1
Inquiry transmit power level: 0
All this happens with Bluez 4.70 (the one from Debian unstable)
on a (pretty much plain upstream) 2.6.32.22 kernel.
I'd like to hear from you if this is a hardware or firmware issue
of the adapter/chip (in which case I suspect it can't be fixed
and I need to find another adapter which isn't broken), or
whether it can be a Bluez issue.
[1] http://www.spinics.net/lists/linux-bluetooth/msg03785.html
Thanks very much for your time.
Have a nice day,
Roel Huybrechts
--
GPG | 4096R/5E2DE374
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2010-10-18 16:54 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=20101018165410.GA5788@titan \
--to=lists@rulus.be \
--cc=linux-bluetooth@vger.kernel.org \
/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).