multi-touch-dev team mailing list archive

[Duncan McGreggor <duncan.mcgreggor@xxxxxxxxxxxxx>]

Hey Ara,

Marc's script looks nice, but I was waiting to get a resolution to the
shell script/device/kernel issue before making some suggestions. Looks
like the script you attached is an updated version that cleverly works
around the issue.

Running the script no longer results in a traceback; I get results now.
However, not all the results I expected. My expectations may be awry due
to not knowing what the script outputs for other N-trig-based hardware.

Here's what I get:

Found device(s):
SynPS/2 Synaptics TouchPad: /dev/input/event6
N-Trig Pen: /dev/input/event9

Here's what I would expect (Henrik can correct my assumptions):

Found device(s):
SynPS/2 Synaptics TouchPad: /dev/input/event6
N-Trig Pen: /dev/input/event9
N-Trig MultiTouch: /dev/input/event10
N-Trig Touchscreen: /dev/input/event11

Thanks!

d

On 08/18/2010 04:32 AM, Ara Pulido wrote:
> Marc Tardif was kind enough to write the script in Python (which will
> make integration with apport much easier).
> 
> Can you guys try it with your hardware, please?
> 
> Thanks!
> Ara.
> 
> El 18/08/10 07:48, Rafi Rubin escribió:
>> Not present on 2.6.35-{14,15,16} for x86_64 on my xt.
>>
>> $ cat /sys/class/input/event*/dev*/cap*/abs                     ~  1:14AM 
>> holly
>> 0
>> 0
>> 0
>> 0
>> 0
>> 0
>> 1000003
>> 73010000000003
>> 30000000003
>> 0
>> 0
>> 0
>> $ uname -a                                                      ~  1:15AM 
>> holly
>> Linux holly 2.6.35-15-generic #21-Ubuntu SMP Wed Aug 11 17:06:48 UTC 2010 
>> x86_64 GNU/Linux
>>
>>
>> I will start a 32b image download and will have to figure out a way to 
>> test multiple kernels.  I guess I can blow away swap or something for 
>> another install.
>>
>> Nothing terribly obvious in the delta of the source for -13 -> -15 
>> (assuming I grabbed the correct git tree).
>>
>> Anyway the functions in questions are input_bits_to_string 
>> (input.c:814ish) and input_print_bitmap (1218) or maybe 
>> input_seq_print_bitmap.
>>
>> Anyway should be easy enough to figure out, and we probably should do to 
>> increase consistency.  However, it might also make sense to adjust the 
>> script to account for buggy kernels which might not get fixed before 
>> people start testing and asking questions.
>>
>> Rafi
>>
>> On Wed, Aug 18, 2010 at 12:58:20AM +0200, Mohamed Ikbel Boulabiar wrote:
>>> I have exactly the same cat output and the same kernel as Duncan with my hp tx2.
>>>
>>> ik.
>>>
>>> On Wed, Aug 18, 2010 at 12:56 AM, Duncan McGreggor
>>> <duncan.mcgreggor@xxxxxxxxxxxxx> wrote:
>>>>>> Henrik and Rafi,
>>>>>>
>>>>>> I've tried to use this script with the Lenovo T410s, and it fails. It
>>>>>> seems that the following N-trig device returns two integers instead of
>>>>>> the expected one integer:
>>>>>>
>>>>>> ? ?/sys/class/input/event10/device/capabilities/abs
>>>>>>
>>>>>> cat'ing it gives the following:
>>>>>>
>>>>>> ? ?730100 3
>>>>>
>>>>> That is a bit strange. ?What kernel version were you using at the time
>>>>> and do you have another kernel version installed?
>>>>>
>>>>> (wondering if its just a broken sprintf)
>>>>
>>>> ?$ uname -a
>>>> ?Linux bree 2.6.35-15-generic #21-Ubuntu SMP Wed Aug 11 16:41:40 UTC
>>>> 2010 i686 GNU/Linux
>>>