public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Cc: hal@freedesktop.org
Subject: Re: [Bluez-devel] Re: Bluetooth and HAL
Date: Thu, 20 Jan 2005 13:50:40 +0100	[thread overview]
Message-ID: <1106225440.8190.175.camel@pegasus> (raw)
In-Reply-To: <pan.2005.01.20.08.17.45.630346@yahoo.com>

Hi Paul,

> I'll remove the ChipVersion then, and I have some more questions:
> How do we tell if we have a BT 1.0 or BT 1.1 or BT 1.2  adapter ?
> By looking at HCI and LMP numbers ?

it is the HCI_version and LMP_version. They can be different, but in
general they show the same version of the specification.

> Do we need a separate bluetooth.version too ?

No.

> Do end user programs really need HCI and LMP version/revision ?

Only if they wanna display some information about the device. Otherwise
they are useless, because the kernel or the Bluetooth library will hide
the differences.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-01-20 12:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19 22:54 [Bluez-devel] Bluetooth and HAL Paul Ionescu
2005-01-20  0:26 ` Marcel Holtmann
2005-01-20  8:17   ` [Bluez-devel] " Paul Ionescu
2005-01-20 12:50     ` Marcel Holtmann [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=1106225440.8190.175.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=hal@freedesktop.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