From: "David Stockwell" <dstockwell@frequency-one.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Experimental Mode: org.bluez.Adapter Methods/Signals
Date: Fri, 28 Mar 2008 18:31:40 -0500 [thread overview]
Message-ID: <019401c8912b$e1876ff0$6701a8c0@freqonedev> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2152 bytes --]
In the adapter.c code (bluez-utils-3.29), there are a number of 4.x methods and signals, which are enabled when hcid is run in experimental mode (-x in startup).
There are a whole lot of others that are labeled as "deprecated", but which are currently available when hcid is in experimental mode, as well as when it is not. Are these in fact going to be dropped when 4.x is released?
On a similar topic:
When the 4.x methods are registered, they register on bus "org.bluez", with interface "org.bluez.Adapter", but unlike 3.x, the path they use is not "/org/bluez/hci0" but just "/hci0" (for the default case). Is this intentional and the future direction of bluez-dbus?
I ask because when I tried calling DiscoverDevices, it would fail when I called with path "/org/bluez/hci0", but would run when I called it with path "/hci0". But, the funny thing is that because the RemoteDeviceFound signal is registered to both the old path and the new path, the signals come back on "/org/bluez/hci0".
Interestingly enough, when I register callbacks for DiscoveryStarted, RemoteDeviceFound, and DiscoveryCompleted against proxies that reference both the old and new path, I find that signals for DiscoveryStarted and DiscoveryCompleted come back against both paths, but the actual RemoteDeviceFound (and RemoteNameUpdated) comes back only against the 3.x path.
before dbus_g_proxy_call: DiscoverDevices
bus: org.bluez
path: /hci0
interface: org.bluez.Adapter
Signal from org.bluez.Adapter path: /org/bluez/hci0
DiscoveryStarted()
Signal from org.bluez.Adapter path: /hci0
DiscoveryStarted()
Signal from org.bluez.Adapter path: /org/bluez/hci0
RemoteDeviceFound(00:1C:CC:D6:90:3F,7a020c,0)
Signal from org.bluez.Adapter path: /org/bluez/hci0
RemoteNameUpdated(00:1C:CC:D6:90:3F,BlackBerry 8320)
Signal from org.bluez.Adapter path: /hci0
DiscoveryCompleted()
Signal from org.bluez.Adapter path: /org/bluez/hci0
DiscoveryCompleted()
I would appreciate a sense of direction, because I am working on avrcp/control, and want to make sure I am aligned with your plans going forward.
David Stockwell
[-- Attachment #1.2: Type: text/html, Size: 3321 bytes --]
[-- Attachment #2: Type: text/plain, Size: 278 bytes --]
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2008-03-28 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 23:31 David Stockwell [this message]
2008-03-29 1:03 ` [Bluez-devel] Experimental Mode: org.bluez.Adapter Methods/Signals Marcel Holtmann
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='019401c8912b$e1876ff0$6701a8c0@freqonedev' \
--to=dstockwell@frequency-one.com \
--cc=bluez-devel@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