On 5/30/07, Renato Golin <[email protected]> wrote:
Now, why joydev's input_dev is reporting -127, 127 just for the two first axis?
Is it getting hit with HID_QUIRK_BADPAD? What does evtest utility show for the device? -- Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: joydev.c and saitek cyborg evo force
- From: Jiri Kosina <[email protected]>
- Re: joydev.c and saitek cyborg evo force
- References:
- joydev.c and saitek cyborg evo force
- From: "Renato Golin" <[email protected]>
- Re: joydev.c and saitek cyborg evo force
- From: Dmitry Torokhov <[email protected]>
- Re: joydev.c and saitek cyborg evo force
- From: Jiri Kosina <[email protected]>
- Re: joydev.c and saitek cyborg evo force
- From: "Renato Golin" <[email protected]>
- Re: joydev.c and saitek cyborg evo force
- From: Jiri Kosina <[email protected]>
- Re: joydev.c and saitek cyborg evo force
- From: "Renato Golin" <[email protected]>
- Re: joydev.c and saitek cyborg evo force
- From: Jiri Kosina <[email protected]>
- Re: joydev.c and saitek cyborg evo force
- From: "Renato Golin" <[email protected]>
- Re: joydev.c and saitek cyborg evo force
- From: "Renato Golin" <[email protected]>
- joydev.c and saitek cyborg evo force
- Prev by Date: Re: BUG: sleeping function called from invalid context at kernel/fork.c:385
- Next by Date: Re: [PATCH] Report that kernel is tainted if there were an OOPS before (v2)
- Previous by thread: Re: joydev.c and saitek cyborg evo force
- Next by thread: Re: joydev.c and saitek cyborg evo force
- Index(es):
 |