From: yesir yao <yesiryao@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: dbus of c program for adapter get/set properties
Date: Thu, 23 Apr 2009 12:52:20 +0800 [thread overview]
Message-ID: <6edf6b480904222152ydbb7d53x7a77c16bd4192e58@mail.gmail.com> (raw)
In-Reply-To: <2d5a2c100904201950s3d8b2b84p2ddb4e89ac5bfe50@mail.gmail.com>
>>
>> I need to use dbus api to control my bluetooth adapter in my C program.
>> After I had read doc/adapter-api.txt and writed the codes, It can't work
>
> The answer is very simple, you are using fixed/hardcoded object path
> (/org/bluez/hci0) that is causing the problem. We made sure it won't
> work by adding the pid to the path so no one will have a change to
> hardcode an adapter path and the code still work after bluetoothd has
> restarted, the correct way of doing this is via '/' path (the only
> fixed path bluetoothd has) which implements org.bluez.Manager (see
> doc/manager-api.txt).
>
I have changed the code of bluez/src/manger.c,
and delete "getpid()" in func manager_init.
so the fixed object path (/org/bluez/hci0) works well.
> About the G_DBUS_METHOD_FLAG_ASYNC are really not for clients,
> although they hint the behavior of the daemon the client should know
> better whether to block or not.
the siample question is:
1) for dbus_connection_send_with_reply_and_block and
dbus_connection_send_with_reply,
which one I should use for the sample code in the first email ?
2) for func dbus_message_append_args, the parm I had set is right or not?
thx a lot for you helps.
prev parent reply other threads:[~2009-04-23 4:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 1:27 dbus of c program for adapter get/set properties yesir yao
2009-04-21 2:50 ` Luiz Augusto von Dentz
2009-04-23 4:52 ` yesir yao [this message]
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=6edf6b480904222152ydbb7d53x7a77c16bd4192e58@mail.gmail.com \
--to=yesiryao@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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