Linux bluetooth development
 help / color / mirror / Atom feed
From: Steven Singer <steven.singer@csr.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] HCI version
Date: Tue, 23 Jan 2007 19:28:54 +0000	[thread overview]
Message-ID: <45B661F6.8010703@csr.com> (raw)
In-Reply-To: <001e01c73b12$ea34afc0$9301a8c0@LUBI>

Lauri Lubi wrote:
>         HCI Ver: 1.2 (0x2) HCI Rev: 0x7a6 LMP Ver: 1.2 (0x2) LMP Subver: 0x7a6
> 
> Is HCI Ver the same as supported Bluetooth version?

Yes it is. Or, at least, it's supposed to be.

Sadly, this dongle reports the wrong spec version. The firmware (0x07a6)
is BT 2.0 + EDR compliant, it just the dongle reports itself as just
BT 1.2 compliant.

I'm sure this firmware reported itself as 2.0 + EDR when we shipped it.

We did add the ability for the firmware to spoof its spec version to
work round a problem in some host stacks where they were rejecting
devices complaint to a later version of the spec than that to which the
stack had been written. Since a 2.0 + EDR device will work quite happily
with a 1.2 stack (there are no new HCI events) this was an easy
workaround. It's possible that the dongle manufacturer is shipping this
device with spoofing enabled because it was being bundled with such a
host stack.

The problem should be easily remedied by resetting the PS key
HCI_LMP_LOCAL_VERSION back to its default value of 0x0303, though, in
practice, it shouldn't make any difference. All this key does is change
what version the dongle reports to the stack not how the firmware
behaves. No devices or host stacks are meant to use the version number to
change their behaviour, they're meant to use the supported features. This
device will continue give EDR performance even without this change and
BlueZ should treat it as having 2.0 + EDR features. If you're intending to
use this dongle with a host stack that might be upset by a 2.0 + EDR device,
you should leave this PS key alone.

If you want to know whether 2.0 + EDR features are really supported then
look at the supported features, not the version.

	- Steven
-- 


To access the latest news from CSR copy this link into a web browser:  http://www.csr.com/email_sig.php

To get further information regarding CSR, please visit our Investor Relations page at http://ir.csr.com/csr/about/overview

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-01-23 19:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18 15:11 [Bluez-users] HCI version Lauri Lubi
2007-01-23 19:28 ` Steven Singer [this message]
2007-01-25  6:51   ` Lauri Lubi

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=45B661F6.8010703@csr.com \
    --to=steven.singer@csr.com \
    --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