From: giulio fedel <giulio.fedel@andorsystems.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] BlueZ Hcid and D-Bus On ARM
Date: Fri, 31 Aug 2007 18:28:14 +0200 [thread overview]
Message-ID: <46D8419E.9050604@andorsystems.com> (raw)
In-Reply-To: <79be12f70708301153s7c6961e3jda270e4fe394d1ca@mail.gmail.com>
Yes,
I'm working on an arm platform (at91rm9200) and it works.
kernel 2.6.22
dbus 1.0.2
bluez 3.14
It is important that dbus and hcid use the same file location for the
socket:
[--prefix=]/var/run/dbus/system_bus_socket
where --prefix is /usr/local by default or something you specified
during configure phase.
dbus-daemon read it from etc/dbus-1/system.conf <listen>...</listen> line,
it not clear to me where hcid read it or if it uses only the default.
use hcid -n option (and the strace utility) to understand something more...
Giulio
John Sample wrote:
> Has anyone here gotten hcid to connect to D-Bus on an embedded ARM
> system? I can get the dbus system daemon up an running, but everytime I
> start hcid it dies right away and I get a "couldn't connect to D-Bus"
> message in my syslog. I don't know what else to even try - any
> suggestions?
>
> --
> John Sample
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-08-31 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 18:53 [Bluez-users] BlueZ Hcid and D-Bus On ARM John Sample
2007-08-31 15:00 ` wimpunk
2007-08-31 16:28 ` giulio fedel [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=46D8419E.9050604@andorsystems.com \
--to=giulio.fedel@andorsystems.com \
--cc=bluez-users@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.