All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erwin Authried <eauth@softsys.co.at>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] API documentation?
Date: Thu, 10 May 2007 10:01:50 +0200	[thread overview]
Message-ID: <1178784111.10803.27.camel@localhost.localdomain> (raw)
In-Reply-To: <1178780976.25565.6.camel@aeonflux.holtmann.net>

Am Donnerstag, den 10.05.2007, 09:09 +0200 schrieb Marcel Holtmann:
> Hi David,
> 
> > >> 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.
> 
> actually I have quite some experience with embedded systems and I used
> to think the same way as you do right now, but D-Bus is the way to go
> even for embedded systems. There is no excuse. If D-Bus is not suitable
> then fix D-Bus and don't blame the system using it.
> 
> > 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.
> 
> And how is the D-Bus overhead a BlueZ problem. Again if the current
> D-Bus daemon and its library is not suitable, then fix it.
> 
Until now, it seems that nobody has ported d-bus to uClinux. Doing that
isn't trivial, because there are several uses of fork() that isn't
available in uClinux. In openwrt, there isn't any mention of d-bus at
all. Most probably, the footprint is too large for memory-restricted
systems. Because of that and the fact there are very few (if any)
projects for embedded systems that use d-bus it's hardly worth the
effort to port it. Bluez has worked quite well for embedded systems with
older versions, but since it ignores the demands of embedded systems
it's probably better to use a different bluetooth stack. 

Regards,
Erwin



-------------------------------------------------------------------------
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

  reply	other threads:[~2007-05-10  8:01 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
2007-05-09 20:32               ` Choi Sonim
2007-05-10  7:09               ` Marcel Holtmann
2007-05-10  8:01                 ` Erwin Authried [this message]
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=1178784111.10803.27.camel@localhost.localdomain \
    --to=eauth@softsys.co.at \
    --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.