linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "M G" <lists.mg@googlemail.com>
To: linux-input@vger.kernel.org
Subject: xpad - led/rumble completely disables controller
Date: Fri, 21 Mar 2008 18:52:58 +0100	[thread overview]
Message-ID: <74d457500803211052l1beada9by3a72a240a3602dfe@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 447 bytes --]

Hi, I'm trying to use my Xbox360 Controller with the xpad driver. But
as soon as the led status is set (i.e. right after pluging it in) it
becomes completely unresponsive. If I comment out the led-setting code
in xpad.c the controller works but only until a rumble effect is
played, then it will become unresponsive again.

I have found that this does not occur if transfer_buffer_length is set
to the exact value, 3 for the led and 8 for rumble.

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: xpad-transferlength.patch --]
[-- Type: text/x-diff; name=xpad-transferlength.patch, Size: 528 bytes --]

--- a/xpad.c	2008-03-21 16:39:58.000000000 +0100
+++ b/xpad.c	2008-03-21 16:38:41.000000000 +0100
@@ -469,6 +469,7 @@
 		xpad->odata[5] = 0x00;
 		xpad->odata[6] = 0x00;
 		xpad->odata[7] = 0x00;
+		xpad->irq_out->transfer_buffer_length = 8;
 		usb_submit_urb(xpad->irq_out, GFP_KERNEL);
 	}
 
@@ -502,6 +503,7 @@
 		xpad->odata[0] = 0x01;
 		xpad->odata[1] = 0x03;
 		xpad->odata[2] = command;
+		xpad->irq_out->transfer_buffer_length = 3;
 		usb_submit_urb(xpad->irq_out, GFP_KERNEL);
 		mutex_unlock(&xpad->odata_mutex);
 	}

             reply	other threads:[~2008-03-21 17:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21 17:52 M G [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-22 12:26 xpad - led/rumble completely disables controller M G
2008-03-24 13:46 M G

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=74d457500803211052l1beada9by3a72a240a3602dfe@mail.gmail.com \
    --to=lists.mg@googlemail.com \
    --cc=linux-input@vger.kernel.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).