linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Natale Vinto <ebballon@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Getting/setting Inquiry trasmit power level unsolved
Date: Mon, 14 Dec 2009 09:55:14 -0800	[thread overview]
Message-ID: <1260813314.4041.17.camel@localhost.localdomain> (raw)
In-Reply-To: <c6e9632c0912140824m5650d242w8296dd756943993f@mail.gmail.com>

Hi Natale,

> I finally got the Belkin F8T016, linked from CSR website (
> http://www.csr.com/applications/qual-mod.php?catID=14 ) as qualified
> end product with CSR's BlueCore chip.
> I read this spec:
> Bluetooth v2.1 + EDR
> Class 2
> 
> The output is always the same:
> 
> # hciconfig hci0
> hci0:   Type: USB
>         BD Address: 00:0A:3A:xx:xx:xx ACL MTU: 1021:8 SCO MTU: 64:1
>         UP RUNNING PSCAN
>         RX bytes:1129 acl:0 sco:0 events:42 errors:0
>         TX bytes:1616 acl:0 sco:0 commands:42 errors:0
> 
> # lsusb
> Bus 002 Device 006: ID 050d:016a Belkin Components
> 
> # hciconfig hci0 commands | grep "Inquiry Transmit Power Level"
>         'Read Inquiry Transmit Power Level'
>         'Write Inquiry Transmit Power Level'
> 
> (started hcidump here)
> 
> # hciconfig hci0 inqtpl
> hci0:   Type: USB
>         BD Address: 00:0A:3A:xx:xx:xx ACL MTU: 1021:8 SCO MTU: 64:1
>         Inquiry transmit power level: 0
> 
> # hciconfig hci0 inqtpl 1
> 
> # hcidump -X -V
> HCI sniffer - Bluetooth packet analyzer ver 1.42
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: Read Inquiry Response Transmit Power Level (0x03|0x0058) plen 0
> > HCI Event: Command Complete (0x0e) plen 5
>     Read Inquiry Response Transmit Power Level (0x03|0x0058) ncmd 1
>     status 0x00 level 0
> < HCI Command: Write Inquiry Response Transmit Power Level (0x03|0x0059) plen 1
>     level 1
> > HCI Event: Command Complete (0x0e) plen 4
>     Write Inquiry Response Transmit Power Level (0x03|0x0059) ncmd 1
>     status 0x00
> 
> but inquiry transmit level remains 0
> # hciconfig hci0 inqtpl
> hci0:   Type: USB
>         BD Address: 00:0A:3A:xx:xx:xx ACL MTU: 1021:8 SCO MTU: 64:1
>         Inquiry transmit power level: 0
> 
> This try made on Ubuntu 9.10 2.6.31 (kernel.org) and 2.6.31-16-generic
> (Ubuntu kernel)
> # dpkg -l bluez
> ii  bluez                   4.51-0ubuntu2           Bluetooth tools and daemons
> 
> So I wonder what is the problem...have I to flash in someway some firmware?

you would have to talk to CSR here. I have no idea what their firmware
is doing.

Regards

Marcel



  reply	other threads:[~2009-12-14 17:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13 18:47 Getting/setting Inquiry trasmit power level unsolved Natale Vinto
2009-11-15 11:57 ` Marcel Holtmann
2009-11-17 16:53   ` Natale Vinto
2009-11-17 20:56     ` Marcel Holtmann
2009-11-17 21:18       ` Natale Vinto
2009-11-18 17:59         ` Natale Vinto
2009-11-18 18:15           ` Marcel Holtmann
2009-11-27 18:11             ` Natale Vinto
2009-12-14 16:24               ` Natale Vinto
2009-12-14 17:55                 ` Marcel Holtmann [this message]
2009-12-23 13:53                   ` Steven Singer

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=1260813314.4041.17.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=ebballon@gmail.com \
    --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).