public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Johan Hedberg <johan.hedberg@nokia.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] D-BUS fixes for hcid
Date: Wed, 16 Jun 2004 14:18:18 +0200	[thread overview]
Message-ID: <1087388298.4309.10.camel@pegasus> (raw)
In-Reply-To: <20040616115718.GA8420@kone>

Hi Johan,

> The first part with the error handling is needed because
> dbus_pending_call_get_reply() may return NULL if a timeout occurs (a
> reply isn't received in time). Also, if new errors are added in the
> future it is probably better to check for the general case here:
> dbus_message_get_type().

ok, but the "message == NULL" must be moved into the D-Bus library. I
checked their source code and actually they miss a

	_dbus_return_val_if_fail (message != NULL, ???);

in their function.

> The second part (dbus_message_set_auto_activation) enables service
> activation if the PinAgent service isn't aquired by any process (i.e.
> the D-BUS daemon will execute the pin-helper program if needed).

The hcid shouldn't execute the D-Bus PIN helper. In case of a failure
with the D-Bus version it should fall back to the old one.

> Do you mean that without these changes, the pin-helper is automatically
> launched when a D-BUS message is sent by hcid to the service
> org.bluez.PinAgent? I could not get it working without the changes. What
> version of D-BUS are you using?

I use these tools:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  bluez-hcidump  1.5-2          Analyses Bluetooth HCI packets
ii  bluez-pin      0.23-1         Bluetooth PIN helper with D-BUS support
ii  bluez-utils    2.7-4          Bluetooth tools and daemons

And I set this in hcid.conf:

        # PIN helper
        pin_helper /usr/bin/bluez-pin;

        # D-Bus PIN helper
        dbus_pin_helper;

>>From my local .xession I start "bluez-pin --dbus &" and everything works
fine.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2004-06-16 12:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16 11:27 [Bluez-devel] D-BUS fixes for hcid Johan Hedberg
2004-06-16 11:37 ` Marcel Holtmann
2004-06-16 11:57   ` Johan Hedberg
2004-06-16 12:05     ` Johan Hedberg
2004-06-16 12:18     ` Marcel Holtmann [this message]
2004-06-16 12:45       ` Johan Hedberg
2004-06-16 13:06         ` Marcel Holtmann
2004-06-16 13:46           ` Johan Hedberg
2004-06-16 13:53             ` Marcel Holtmann
2004-06-16 13:58           ` Achim Bohnet
2004-06-16 14:18             ` Johan Hedberg
2004-06-16 23:06               ` Marcel Holtmann
2004-06-17  9:48                 ` Johan Hedberg
2004-06-17 12:05                   ` Marcel Holtmann
2004-06-17  7:27               ` Sjoerd Simons
2004-06-18  7:30                 ` Achim Bohnet

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=1087388298.4309.10.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=johan.hedberg@nokia.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