All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Getting a functional driver for Mad Catz Fightstick TE 2 (Xbox One version)
Date: Tue, 8 Mar 2016 11:35:26 -0800	[thread overview]
Message-ID: <20160308193526.GA27477@kroah.com> (raw)
In-Reply-To: <20160308191526.rzi6oq4sfsbm4h62@myarchbang>

On Tue, Mar 08, 2016 at 08:15:26PM +0100, Silvan Jegen wrote:
> Heyho
> 
> I bought a Mad Catz Fightstick TE2 for Xbox One because I wanted to play
> some fighting games on Linux. I chose this stick because it has gotten good
> reviews and I assumed that the Kernel driver should work because there are
> already drivers for Xbox One controllers in drivers/input/joystick/xpad.c.
> 
> It turns out that the driver does not work and dmesg just shows
> 
> [12293.077720] usb 1-1.2.1: new full-speed USB device number 9 using ehci-pci
> 
> when plugging it in. Simply adding the line
> 
> { 0x0738, 0x4a01, "Mad Catz FightStick TE 2", 0, XTYPE_XBOXONE },
> 
> (where the two Hex values are VENDOR_ID and PRODUCT_ID) to xpad_device[]
> in xpad.c does not help either (which I naively hoped it would).

Try asking this on the linux-input at vger.kernel.org mailing list, the
developers there should be able to help you out better than this one
can.

good luck,

greg k-h

  reply	other threads:[~2016-03-08 19:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 19:15 Getting a functional driver for Mad Catz Fightstick TE 2 (Xbox One version) Silvan Jegen
2016-03-08 19:35 ` Greg KH [this message]
2016-03-08 21:40   ` Silvan Jegen
  -- strict thread matches above, loose matches on Subject: below --
2016-03-08 21:45 Silvan Jegen
2016-03-09 11:43 ` Gregor Riepl
2016-03-10  8:48   ` Silvan Jegen

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=20160308193526.GA27477@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.