Re: joydev.c and saitek cyborg evo force

[Jiri Kosina]

On Tue, 12 Jun 2007, Renato Golin wrote:

> At joydev_connect, the last parameter "input_dev" reports me that range 
> (dev->absmax[i] and dev->absmin[i]). When I turned on HID_DEBUG it 
> reported [0, 4096] for both axis 0 and 1, which is correct so it must be 
> between HID and joydev.

Renato,

could you please apply the stupid patch below (against 2.6.20, I know you 
are using it :) ) and report the result? It should show us whether the 
values 0 and 4096 (which can be seen in your hid parsing debug dump) are 
correctly passed from HID to input, or they are garbled inside the hid 
layer somewhere already.

Thanks.

diff --git a/drivers/hid/hid-input.c b/drivers/hid/hid-input.c
index c7a6833..9dea1e8 100644
--- a/drivers/hid/hid-input.c
+++ b/drivers/hid/hid-input.c
@@ -665,9 +665,16 @@ static void hidinput_configure_usage(str
 			b = field->logical_maximum = 255;
 		}
 
-		if (field->application == HID_GD_GAMEPAD || field->application == HID_GD_JOYSTICK)
+		if (field->application == HID_GD_GAMEPAD || field->application == HID_GD_JOYSTICK) {
+			printk(KERN_DEBUG "calling input_set_abs_params, code: %x, min: %x, max: %x, fuzz: %x, flat: %x\n", 
+					usage->code, a, b, (b - a) >> 8, (b - a) >> 4);
 			input_set_abs_params(input, usage->code, a, b, (b - a) >> 8, (b - a) >> 4);
-		else	input_set_abs_params(input, usage->code, a, b, 0, 0);
+		}
+		else {
+			printk(KERN_DEBUG "calling input_set_abs_params, code: %x, min: %x, max: %x, fuzz: %x, flat: %x\n", 
+					usage->code, a, b, (b - a) >> 8, (b - a) >> 4);
+			input_set_abs_params(input, usage->code, a, b, 0, 0);
+		}
 
 	}
 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/