From: Marcel Holtmann <marcel@holtmann.org>
To: Bastien Nocera <hadess@hadess.net>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCHes] Add sixpair
Date: Thu, 16 Oct 2008 01:52:57 +0200 [thread overview]
Message-ID: <1224114777.28173.41.camel@californication> (raw)
In-Reply-To: <1224083727.5268.3149.camel@cookie.hadess.net>
Hi Bastien,
> Here are the patches to get sixpair support built into BlueZ. It uses
> libusb-1.0 as well as a yet to be merged libusb-1.0 patch to allow
> re-attaching a driver to a device.
so I applied all patches except the changes for the build system. I am
not sure that this is the right way to go.
If we require libusb-1.0, then we should just change our current code
that depends on libusb-0.1 and require libusb-1.0 for all of it.
> Problems left to solve:
> - sixaxis enabler code (as seen in enable_sixaxis() in compat/hidd.c)
> seems to have disappeared from the input plugin. Is that done in the
> kernel now, or was it just removed?
The kernel is not doing it. Seems to be an oversight.
> - After "cable pairing" the device, I need to unplug/replug the adapter,
> or restart bluetoothd. Can anyone think of a better way of getting the
> list of devices updated?
We could use inotify or SIGUSR2 or something to re-read the database.
> - Some minor niggles in the code itself (use D-Bus instead of parsing
> command-line tools)
Of course.
> - udev rule(s) and parsing only the selected device would be necessary
> if not required
If we can do this via the HID bus, then we can do it every time and it
would not affect the controller itself.
Regards
Marcel
next prev parent reply other threads:[~2008-10-15 23:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 15:15 [PATCHes] Add sixpair Bastien Nocera
2008-10-15 15:22 ` Marcel Holtmann
2008-10-15 23:52 ` Marcel Holtmann [this message]
2008-10-16 0:28 ` Bastien Nocera
2008-10-23 4:52 ` Marcel Holtmann
2009-02-28 21:48 ` AddCablePairedDevice (was Re: [PATCHes] Add sixpair) Bastien Nocera
2009-02-28 22:44 ` Marcel Holtmann
2009-02-28 23:47 ` Bastien Nocera
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=1224114777.28173.41.camel@californication \
--to=marcel@holtmann.org \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
/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