From: Steven Singer <steven.singer@csr.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Getting/setting Inquiry trasmit power level unsolved
Date: Wed, 23 Dec 2009 13:53:21 +0000 [thread overview]
Message-ID: <4B3220D1.3000107@csr.com> (raw)
In-Reply-To: <1260813314.4041.17.camel@localhost.localdomain>
Marcel Holtmann wrote:
> Natale Vinto wrote:
>> 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.
[...]
>> 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
I can tell from the ACL MTU that's not one of ours.
I have heard rumours (probably on this mailing list) that OEMs
sometimes change the chipset they use in devices without telling
anyone.
Isn't there some option to hciconfig that dumps the manufacturer ID
and firmware version (maybe hciconfig hci0 version)?
--
Steven Singer
Software Engineer
Cambridge Silicon Radio Ltd. Tel: +44 (0)1223 692000 Fax: +44 (0)1223 692001
Churchill House, Cambridge Business Park, Cowley Road, Cambridge CB4 0WZ, UK
Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
prev parent reply other threads:[~2009-12-23 13:53 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
2009-12-23 13:53 ` Steven Singer [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=4B3220D1.3000107@csr.com \
--to=steven.singer@csr.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).