From: Alex Custov <alex.custov@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: touchscreen wirh 2.6.26
Date: Fri, 27 Nov 2009 19:36:06 +0200 [thread overview]
Message-ID: <39840bc80911270936n2cb568e6wd33a376ab59a6e62@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.00.0911271308270.6953@wotan.suse.de>
2009/11/27 Jiri Kosina <jkosina@suse.cz>:
> On Fri, 27 Nov 2009, Alex Custov wrote:
>
>> >> I have Acer T230H on Debian Lenny with 2.6.26.8 manually complied
>> >> kernel. The problem is that this is a multitouch monitor and it seems
>> >> that it doesn't work at all (even single touches). All things under
>> >> "Drivers => Input device support => Touchscreens" are enabled in kernel
>> >> (as modules). Is this type of monitor supported, or I should upgrade to
>> >> a newer kernel? Thanks.
>> >
>> > How is the touchscreen conntected to system? Is it USB? If so, what is the
>> > vendor and product ID? (lsusb will tell).
>>
>> Hi. Thanks for answer. I've already found the /dev device it has - it
>> is /dev/usb/hiddev0. Yes, it is USB connected. I did "cat
>> /dev/usb/hiddev0" and touched some points on the screen, it seems that
>> it works (I got some binary data from 'cat'). Now I will try to add
>> the corresponding section to the xorg.conf to let it work in X.
>
> It might not be that trivial -- /dev/usb/hiddev0 gives you only
> more-or-less raw HID data, but they have still to be interpreted somehow
> to make sense.
>
> If the device is implementing some vendor-specific (or device-specific)
> protocol, then the data you see coming through hiddev0 might not be useful
> at all directly in X.
>
> Repeating from my previous mail -- please provide the idVendor/idProduct
> (found by lsusb -v) for this device. It might be supported in later
> kernels, but without this information, it's impossible to tell.
>
> --
> Jiri Kosina
> SUSE Labs, Novell Inc.
>
Here you are:
Bus 004 Device 002: ID 0408:3000 Quanta Computer, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0408 Quanta Computer, Inc.
idProduct 0x3000
bcdDevice 0.00
iManufacturer 1 Acer
iProduct 2 T230H
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 210
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 8
Device Status: 0x0000
(Bus Powered)
--
next prev parent reply other threads:[~2009-11-27 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 3:57 Alex Custov
2009-11-27 10:59 ` Jiri Kosina
2009-11-27 12:03 ` Alex Custov
2009-11-27 12:10 ` Jiri Kosina
2009-11-27 17:36 ` Alex Custov [this message]
2009-11-27 23:30 ` Jiri Kosina
2009-12-09 21:21 ` Tamási János
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39840bc80911270936n2cb568e6wd33a376ab59a6e62@mail.gmail.com \
--to=alex.custov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®