linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] HCID D-Bus
Date: Fri, 09 Sep 2005 01:07:19 +0200	[thread overview]
Message-ID: <1126220839.5286.57.camel@blade> (raw)
In-Reply-To: <e1effdeb050908125079935830@mail.gmail.com>

Hi Claudio,

> In the last email about bluetoothd, you suggested send patches to
> enhance hcid. I studied the hcid code and I would like align our ideas
> before start coding. My suggestions are:
> 
> 1. Develop a common code addressing all D-Bus versions

not needed, because my plan is to drop support for anything below D-Bus
version 0.5 (which should be compatible with D-Bus 0.3x) starting with
bluez-utils-0.22. My original plan was to do it in next release, but
there are some memory leak fixes and I want to get out a new version as
soon as possible. However maybe it is a good idea to drop support for
older D-Bus versions now.

It seems the only problematic distribution is Debian unstable. Every
other distribution (including Ubuntu) uses at least D-Bus 0.35.

> 2. Send signals to connection complete and disconnection

While I was adding the signals for the inquiry responses, I thought
about doing this, too. I added the needed functions for it and open the
filter for these messages. The only problem is that the disconnect uses
the ACL handle and not the device address. This means you have to keep
track of all handles. Normally the kernel does this all for us. This is
one reason for a good/new interface between the kernel and bluetoothd.
Coding everything twice is stupid.

> 3. Register a D-Bus hci object path as a initial point for bluetoothd
> and provide basic services(inquiry, auth, ...).

Go ahead. I would really welcome it.

I need a job where I can fulltime work on bluetoothd and add all the
cool things we talked about. If anyone know one or has one, let me know.

> I am sending a patch to solve the problem of D-Bus versions. Sorry,
> byte array is not being handled yet, but I will fix it. This is just a
> idea of how solve the problem of several D-Bus versions. Get the dbus
> major/minor version in the "configure" is a better approach, instead
> of check if the function dbus_message_iter_get_basic belongs to the
> dbus-1 library. If you allow change the makefiles(acinclude.m4,
> configure.in, config.h.in ) I can modify it.

I like to drop support for older D-Bus versions. After a private talk
with J5 it seems the only sane way to do.

Regards

Marcel




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-09-08 23:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-08 19:50 [Bluez-devel] HCID D-Bus Claudio Takahasi
2005-09-08 23:07 ` Marcel Holtmann [this message]
2005-09-09  8:25   ` Peter Robinson
2005-09-09  9:37     ` Marcel Holtmann
2005-09-09 13:29       ` Sjoerd Simons
2005-09-09 13:40         ` Marcel Holtmann
2005-09-12 21:07           ` [Bluez-devel] HCID D-Bus (Sig Fault) Claudio Takahasi
2005-09-12 21:14             ` [Bluez-devel] HCID D-Bus (Seg Fault) Claudio Takahasi
2005-09-12 21:40             ` [Bluez-devel] HCID D-Bus (Sig Fault) Marcel Holtmann
2005-09-12 23:09               ` Claudio Takahasi
2005-09-12 23:21                 ` Marcel Holtmann
2005-09-13 13:03                   ` [Bluez-devel] HCID D-Bus (Seg Fault) Claudio Takahasi
2005-09-13 18:54                     ` Marcel Holtmann
2005-09-14 12:00                       ` Claudio Takahasi
2005-09-14 15:16                         ` Marcel Holtmann
2005-09-14 16:06                           ` Claudio Takahasi
2005-09-15  8:11                             ` 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=1126220839.5286.57.camel@blade \
    --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).