From: Bastien Nocera <hadess@hadess.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Todd Showalter <todd@electronjump.com>,
David Herrmann <dh.herrmann@gmail.com>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>
Subject: Re: Game Controllers
Date: Sat, 07 Sep 2013 14:01:07 -0300 [thread overview]
Message-ID: <1378573267.1499.3.camel@sirocco> (raw)
In-Reply-To: <20130503155000.GA5567@core.coreip.homeip.net>
Em Fri, 2013-05-03 às 08:50 -0700, Dmitry Torokhov escreveu:
> On Thu, May 02, 2013 at 05:10:42PM -0400, Todd Showalter wrote:
> > On Thu, May 2, 2013 at 4:45 PM, Dmitry Torokhov
> > <dmitry.torokhov@gmail.com> wrote:
> >
> > > Again, the kernel will try to do the right thing and produce the correct
> > > events for new input devices, but we are not going to introduce a copy
> > > of evdev protocol that limits the events to "standard gamepad" ones.
> >
> > Ok. I can see there's no point arguing this. What can I do to at
> > least make sure future devices behave? Is there anything that can be
> > done about current devices other than translate in userspace?
>
> Please post the patches for discussion and keep en eye on changes going
> into drivers/input/joystick and drivers/hid as you have a vested
> interest of everyone getting it right.
>
> I am not sure about status of PS3 controller, I think Bastien was
> working on supporting it from userspace?
Antonio Ospite has patches against bluez5 to make it work[1], though
some more work is definitely needed. Benjamin Tissoires has a test
device now, so between them, they should be able to get it running
again.
Cheers
[1]: http://pkgs.fedoraproject.org/cgit/bluez.git/tree/playstation-peripheral-pugin-v5.x.patch
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-09-07 17:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 0:13 Game Controllers Todd Showalter
2013-04-29 21:04 ` Dmitry Torokhov
2013-04-30 0:46 ` Todd Showalter
2013-05-02 6:35 ` Antonio Ospite
2013-05-02 13:46 ` Todd Showalter
2013-05-02 14:09 ` David Herrmann
2013-05-02 15:37 ` Todd Showalter
2013-05-02 16:55 ` Dmitry Torokhov
2013-05-02 15:58 ` Todd Showalter
2013-05-02 16:38 ` Dmitry Torokhov
2013-05-02 17:06 ` Todd Showalter
2013-05-02 18:29 ` Dmitry Torokhov
2013-05-02 19:54 ` Todd Showalter
2013-05-02 20:18 ` Dmitry Torokhov
2013-05-02 20:30 ` Todd Showalter
2013-05-02 20:49 ` Dmitry Torokhov
2013-05-02 17:01 ` Dmitry Torokhov
2013-05-02 17:35 ` Todd Showalter
2013-05-02 17:54 ` David Herrmann
2013-05-02 19:10 ` Todd Showalter
2013-05-02 20:45 ` Dmitry Torokhov
2013-05-02 21:10 ` Todd Showalter
2013-05-03 15:50 ` Dmitry Torokhov
2013-09-07 17:01 ` Bastien Nocera [this message]
2013-05-03 10:29 ` Simon Farnsworth
2013-05-03 12:57 ` Todd Showalter
2013-05-03 16:01 ` Dmitry Torokhov
2013-05-03 17:12 ` Todd Showalter
2013-05-03 22:03 ` Ignaz Forster
2013-05-04 13:48 ` Todd Showalter
2013-05-02 3:25 ` Ray Dillinger
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=1378573267.1499.3.camel@sirocco \
--to=hadess@hadess.net \
--cc=dh.herrmann@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=todd@electronjump.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).