[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freedesktop-xorg
Subject:    Re: Avago Technologies touchscreen problems
From:       Erik de Castro Lopo <mle+xorg () mega-nerd ! com>
Date:       2010-06-24 1:51:28
Message-ID: 20100624115128.3da157c7.mle+xorg () mega-nerd ! com
[Download RAW message or body]

Peter Hutterer wrote:

> judging by the log it doesn't export absolute axes which seems rather odd
> for a touchscreen. so I suspect a kernel driver issue.

If its a kernel issue any idea about which specific mailing list
or person to contact?

> what does the evtest output for the device show?

Since Xorg reported this:

  (II) config/udev: Adding input device AVAGO TECHNOLOGIES AVAGO USB OFN Device \
(/dev/input/event3)  (**) AVAGO TECHNOLOGIES AVAGO USB OFN Device: Applying \
InputClass "evdev pointer catchall"  (**) AVAGO TECHNOLOGIES AVAGO USB OFN Device: \
Applying InputClass "evdev keyboard catchall"  (**) AVAGO TECHNOLOGIES AVAGO USB OFN \
Device: always reports core events  (**) AVAGO TECHNOLOGIES AVAGO USB OFN Device: \
Device: "/dev/input/event3"  (II) AVAGO TECHNOLOGIES AVAGO USB OFN Device: Found 3 \
mouse buttons  (II) AVAGO TECHNOLOGIES AVAGO USB OFN Device: Found scroll wheel(s)
  (II) AVAGO TECHNOLOGIES AVAGO USB OFN Device: Found relative axes
  (II) AVAGO TECHNOLOGIES AVAGO USB OFN Device: Found x and y relative axes
  (II) AVAGO TECHNOLOGIES AVAGO USB OFN Device: Found keys
  (II) AVAGO TECHNOLOGIES AVAGO USB OFN Device: Configuring as mouse
  (II) AVAGO TECHNOLOGIES AVAGO USB OFN Device: Configuring as keyboard
  (**) AVAGO TECHNOLOGIES AVAGO USB OFN Device: YAxisMapping: buttons 4 and 5
  (**) AVAGO TECHNOLOGIES AVAGO USB OFN Device: EmulateWheelButton: 4, \
EmulateWheelInertia: 10, EmulateWheelTimeout: 200  (II) XINPUT: Adding extended input \
device "AVAGO TECHNOLOGIES AVAGO USB OFN Device" (type: KEYBOARD)  (**) Option \
"xkb_rules" "evdev"  (**) Option "xkb_model" "pc105"
  (**) Option "xkb_layout" "us"
  (II) AVAGO TECHNOLOGIES AVAGO USB OFN Device: initialized for relative axes.
  (II) config/udev: Adding input device AVAGO TECHNOLOGIES AVAGO USB OFN Device \
(/dev/input/mouse0)  (II) No input driver/identifier specified (ignoring)

Is that last line significant?

I ran "evtest /dev/input/event3" which output this:

  Input driver version is 1.0.0
  Input device ID: bus 0x3 vendor 0x192f product 0x0 version 0x101
  Input device name: "AVAGO TECHNOLOGIES AVAGO USB OFN Device"
  Supported events:
    Event type 0 (Sync)
    Event type 1 (Key)
      Event code 1 (Esc)
      Event code 2 (1)
      Event code 3 (2)
      Event code 4 (3)
      Event code 5 (4)
      Event code 6 (5)
      Event code 7 (6)
      Event code 8 (7)
      Event code 9 (8)
      Event code 10 (9)
      Event code 11 (0)
      Event code 12 (Minus)
  
      ....
  
  
      Event code 108 (Down)
      Event code 109 (PageDown)
      Event code 110 (Insert)
      Event code 111 (Delete)
      Event code 119 (Pause)
      Event code 125 (LeftMeta)
      Event code 126 (RightMeta)
      Event code 127 (Compose)
      Event code 272 (LeftBtn)
      Event code 273 (RightBtn)
      Event code 274 (MiddleBtn)
    Event type 2 (Relative)
      Event code 0 (X)
      Event code 1 (Y)
      Event code 8 (Wheel)
    Event type 4 (Misc)
      Event code 4 (ScanCode)
    Event type 17 (LED)
      Event code 0 (NumLock)
      Event code 1 (CapsLock)
      Event code 2 (ScrollLock)
      Event code 3 (Compose)
      Event code 4 (Kana)
    Event type 20 (Repeat)


Yes, relative X/Y in the mouse section about is suspicious.

Erik
-- 
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/
_______________________________________________
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: freedesktop-xorg@progressive-comp.com


[prev in list] [next in list] [prev in thread] [next in thread]