From: "David Stockwell" <dstockwell@frequency-one.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Cc: "Marcel Holtmann" <marcel@holtmann.org>
Subject: Re: [Bluez-devel] UPDATE: org.bluez.Adapter Methods/Signals
Date: Tue, 8 Apr 2008 12:54:21 -0500 [thread overview]
Message-ID: <00f801c899a1$946db020$6701a8c0@freqonedev> (raw)
In-Reply-To: 2B4A186F-49DD-4131-ABB7-46E79D1A9DE8@holtmann.org
To be clear, I have registered the RemoteDeviceFound and RemoteNameUpdated signals against both "/org/bluez/hci0" AND "/hci0" (both
with "org.bluez.Adapter" interface). Signals for these signals always come back against "/org/bluez/hci0", and NOT against "/hci0"
(path retrieved with dbus_g_proxy_get_path).
DS
----- Original Message -----
From: "Marcel Holtmann" <marcel@holtmann.org>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Sent: Monday, April 07, 2008 5:58 PM
Subject: Re: [Bluez-devel] UPDATE: org.bluez.Adapter Methods/Signals
Hi David,
> After installing *-3.30, when calling DiscoverDevices, with path "/
> hci0", RemoteDeviceFound and RemoteNameUpdated are STILL returned
> against path "/org/bluez/hci0", and not the originating path, "/hci0".
that is fine. On /hci0 you should see DeviceFound signals.
Regards
Marcel
next prev parent reply other threads:[~2008-04-08 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 22:45 [Bluez-devel] UPDATE: org.bluez.Adapter Methods/Signals David Stockwell
2008-04-07 22:58 ` Marcel Holtmann
2008-04-08 17:54 ` David Stockwell [this message]
2008-04-08 18:56 ` Marcel Holtmann
2008-04-08 23:07 ` David Stockwell
2008-04-08 23:36 ` Marcel Holtmann
2008-04-09 0:08 ` David Stockwell
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='00f801c899a1$946db020$6701a8c0@freqonedev' \
--to=dstockwell@frequency-one.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.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