From owner-freebsd-bluetooth@FreeBSD.ORG Sat Apr 11 19:07:21 2009 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09DBB106567C for ; Sat, 11 Apr 2009 19:07:21 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smtp02.one2one.net (smtp02.one2one.net [149.254.192.174]) by mx1.freebsd.org (Postfix) with ESMTP id 955AE8FC19 for ; Sat, 11 Apr 2009 19:07:20 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from [127.0.0.1] (helo=localhost) by localhost.t-mobile.co.uk with esmtp (Exim 4.50) id 1LsiXr-0006fT-8g; Sat, 11 Apr 2009 20:07:15 +0100 Received: from localhost.t-mobile.co.uk ([127.0.0.1]) by localhost (smtpbeckt01 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25404-03; Sat, 11 Apr 2009 20:07:14 +0100 (BST) Received: from [10.214.167.244] (helo=rya-online.net) by localhost.t-mobile.co.uk with smtp (Exim 4.50) id 1LsiXo-0006fO-Ex; Sat, 11 Apr 2009 20:07:14 +0100 Received: (nullmailer pid 1522 invoked by uid 1000); Sat, 11 Apr 2009 19:05:54 -0000 Date: Sat, 11 Apr 2009 20:05:54 +0100 (BST) To: Bruce Simpson In-Reply-To: <49E0DAE2.3030805@incunabulum.net> References: <49D92E26.2030508@incunabulum.net> <49DD40E2.5030403@incunabulum.net> <1239264003.862926.638.nullmailer@galant.ukfsn.org> <49DE4F44.8070707@incunabulum.net> <1239359436.893706.893.nullmailer@galant.ukfsn.org> <49DF8C8C.5030006@incunabulum.net> <49E0DAE2.3030805@incunabulum.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1239476754.337291.1460.nullmailer@galant.ukfsn.org> From: Iain Hibbert X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at example.com X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: plunky@rya-online.net X-SA-Exim-Scanned: No (on localhost.t-mobile.co.uk); SAEximRunCond expanded to false Cc: "freebsd-bluetooth@freebsd.org" , "alexei@raylab.com" Subject: Re: BlueZ dbus binding is device dependent X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Apr 2009 19:07:21 -0000 On Sat, 11 Apr 2009, Bruce Simpson wrote: > So, just to confirm, I read the code examples in this BlueZ Wiki article; > and it does indeed appear that the naming convention BlueZ uses in DBus is > BlueZ dependent:- > http://wiki.bluez.org/wiki/HOWTO/DiscoveringDevices first, that API may not be the same as the BlueZ 4.x series which I think has been evolving. The wiki main page says the API is best defined by the documents in the bluez releases. second, I'm not sure if it is a total disaster. The device being referenced is at least a string "/org/bluez/hci0" rather than the integer dev_id that the bluez library uses. That can be worked on fairly easily, plus I might have seen a comment on the bluez list (which I subscribed to but don't really read) that hardcoded defs are to be frowned on, I think there is a way to find local devices. Then, the module name "org.bluez" is probably not needed to change - for instance if a GNOME application uses the bluez dbus module, I think that all calls end up passed to bluetoothd and 'all that is required' is having a bluez compatible bluetoothd. Whether the bluez bluetoothd can be easily patched or if a fork or a rewrite is required I don't know. I looked at the bluez sources but I don't have any context for it so am just confused.. iain