From: Sven Eckelmann <sven@narfation.org>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: simon@mungewell.org, linux-input@vger.kernel.org,
Jiri Kosina <jkosina@suse.cz>,
Colin Leitner <colin.leitner@gmail.com>
Subject: Re: Re: [PATCH] HID: sony: Add force feedback support for Dualshock3 USB
Date: Mon, 18 Nov 2013 00:53:25 +0100 [thread overview]
Message-ID: <8249378.0C4gn7PafG@sven-desktop> (raw)
In-Reply-To: <5434362.OvDlhOjSJd@sven-edge>
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
On Monday 18 November 2013 00:12:14 Sven Eckelmann wrote:
> > Also please make sure that setting the rumble does not change the LEDs
> > status if there is any set: HID output report 1 is used for both LEDs
> > and rumble. In the bluez plugin[1] I plan on setting LEDs from userspace
> > to match the joystick number, just as the PS3 does, it would be strange
> > for the user if a rumble event would reset the LEDs status.
>
> I never used the LEDs and therefore cannot say anything about it (I don't
> have a specification for the used command format). Maybe I can try to play
> with them next week.
>
> But you're patch has some comments in set_leds. Do I correctly interpret the
> byte 10 in leds_report as "only make changes to following LEDs"? So setting
> it to 1 would make the command not change the LEDs at all?
Ok, just tried it and it seems this byte is really for the LEDs. But
unfortunately, it is enabling/disabling the LEDs completely and not the
configuration.
And sending less bytes just lets everything fail.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-17 23:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 18:25 [PATCH] HID: sony: Add force feedback support for Dualshock3 USB Sven Eckelmann
2013-11-11 10:26 ` Jiri Kosina
2013-11-16 22:30 ` simon
2013-11-17 1:48 ` simon
2013-11-17 9:36 ` Sven Eckelmann
2013-11-17 16:30 ` David Herrmann
2013-11-17 18:08 ` Sven Eckelmann
2013-11-17 19:11 ` simon
2013-11-17 17:38 ` simon
2013-11-17 17:41 ` Sven Eckelmann
2013-11-17 22:25 ` Antonio Ospite
2013-11-17 23:12 ` Sven Eckelmann
2013-11-17 23:53 ` Sven Eckelmann [this message]
2013-11-18 0:26 ` Re: " Sven Eckelmann
2013-11-18 1:21 ` simon
2013-11-18 3:54 ` simon
2013-11-18 10:27 ` Antonio Ospite
2013-11-18 15:27 ` Antonio Ospite
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=8249378.0C4gn7PafG@sven-desktop \
--to=sven@narfation.org \
--cc=colin.leitner@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=ospite@studenti.unina.it \
--cc=simon@mungewell.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 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.