public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] client.c cleanup
Date: Tue, 29 Jan 2008 17:24:06 +0000	[thread overview]
Message-ID: <1201627446.2389.121.camel@cookie.hadess.net> (raw)
In-Reply-To: <1201626119.6218.15.camel@violet>


On Tue, 2008-01-29 at 18:01 +0100, Marcel Holtmann wrote:
> Hi Bastien,
> 
> > Some time ago I had problems with client.c's architecture. It would
> > allow me to easily report completed discoveries without causing crashes.
> > 
> > The attached patch moves all the static variables into the main
> > BluetoothClient object, and instead of return a new object when using
> > _new() we return an existing instance of the client.
> > 
> > This makes no changes to the external API for the BluetoothClient, and
> > should work just as well as older versions did.
> 
> patch has been applied. Don't really see the difference, but I am okay
> with doing it this way.

There's no differences in terms of the outside API, but it allows the
signals coming back from hcid to have a reference to a BluetoothClient
object and thus sending out signals, etc.

> > A couple of bugs I found in client.c:
> > - launch test-client with a dongle inserted, remove and reinsert the
> > dongle, the bdaddr of the device is not set anymore
> > - launch test-client without a dongle inserted, insert it, the bdaddr is
> > not set and there's no children to the adapter (although there are if
> > inserted when started)
> > - launch test-client with a dongle inserted, remove it, add another one,
> > the set of known devices underneath hasn't changed
> > 
> > All those problems exist in the old version of client.c, and I intend on
> > fixing them, as well as making the search button work as expected in the
> > device selection widget.
> 
> Send patches when you figured it out :)

I think for most of those it would mean clearing the children of the
adapters (removing them from the tree). Not sure what's wrong about the
bdaddr not appearing for newly inserted devices though, probably just a
missing call.

Cheers


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2008-01-29 17:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-25  2:22 [Bluez-devel] [PATCH] client.c cleanup Bastien Nocera
2008-01-29 17:01 ` Marcel Holtmann
2008-01-29 17:24   ` Bastien Nocera [this message]
2008-01-29 17:35     ` Marcel Holtmann
2008-01-29 18:08       ` Bastien Nocera
2008-01-29 18:14         ` Marcel Holtmann
2008-01-30 17:31   ` Bastien Nocera
2008-01-31 14:57     ` Bastien Nocera
2008-01-31 17:48       ` Bastien Nocera
2008-02-01 10:46         ` Bastien Nocera
2008-02-01 12:11           ` Bastien Nocera
2008-02-01 12:23             ` 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=1201627446.2389.121.camel@cookie.hadess.net \
    --to=hadess@hadess.net \
    --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