linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chih-Wei Huang <cwhuang@android-x86.org>
To: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
	Jiri Kosina <jkosina@suse.cz>,
	linux-input@vger.kernel.org
Subject: Re: ET1602 Touchscreen doesn't work
Date: Fri, 10 Jun 2011 10:23:06 +0800	[thread overview]
Message-ID: <BANLkTinnGiu_qWnCTq-1peyEw4=xUdnAkw@mail.gmail.com> (raw)
In-Reply-To: <20110609133943.GA2439@nautilus.holoscopio.com>

2011/6/9 Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>:
> Nice. That was one of the tests. But have you tested without the quirck
> in hid-quirks and without the suggested change by Benjamin? Considering
> the device would indicate it supports RX and Z axis, but not X and Y
> axis, it should not work either in Android.

Did you mean just remove this line in hid-quirks.c?

{ USB_VENDOR_ID_TOUCHPACK, USB_DEVICE_ID_TOUCHPACK_RTS, HID_QUIRK_MULTI_INPUT },

That's what I've tried (with and without Benjamin's change) .
Yes, it works in Android 2.2.

-- 
Chih-Wei
Android-x86 project
http://www.android-x86.org

  reply	other threads:[~2011-06-10  2:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTikX9njth-jP6PpQuwL9sTUciu1nQA@mail.gmail.com>
2011-06-02 14:41 ` ET1602 Touchscreen doesn't work Thadeu Lima de Souza Cascardo
2011-06-03  4:02   ` Chih-Wei Huang
2011-06-03 12:44     ` Thadeu Lima de Souza Cascardo
2011-06-08 10:33       ` Chih-Wei Huang
2011-06-08 11:31         ` Benjamin Tissoires
2011-06-08 12:57           ` Thadeu Lima de Souza Cascardo
2011-06-08 14:56             ` Chih-Wei Huang
2011-06-08 15:31               ` Thadeu Lima de Souza Cascardo
2011-06-09 11:26                 ` Chih-Wei Huang
2011-06-09 13:39                   ` Thadeu Lima de Souza Cascardo
2011-06-10  2:23                     ` Chih-Wei Huang [this message]
2011-06-13 15:09                       ` Thadeu Lima de Souza Cascardo

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='BANLkTinnGiu_qWnCTq-1peyEw4=xUdnAkw@mail.gmail.com' \
    --to=cwhuang@android-x86.org \
    --cc=benjamin.tissoires@gmail.com \
    --cc=cascardo@holoscopio.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).