linux-kernel - Re: joydev.c and saitek cyborg evo force

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0706201156410.23812@jikos.suse.cz>
Date:	Wed, 20 Jun 2007 12:00:03 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Renato Golin <rengolin@...il.com>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: joydev.c and saitek cyborg evo force

On Thu, 14 Jun 2007, Renato Golin wrote:

> Applied your patch and the log is below,
[...]
> [ 6973.596722] calling input_set_abs_params, code: 0, min: ffffff81,
> max: 7f, fuzz: 0, flat: f
> [ 6973.596724] Absolute.X
> [ 6973.596732] calling input_set_abs_params, code: 1, min: ffffff81,
> max: 7f, fuzz: 0, flat: f
> [ 6973.596735] Absolute.Y

Hi Renato,

this signalizes something is wrong between the device and HID layer - it 
could be both the report descriptor of the device being wrong, or some bug 
in hid-input that is not triggered by any other device.

Could you please send me the report descriptor of the device, so that I 
could debug it locally here?

The report descriptor should be present in your HID_DEBUG dump, but you 
don't seem to have provided in any of the previous mails. The relevant 
line in dmesg should look similar to:

report descriptor (size 61, read 54) = 05 0b 09 05 a1 01 05 09 19 11 29 18 
15 00 25 01 75 01 95 08 81 22 05 08 09 3a a1 02 05 09 19 11 29 17 15 00 25 
01 75 01 95 07 b1 a2 c0 06 ff ff 09 01 15 00 25 01 75 01 95 01 b1 22 c0

Thanks,

-- 
Jiri Kosina
SUSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/