From: Ondrej Zary <linux@rainbow-software.org>
To: Oliver Neukum <oneukum@suse.de>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
Daniel Ritz <daniel.ritz@gmx.ch>
Subject: Re: [0000/0003]full power management for usb touchscreens
Date: Tue, 29 Jun 2010 15:51:11 +0200 [thread overview]
Message-ID: <201006291551.13148.linux@rainbow-software.org> (raw)
In-Reply-To: <201006240856.16402.oneukum@suse.de>
On Thursday 24 June 2010, Oliver Neukum wrote:
> Am Dienstag, 22. Juni 2010, 15:43:24 schrieb Ondrej Zary:
> > On Tuesday 22 June 2010, Oliver Neukum wrote:
> > > This is a violation of the spec. Can you give me the IDs so that I can
> > > put the devices into the quirks file? Or can I take this from the
> > > driver? Do all devices that marked as always needing an irq transfer
> > > behave this way?
> >
> > This is not a bug surprise as this device is broken in many ways. It
> > takes ages to detect and identify and looks like cdc_acm. The
> > pseudo-multitouch capable protocol is pretty bad too. Also there are some
> > reports about devices using the same ID but different protocol.
> >
> > I have only one - 1870:0001, don't know anything about the other.
>
> OK, it seems like those devices are hopeless. Could you test this series
> form harmlessness on a broken device and functionality on a non-broken
> device?
Tested with:
0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen
595a:0001 IRTOUCHSYSTEMS Co. Ltd. Touchscreen
1870:0001 Nexio Co., Ltd iNexio Touchscreen controller
The patches have no visible effect on these devices so they're probably OK.
--
Ondrej Zary
prev parent reply other threads:[~2010-06-29 13:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 13:13 [0000/0003]full power management for usb touchscreens Oliver Neukum
[not found] ` <201006071513.29478.oneukum-l3A5Bk7waGM@public.gmane.org>
2010-06-07 16:19 ` Dmitry Torokhov
[not found] ` <20100607161920.GA7706-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2010-06-08 12:49 ` Ondrej Zary
2010-06-09 13:40 ` Ondrej Zary
2010-06-09 16:36 ` Oliver Neukum
[not found] ` <201006091836.14136.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2010-06-10 11:33 ` Ondrej Zary
2010-06-10 13:46 ` Oliver Neukum
[not found] ` <201006101546.55460.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2010-06-10 14:13 ` Ondrej Zary
[not found] ` <201006101613.52736.linux-ZCIryABCsrmttCpgsWEBFmD2FQJk+8+b@public.gmane.org>
2010-06-10 14:25 ` Oliver Neukum
2010-06-18 18:22 ` Oliver Neukum
2010-06-18 18:34 ` Ondrej Zary
[not found] ` <201006182034.05793.linux-ZCIryABCsrmttCpgsWEBFmD2FQJk+8+b@public.gmane.org>
2010-06-18 18:41 ` Oliver Neukum
2010-06-22 11:06 ` Ondrej Zary
2010-06-22 13:24 ` Oliver Neukum
[not found] ` <201006221524.25084.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2010-06-22 13:43 ` Ondrej Zary
[not found] ` <201006221543.27169.linux-ZCIryABCsrmttCpgsWEBFmD2FQJk+8+b@public.gmane.org>
2010-06-24 6:56 ` Oliver Neukum
2010-06-29 13:51 ` Ondrej Zary [this message]
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=201006291551.13148.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=daniel.ritz@gmx.ch \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).