From: Frederic Danis <frederic.danis@palmsource.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] [PATCH] DBus GetRemoteName problem
Date: Tue, 06 Jun 2006 16:35:07 +0200 [thread overview]
Message-ID: <4485929B.8010602@palmsource.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 556 bytes --]
Hello,
When I use GetRemoteName of dbus-test program I receive a
DiscoveryCompleted signal after the RemoteNameUpdated (or
RemoteNameFailed) signal.
You can find attached a patch to fix this.
Hope this helps.
Regards
Fred
--
-----------------------------------------------
It is not by improving the oil lamp that one invents the electric bulb!
-----------------------------------------------
Danis Frederic PalmSource Europe
Software engineer
Mail : mailto:frederic.danis@palmsource.com
-----------------------------------------------
[-- Attachment #2: fix_dbus_get_remote_name.patch --]
[-- Type: text/plain, Size: 430 bytes --]
--- dbus-adapter.c.orig 2006-06-06 11:35:32.000000000 +0200
+++ dbus-adapter.c 2006-06-06 14:51:57.000000000 +0200
@@ -1255,8 +1255,7 @@
* Otherwise, send the HCI cmd to get the remote name
*/
if (dbus_data->discover_state == STATE_IDLE) {
- if (!disc_device_req_name(dbus_data))
- dbus_data->discover_state = STATE_RESOLVING_NAMES;
+ disc_device_req_name(dbus_data);
}
return error_request_deferred(conn, msg);
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
[-- Attachment #4: 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:[~2006-06-06 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 14:35 Frederic Danis [this message]
2006-06-06 16:52 ` [Bluez-devel] [PATCH] DBus GetRemoteName problem Claudio Takahasi
2006-06-07 12:45 ` Claudio Takahasi
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=4485929B.8010602@palmsource.com \
--to=frederic.danis@palmsource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.