From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Reading RSSI of non-connected devices
Date: Wed, 14 Dec 2005 18:17:08 +0100 [thread overview]
Message-ID: <1134580628.10473.8.camel@localhost> (raw)
In-Reply-To: <43A04C03.9030907@rumms.uni-mannheim.de>
Hi Andreas,
> >As Marcel mentioned earlier, the easiest is to use the D-Bus services in
> >hcid to do that.
> >
> He didn't. He said the safe way would be to use raw HCI sockets and (in
> other words) that the D-Bus interface was unstable. Also, I am currently
> testing this on desktop and notebook machines but it was actually
> supposed to run on mobile devices (Zaurus) where we would not be able to
> update the kernel and require the latest D-Bus/BlueZ interfaces.
the D-Bus interface has nothing to do with used kernel.
> Nontheless we will evaluate D-Bus, but for the time being my boss is
> content with HCI sockets under root account.
> I'm familiar with socket programming in general but haven't used D-Bus
> before and so we are worried whether introducing another layer such as
> D-Bus might be of disadvantage for our software which needs non-cached
> data, nearly in realtime (just as with HCI sockets). The D-Bus page
> itself says it's not stable yet and I did not find documentation on how
> to use it with BlueZ. The BlueZ library was very helpful in getting my
> code to work, whereas I have no clue on where to find any such hints for
> D-Bus both in the BlueZ 2.22 downloads and in the 2.6.13.4 kernel which
> were the latest respectively when I downloaded them some weeks ago. I
> can only guess from the examples at freedesktop.org that it'll be
> /org/bluez/something.
The D-Bus interface works quite good, but I won't guarantee a stable API
at the moment. If needed, I am going to break it.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-12-14 17:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 15:00 [Bluez-devel] Reading RSSI of non-connected devices Andreas Färber
2005-12-07 15:08 ` Marcel Holtmann
2005-12-07 16:21 ` Andreas Färber
2005-12-07 16:43 ` Marcel Holtmann
2005-12-14 15:21 ` Andreas Faerber
2005-12-14 15:26 ` Bastien Nocera
2005-12-14 16:44 ` Andreas Faerber
2005-12-14 17:17 ` Marcel Holtmann [this message]
2005-12-14 20:53 ` Andreas Färber
2005-12-14 16:23 ` Marcel Holtmann
2005-12-14 16:58 ` Andreas Faerber
2005-12-14 17:13 ` Marcel Holtmann
2005-12-14 20:43 ` Andreas Färber
2005-12-15 5:15 ` Marcel Holtmann
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=1134580628.10473.8.camel@localhost \
--to=marcel@holtmann.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).