[Kernel-packages] [Bug 1035723] Re: Joystick (SideWinder FF2) Force Feedback doesn't reset properly

2015-01-17 Thread Christopher M. Penalver
Jim Keir, as per http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS you would want to redirect your patch upstream to the linux-input mailing list, CC Jiri Kosina. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed

[Kernel-packages] [Bug 1035723] Re: Joystick (SideWinder FF2) Force Feedback doesn't reset properly

2015-01-16 Thread Jim Keir
Proposed patch to get the Microsoft Sidewinder Force Feedback 2 working. Three bugs are addressed: 1) The FF2 driver (usbhid/hid-pidff.c) sends commands to the stick during ff_init. However, this is called inside a block where driver_input_lock is locked, so the results of these initial commands

[Kernel-packages] [Bug 1035723] Re: Joystick (SideWinder FF2) Force Feedback doesn't reset properly

2014-11-16 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1035723] Re: Joystick (SideWinder FF2) Force Feedback doesn't reset properly

2014-09-17 Thread Christopher M. Penalver
Martin Becker, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read

[Kernel-packages] [Bug 1035723] Re: Joystick (SideWinder FF2) Force Feedback doesn't reset properly

2014-09-16 Thread Martin Becker
** Changed in: linux (Ubuntu) Status: Expired = New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1035723 Title: Joystick (SideWinder FF2) Force Feedback doesn't reset properly

[Kernel-packages] [Bug 1035723] Re: Joystick (SideWinder FF2) Force Feedback doesn't reset properly

2014-09-16 Thread Martin Becker
In kernel 3.13.0 I still have the same issues. So I also did some debugging. Major findings: - in hid-core.c the function usbhid_parse() is called after the joystick is attached - usbhid_parse() calls function hid_set_idle(), and this one fails while sending an URB (details see below). Reason:

[Kernel-packages] [Bug 1035723] Re: Joystick (SideWinder FF2) Force Feedback doesn't reset properly

2014-09-16 Thread Martin Becker
Wireshark capture of EPIPE ** Attachment added: wireshark trace https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1035723/+attachment/4205605/+files/sidewinder2.pcap.pcapng -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1035723] Re: Joystick (SideWinder FF2) Force Feedback doesn't reset properly

2014-09-16 Thread Martin Becker
Just found out, that it is an upstream bug. The force feedback works in 2.6.38-12. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1035723 Title: Joystick (SideWinder FF2) Force Feedback

[Kernel-packages] [Bug 1035723] Re: Joystick (SideWinder FF2) Force Feedback doesn't reset properly

2013-10-10 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1035723] Re: Joystick (SideWinder FF2) Force Feedback doesn't reset properly

2013-08-11 Thread Christopher M. Penalver
bra1nDeaD, as per http://www.dell.com/support/troubleshooting/us/en/19/Product/optiplex-755 an update is available for your BIOS (A22). If you update to this, does it change anything? If not, could you please both specify what happened, and provide the output of the following terminal command: