From: Mike Murphy <mamurph@cs.clemson.edu>
To: linux-kernel@vger.kernel.org
Cc: linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Greg KH <greg@kroah.com>, Oliver Neukum <oliver@neukum.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: PATCH [UPDATED] [0/3] input: xpad.c - Xbox 360 wireless and sysfs support
Date: Tue, 3 Mar 2009 22:55:26 -0500 [thread overview]
Message-ID: <5aa163d00903031955m42fc3583s3fc784dc3a8a1725@mail.gmail.com> (raw)
Greetings,
The following patchset is an update to my prior submission, which
addresses the code division, typecasting, and internal function
non-use issues present in the previous version of the patch. This
patch has not been changed since last night in the prior thread...
testing this evening confirmed that it is working correctly for the
Xbox 360 wireless hardware. Thanks to Andrew Morton, Greg K-H, and
Linus Torvalds for their help.
--- Original Description ---
This patchset improves the in-kernel xpad.c driver by improving
support for the Xbox 360 wireless controllers, and by adding a number
of features that can be controlled via a new sysfs interface. Rumble
is now enabled on the wireless 360 controllers, and the LED display is
set properly instead of flashing constantly. New features include
implementation of a dead zone for the analog sticks, ability to map
the stick inputs onto a square axis, ability to turn rumble off on a
per-controller basis, and a mechanism for identifying the controller
type and (presumably) unique ID of wireless controllers. In addition,
and as a change to the most recent development patch, I have adjusted
the triggers so that they both implement half-axes instead of full
axes. In other words, they report a range from 0 to +32767, instead of
-32767 to +32767. This change improves behavior on some gaming
emulators, and it can be turned off via the sysfs interface.
In addition to the core patch, I have updated
Documentation/input/xpad.txt, and I have added
Documentation/ABI/testing/game_device-sysfs-interface to document the
added sysfs interface. I'd like to thank Oliver Neukum, Greg
Kroah-Hartman, and Frederic Weisbecker for their helpful feedback
during the development process.
Mike
--
Mike Murphy
Ph.D. Candidate and NSF Graduate Research Fellow
Clemson University School of Computing
120 McAdams Hall
Clemson, SC 29634-0974 USA
Tel: +1 864.656.2838 Fax: +1 864.656.0145
http://cirg.cs.clemson.edu/~mamurph
reply other threads:[~2009-03-04 3:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5aa163d00903031955m42fc3583s3fc784dc3a8a1725@mail.gmail.com \
--to=mamurph@cs.clemson.edu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=greg@kroah.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).