From: David Given <dg@tao-group.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] API documentation?
Date: Wed, 09 May 2007 18:21:10 +0100 [thread overview]
Message-ID: <46420306.8020509@tao-group.com> (raw)
In-Reply-To: <be976db60705090927n71d22c0an5116c8a1323ed3a3@mail.gmail.com>
Mark S. Townsley wrote:
[...]
> I tried to search online but could not find any answer. I searched the
> archive, nothing comes up. Can you provide your expertise on this one?
> What are these .service files? How can I make one for org.bluez?
I'm using a Ubuntu Feisty, which is only a few weeks old; bluez-utils appears
to be the critical package, containing hcid (that seems to do the work) and
/etc/dbus-1/system.d/bluetooth.conf (that declares the Bluetooth service). I
can't find any documentation describing how to set all this up, though...
[...]
> On 5/9/07, Marcel Holtmann <marcel@holtmann.org> wrote:
>> to be quite frankly, then don't ask me about it. If you wanna screw with
>> your system you are on your own.
You seem not to have much experience with embedded systems.
On my system, there are two instances of dbus-daemon occupying 432 pages and
304 pages respectively, an instance of dbus-launch with 244, and an instance
of hcid with 348. There are also two *more* instances of dbus-daemon, but they
may be specific to the user and so irrelevant. Even so, that's still a total
of 1328 pages, or 5312kB.
That's just not *reasonable* on a system with low memory, especially since
Bluetooth will be the only thing that uses it.
Since all this code is going to have to go through the kernel interface anyway
to get anything done, it's far more appropriate to use that instead.
Particularly since there's a helpful library, hcilib, that wraps the kernel
interface and makes it easy to use. (And which, BTW, is recommended by all the
tutorial code I've been able to find.)
I was hoping that someone would be able to point me at the document that
specifies what this interface actually *is*.
--
David Given
dg@tao-group.com
This message is subject to Tao's e-mail terms ( http://e.tao-group.com/1 )
Tao Group Ltd, 62/63 Suttons Business Park, Suttons Park Avenue,
Reading, Berkshire RG6 1AZ. Registered in England, number 2722079
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-05-09 17:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 14:27 [Bluez-users] API documentation? David Given
2007-05-09 14:52 ` Marcel Holtmann
2007-05-09 15:18 ` David Given
2007-05-09 15:27 ` Marcel Holtmann
2007-05-09 15:36 ` David Given
2007-05-09 16:02 ` Marcel Holtmann
2007-05-09 16:27 ` Mark S. Townsley
2007-05-09 17:21 ` David Given [this message]
2007-05-09 20:32 ` Choi Sonim
2007-05-10 7:09 ` Marcel Holtmann
2007-05-10 8:01 ` Erwin Authried
2007-05-10 9:32 ` Marcel Holtmann
2007-05-10 11:19 ` Andrew Kohlsmith
2007-05-10 12:57 ` Marcel Holtmann
2007-05-10 13:44 ` Andrew Kohlsmith
2007-05-10 13:51 ` Marcel Holtmann
2007-05-10 9:34 ` David Given
2007-05-10 9:40 ` Marcel Holtmann
2007-05-09 22:29 ` Johan Hedberg
2007-05-10 3:58 ` Mark S. Townsley
2007-05-10 4:03 ` Mark S. Townsley
2007-05-10 9:49 ` Pierre-Yves Paulus
-- strict thread matches above, loose matches on Subject: below --
2007-05-10 12:23 Voni Hakau
2007-05-10 13:10 ` Marcel Holtmann
2007-05-10 13:47 ` Andrew Kohlsmith
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=46420306.8020509@tao-group.com \
--to=dg@tao-group.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 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).