Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 Apr 2009 20:05:54 +0100 (BST)
From:      Iain Hibbert <plunky@rya-online.net>
To:        Bruce Simpson <bms@incunabulum.net>
Cc:        "freebsd-bluetooth@freebsd.org" <freebsd-bluetooth@freebsd.org>, "alexei@raylab.com" <alexei@raylab.com>
Subject:   Re: BlueZ dbus binding is device dependent
Message-ID:  <1239476754.337291.1460.nullmailer@galant.ukfsn.org>
In-Reply-To: <49E0DAE2.3030805@incunabulum.net>
References:  <49D92E26.2030508@incunabulum.net>  <bb4a86c70904061358l3983ed51m11265859a833f202@mail.gmail.com>  <49DD40E2.5030403@incunabulum.net> <1239264003.862926.638.nullmailer@galant.ukfsn.org> <bb4a86c70904091013l2d7c2b77ic7f6988e6e7709f2@mail.gmail.com> <49DE4F44.8070707@incunabulum.net> <1239359436.893706.893.nullmailer@galant.ukfsn.org> <49DF8C8C.5030006@incunabulum.net> <49E0DAE2.3030805@incunabulum.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1239476754.337291.1460.nullmailer>