Return-Path: Subject: Re: [Bluez-devel] Re: Bluetooth and HAL From: Marcel Holtmann To: BlueZ Mailing List Cc: hal@freedesktop.org In-Reply-To: References: <1106180785.8190.151.camel@pegasus> Content-Type: text/plain Message-Id: <1106225440.8190.175.camel@pegasus> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 20 Jan 2005 13:50:40 +0100 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