o this at the start of pidff_upload_effect.
Signed-off-by: Jim Keir
---
drivers/hid/usbhid/hid-pidff.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/hid/usbhid/hid-pidff.c b/drivers/hid/usbhid/hid-pidff.c
index 0b531c6..1b3fa70 100644
--- a/drivers/hid/usbhid/hid-pidff.c
+++ b/dri
] at the end of
pid_upload_effect, for later use. However, if an effect is modified and
re-sent then this identifier is not being copied back from
pidff-pid_id[effect-id] before sending the command to the device. The
fix is to do this at the start of pidff_upload_effect.
Signed-off-by: Jim Keir jimk
o this at the start of pidff_upload_effect.
Signed-off-by: Jim Keir
drivers/hid/usbhid/hid-pidff.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/hid/usbhid/hid-pidff.c b/drivers/hid/usbhid/hid-pidff.c
index 0b531c6..1b3fa70 100644
--- a/drivers/hid/usbhid/hid-pidff.c
+++ b/dri
-id] at the end of
pid_upload_effect, for later use. However, if an effect is modified and
re-sent then this identifier is not being copied back from
pidff-pid_id[effect-id] before sending the command to the device. The
fix is to do this at the start of pidff_upload_effect.
Signed-off-by: Jim Keir
OK, I am pushing a little bit, I just don't want today to go deep in
the code :-)
On Fri, Jan 23, 2015 at 12:21 PM, Jim Keir wrote:
---
Hi,
Changes from previous patches:
- All changes removed from higher-level files
- Extra debug line removed
Signed-off-by: Jim Keir
drivers/hid/usbhid/hid
:-)
On Fri, Jan 23, 2015 at 12:21 PM, Jim Keir jimk...@oracledbadirect.com wrote:
---
Hi,
Changes from previous patches:
- All changes removed from higher-level files
- Extra debug line removed
Signed-off-by: Jim Keir jimk...@oracledbadirect.com
drivers/hid/usbhid/hid-pidff.c | 6 ++
1 file
---
Hi,
Changes from previous patches:
- All changes removed from higher-level files
- Calls to hid_device_io_start/stop added here
Signed-off-by: Jim Keir
drivers/hid/usbhid/hid-pidff.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/hid/usbhid/hid-pidff.c b/drivers/hid
---
Hi,
Changes from previous patches:
- All changes removed from higher-level files
- Extra debug line removed
Signed-off-by: Jim Keir
drivers/hid/usbhid/hid-pidff.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/hid/usbhid/hid-pidff.c b/drivers/hid/usbhid/hid-pidff.c
---
Hi,
Changes from previous patches:
- All changes removed from higher-level files
- Extra debug line removed
Signed-off-by: Jim Keir jimk...@oracledbadirect.com
drivers/hid/usbhid/hid-pidff.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/hid/usbhid/hid-pidff.c b
---
Hi,
Changes from previous patches:
- All changes removed from higher-level files
- Calls to hid_device_io_start/stop added here
Signed-off-by: Jim Keir jimk...@oracledbadirect.com
drivers/hid/usbhid/hid-pidff.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/hid/usbhid
was using before. Apologies for the mistakes, I'm still feeling my way
around here.
---
Allow the Microsoft Sidewinder Force Feedback 2 joystick to perform the
required communication with the device during initialisation.
Signed-off-by: Jim Keir
---
diff --git a/drivers/hid/usbhid/hid
Hi,
Here's the second part of the patch which allows existing effects to be
modified.
Cheers,
Jim
---
Modifications to existing force effects in the Microsoft Sidewinder
Force Feedback 2 joystick are sent with the correct effect ID.
Signed-off-by: Jim Keir
---
diff --git a/drivers/hid
was using before. Apologies for the mistakes, I'm still feeling my way
around here.
---
Allow the Microsoft Sidewinder Force Feedback 2 joystick to perform the
required communication with the device during initialisation.
Signed-off-by: Jim Keir jimk...@oracledbadirect.com
---
diff --git
Hi,
Here's the second part of the patch which allows existing effects to be
modified.
Cheers,
Jim
---
Modifications to existing force effects in the Microsoft Sidewinder
Force Feedback 2 joystick are sent with the correct effect ID.
Signed-off-by: Jim Keir jimk...@oracledbadirect.com
From: Jim Keir
Signed-off-by: Jim Keir
Currently the SWFF2 driver fails during initialisation, making the force
capability of the joystick unusable. Further, there is a long-standing
bug in the same driver where commands to update force parameters are
addressed to the last-created force effect
From: Jim Keir jimk...@yahoo.co.uk
Signed-off-by: Jim Keir jimk...@yahoo.co.uk
Currently the SWFF2 driver fails during initialisation, making the force
capability of the joystick unusable. Further, there is a long-standing
bug in the same driver where commands to update force parameters
16 matches
Mail list logo
