From: Marcel Holtmann <marcel@holtmann.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Bastien Nocera <hadess@hadess.net>,
BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Add sixaxis cable-pairing plugin
Date: Sat, 06 Jun 2009 19:51:08 +0200 [thread overview]
Message-ID: <1244310668.23850.76.camel@localhost.localdomain> (raw)
In-Reply-To: <2d5a2c100906061041n7f3793d4ud7bd80855c6788a8@mail.gmail.com>
Hi Luiz,
> First I would like to know if splitting the current code of gudev into
> udev-glib and udev-gobject would be a good idea to begin with. By
> looking at connmand code it seems quite simple to integrate glib
> mainloop with udev so if we were not adding any API to udev-glib it
> seems like an unnecessary step, I heard that udev has some race
> conditions so perhaps we could add some very basic watch registration
> like we have done to libgdus. That way udev-object API doesn't have to
> change much just depend on udev-glib.
>
> On bluetoothd side, I would like to make udev code generic enough to
> detect any bluetooth device not only sixaxis so we can do different
> plugins to handle any device doing this cable association/cable
> pairing thing.
don't bother with udev-glib here. The native libudev integration with
mainloop is simple enough. If you need an example, look at ConnMan.
Regards
Marcel
next prev parent reply other threads:[~2009-06-06 17:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 9:28 [PATCH] Add sixaxis cable-pairing plugin Bastien Nocera
2009-06-04 18:13 ` Marcel Holtmann
2009-06-05 10:42 ` Bastien Nocera
2009-06-05 13:06 ` Marcel Holtmann
2009-06-05 13:52 ` Bastien Nocera
2009-06-05 14:15 ` Marcel Holtmann
2009-06-05 14:48 ` Bastien Nocera
2009-06-05 14:56 ` Marcel Holtmann
2009-06-05 15:06 ` Bastien Nocera
2009-06-06 17:41 ` Luiz Augusto von Dentz
2009-06-06 17:51 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-09 13:19 Bastien Nocera
2009-10-11 9:40 ` 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=1244310668.23850.76.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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.