Linux bluetooth development
 help / color / mirror / Atom feed
From: Peter Stephenson <pws@csr.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] phone model and link manager version
Date: Fri, 09 Feb 2007 11:02:17 +0000	[thread overview]
Message-ID: <200702091102.l19B2H0L012760@news01.csr.com> (raw)
In-Reply-To: <b5dccebe0702090241w797ff03fk8dc41eb2e8881015@mail.gmail.com>

"Mikael Lindqvist" wrote:
> I wonder if there is any correlation between the Link Manager Protocol
> (LMP) Subversion and the model of a bluetooth phone.

Yes and no, but mostly no.  The LMP subversion is that of the link
manager on the Bluetooth chip, not (for example) the phone's GSM
baseband chip---unless Bluetooth is built into the latter, which is
possible but not very common.  In either case it's probably not telling
you the sorts of things you want to know about the phone, simply about
the phone manufacturer's procurement policy.

Note that because they're telling you about the Bluetooth chip, the LMP
and HCI subversion numbers are useless without the Bluetooth
manufacturer ID (which is also reported).  You can decode these
from http://www.bluetooth.org/assigned-numbers/company_identifiers.php

There will be *some* correlation: an older version is likely to appear
in an older phone, obviously.  But even the same model of phone might
have a different version of the firmware, and in some cases even a
completely different Bluetooth chip.  There's not even a requirement
that the LMP subversion is monotonically increasing with time.

pws


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

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2007-02-09 11:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 10:41 [Bluez-users] phone model and link manager version Mikael Lindqvist
2007-02-09 11:02 ` Peter Stephenson [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=200702091102.l19B2H0L012760@news01.csr.com \
    --to=pws@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