Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux: Kernel

touchscreen wirh 2.6.26

 

 

Linux kernel RSS feed   Index | Next | Previous | View Threaded


alex.custov at gmail

Nov 24, 2009, 7:57 PM

Post #1 of 7 (615 views)
Permalink
touchscreen wirh 2.6.26

Hello.

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.

Please CC any comments.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


jkosina at suse

Nov 27, 2009, 2:59 AM

Post #2 of 7 (586 views)
Permalink
Re: touchscreen wirh 2.6.26 [In reply to]

On Wed, 25 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).

--
Jiri Kosina
SUSE Labs, Novell Inc.

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


alex.custov at gmail

Nov 27, 2009, 4:03 AM

Post #3 of 7 (586 views)
Permalink
Re: touchscreen wirh 2.6.26 [In reply to]

2009/11/27 Jiri Kosina <jkosina [at] suse>:
> On Wed, 25 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).
>
> --
> Jiri Kosina
> SUSE Labs, Novell Inc.
>
>

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.

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


jkosina at suse

Nov 27, 2009, 4:10 AM

Post #4 of 7 (584 views)
Permalink
Re: touchscreen wirh 2.6.26 [In reply to]

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo [at] vger
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/


alex.custov at gmail

Nov 27, 2009, 9:36 AM

Post #5 of 7 (581 views)
Permalink
Re: touchscreen wirh 2.6.26 [In reply to]

2009/11/27 Jiri Kosina <jkosina [at] suse>:
> 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)

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


jkosina at suse

Nov 27, 2009, 3:30 PM

Post #6 of 7 (581 views)
Permalink
Re: touchscreen wirh 2.6.26 [In reply to]

On Fri, 27 Nov 2009, Alex Custov wrote:

> 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

Unfortunately, this touchscreen is not (yet) neither supported by
usbtouchscreen kernel driver, nor is it apparently HID standard compliant,
so HID driver can't do much with it as well.

You will have to reverse-engineer the data protocol the touchscreen is
sending. It's usually quite easy, in cases in which the device doesn't
require complex initialization before it can become functional.

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


janusz at uhulinux

Dec 9, 2009, 1:21 PM

Post #7 of 7 (541 views)
Permalink
Re: touchscreen wirh 2.6.26 [In reply to]

Hi!

I wrote a small (and really ugly) uinput driver to this device. I hope
this helps somebody to write a proper driver for this touchscreen.


2009-11-28 00:30 keltezéssel, Jiri Kosina írta:
> On Fri, 27 Nov 2009, Alex Custov wrote:
>
>
>> 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
>>
> Unfortunately, this touchscreen is not (yet) neither supported by
> usbtouchscreen kernel driver, nor is it apparently HID standard compliant,
> so HID driver can't do much with it as well.
>
> You will have to reverse-engineer the data protocol the touchscreen is
> sending. It's usually quite easy, in cases in which the device doesn't
> require complex initialization before it can become functional.
>
>
Attachments: acer-t230H.c (3.52 KB)

Linux kernel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.