Re: xbox 360 wireless controller xpad360 driver

Re: xbox 360 wireless controller xpad360 driver

[Jiri Kosina]

On Fri, 6 Aug 2010, Kenneth Ray Smith II wrote:

> https://bugs.launchpad.net/ubuntu/+bug/365435
> 
> http://art.ubuntuforums.org/showthread.php?p=7412807

Hi,

as this is related to xpad driver, I am adding some relevant CCs. For the 
future, please always send some short summary of the problem ... just 
sending URLs with no explanation whatsoever makes it likely to be lost in 
other noise.

Thanks,

-- 
Jiri Kosina
SUSE Labs, Novell Inc.

Re: xbox 360 wireless controller xpad360 driver

[Christoph Fritz]

On Mon, 2010-08-09 at 11:36 +0200, Jiri Kosina wrote:
> On Fri, 6 Aug 2010, Kenneth Ray Smith II wrote:
> 
> > https://bugs.launchpad.net/ubuntu/+bug/365435
> > 
> > http://art.ubuntuforums.org/showthread.php?p=7412807
> 
> Hi,
> 
> as this is related to xpad driver, I am adding some relevant CCs. For the 
> future, please always send some short summary of the problem ... just 
> sending URLs with no explanation whatsoever makes it likely to be lost in 
> other noise.

Hi,

as I can see from https://bugs.launchpad.net/ubuntu/+bug/365435 it's
subject is: "xbox 360 wireless controller acts like curser or mouse."

But xpad.c doesn't use any relative axes. What it used were mouse
buttons, but this was fixed with following commit:

commit 7beae7028acec3bb235fa079fd7e45cc289c0fd7
Author: Christoph Fritz <chf.fritz@googlemail.com>
Date:   Tue Jul 13 09:42:33 2010 -0700

    Input: xpad - remove mouse buttons and axes for dance pads
    
    Dance pads don't have any axes/sticks, only buttons for directions. For
    example buttons like left+right will get triggered at once, an axis
    can't handle this anyway.  So this patch adds a module parameter named
    "sticks_to_null" for unknown devices. A known dance pad makes use of
    it by changing to a new mapping-option named DANCEPAD_MAP_CONFIG. Other
    tested devices may follow by adding this mapping-option too.
    
    Some buttons of xpad-devices are addressing mouse-buttons instead of
    gamepad-buttons. This gets fixed too.
    

And maybe we should make module param dpad_to_buttons work for known
pads too, so that a user can decide if the pressure should get measured
in simple key_events (0 or 1) or as an axis with "analog" values.
Because all programs (games) I know of don't like buttons reported as
axes. Even further, I was told that most xbox games don't make use of
this pressure-hitting-button-feature.
So if it would be up to me - I would remove the whole analog-button
thing or make option dpad_to_buttons default. Should I go for it?

 thanks,
  chf