From: Antonio Ospite <ospite@studenti.unina.it>
To: simon@mungewell.org
Cc: "Bastien Nocera" <hadess@hadess.net>,
linux-bluetooth@vger.kernel.org, linux-input@vger.kernel.org,
"Jim Paris" <jim@jtan.com>, "Ranulf Doswell" <ralf@ranulf.net>,
"Pascal A . Brisset" <pascal44973@pabr.org>,
"Marcin Tolysz" <tolysz@gmail.com>,
"Christian Birchinger" <joker@netswarm.net>,
"Filipe Lopes" <falktx@gmail.com>, "Alan Ott" <alan@signal11.us>,
"Mikko Virkkila" <virkkila@kapsi.fi>
Subject: Re: [PATCH v2 3/3] Add sixaxis plugin: USB pairing and LEDs settings
Date: Wed, 8 Jun 2011 11:20:54 +0200 [thread overview]
Message-ID: <20110608112054.1521ada7.ospite@studenti.unina.it> (raw)
In-Reply-To: <d49388493b61c568c5ce7cd2ae9594e0.squirrel@host171.canaca.com>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
On Fri, 3 Jun 2011 11:56:38 -0400
simon@mungewell.org wrote:
> Just generally on this subject, should the code which performs the USB
> 'write' be in 'hid-sony.c' rather than the BT core.
>
> It's possible that the Sixaxis or other compatible controllers will be
> only USB connected and BT might not even exist on the system.
>
> If/When I manage to do some work on rumble support, we will probably need
> to ensure that a 'hid-sonyff.c' is aware of any LED settings otherwise it
> might overwrite them when setting the rumble.
>
About leds: in order to decide which leds to set in a meaningful way we
need to know the X in /dev/input/jsX, and udev is the only way I know
to find that out, so either in a bluez plugin or in a standalone
daemon I think the answer is in userspace.
About knowing the led status, I have to check if we can read the led
settings out of the device after we have set them in the HID Output
Report, that's a good point.
Thanks,
Antonio
--
Antonio Ospite
http://ao2.it
PGP public key ID: 0x4553B001
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-06-08 9:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 10:04 [PATCH v2 0/3] Another try for the Sixaxis plugin Antonio Ospite
2011-02-25 10:04 ` [PATCH v2 1/3] Remove input/sixpair.c Antonio Ospite
2011-02-25 10:04 ` Antonio Ospite
2011-02-25 10:04 ` [PATCH v2 2/3] Re-add manager_get_default_adapter() Antonio Ospite
2011-02-25 10:04 ` [PATCH v2 3/3] Add sixaxis plugin: USB pairing and LEDs settings Antonio Ospite
2011-02-25 10:04 ` Antonio Ospite
2011-05-06 1:14 ` Bastien Nocera
2011-05-06 1:14 ` Bastien Nocera
2011-05-06 8:45 ` Antonio Ospite
2011-05-06 8:45 ` Antonio Ospite
2011-05-06 23:14 ` Antonio Ospite
2011-05-06 23:14 ` Antonio Ospite
2011-05-07 16:57 ` Bastien Nocera
2011-05-07 16:57 ` Bastien Nocera
2011-06-03 11:59 ` Antonio Ospite
2011-06-03 15:25 ` Bastien Nocera
2011-06-03 15:25 ` Bastien Nocera
2011-06-03 15:56 ` simon
2011-06-08 9:20 ` Antonio Ospite [this message]
2011-02-25 12:34 ` [PATCH v2 0/3] Another try for the Sixaxis plugin Bastien Nocera
2011-02-25 12:34 ` Bastien Nocera
2011-03-24 17:32 ` Antonio Ospite
2011-03-25 15:31 ` Jim Paris
2011-03-25 16:27 ` Antonio Ospite
2011-02-25 14:11 ` pascal44973
2011-02-25 15:49 ` Simon Kenyon
2011-02-25 15:49 ` Simon Kenyon
2011-02-25 16:02 ` Bastien Nocera
2011-02-25 16:02 ` Bastien Nocera
2011-04-30 11:31 ` Joakim Plate
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=20110608112054.1521ada7.ospite@studenti.unina.it \
--to=ospite@studenti.unina.it \
--cc=alan@signal11.us \
--cc=falktx@gmail.com \
--cc=hadess@hadess.net \
--cc=jim@jtan.com \
--cc=joker@netswarm.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=pascal44973@pabr.org \
--cc=ralf@ranulf.net \
--cc=simon@mungewell.org \
--cc=tolysz@gmail.com \
--cc=virkkila@kapsi.fi \
/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.