Linux bluetooth development
 help / color / mirror / Atom feed
From: "Mikael Lindqvist" <li.mikael.spam@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] phone model and link manager version
Date: Fri, 9 Feb 2007 11:41:04 +0100	[thread overview]
Message-ID: <b5dccebe0702090241w797ff03fk8dc41eb2e8881015@mail.gmail.com> (raw)

Hello,

I wonder if there is any correlation between the Link Manager Protocol
(LMP) Subversion and the model of a bluetooth phone. I mean, if I find
out the LMP subversion of a remote device with for example hcitool,
like this:

sudo hcitool info <bdaddr>

Requesting information ...
...
LMP Version: 1.2 (0x2) LMP Subversion: 0x41c

Can this subversion be used to identify the model of the phone?

If not, can it be used to suggest that the phone is any of a small set
of models?

If firmware updates are being made on the phone, will that affect the
LMP subversion?

What process inside a phone manufacturer company decide that a
Bluetooth chip with a certain LMP subversion ends up in a specific
model? Is it just related to when the phone happened to be produced or
is it somehow related to the model?

Thanks in advance!

-- Mikael

-------------------------------------------------------------------------
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 10:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 10:41 Mikael Lindqvist [this message]
2007-02-09 11:02 ` [Bluez-users] phone model and link manager version Peter Stephenson

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=b5dccebe0702090241w797ff03fk8dc41eb2e8881015@mail.gmail.com \
    --to=li.mikael.spam@gmail.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