linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sebastian Dalfuß" <sd@sedf.de>
To: linux-input@vger.kernel.org
Subject: hid: egalax 0x0eef:0x0001 no longer detected by hid-multitouch
Date: Fri, 30 Aug 2013 19:59:46 +0200	[thread overview]
Message-ID: <20130830175946.GA17584@sedf.de> (raw)

Dear Maintainers,

In 3.6.x the egalax touch panel (Vendor: 0eef, Dev: 0001) worked 
perfectly well with hid-multitouch, right out of the box. In 3.9 and 
3.10 it doesn't; the panel doesn't show up in /proc/bus/input/devices .
If the module usbtouchscreen is present, 3.9/3.10 wrongly try to use 
that one (flipped y-axis, wrong scale, get's stuck) instead of 
hid-multitouch(worked previously perfectly well, no need for 
calibration, quirks, configuration). If usbtouchscreen isn't present, 
the panel isn't detected, even if hid-multitouch gets poked with appropriate
parameters in /sys/module/hid_multitouch/drivers/hid\:hid-multitouch/new_id .
In an desperate attempt, I manually added the device/vendor id to
hid-multitouch.c, which didn't yield any improvement. It seems that the hid
subsystem doesn't even recognize that this device is indeed a hid 
touchpanel.

Is there a way to force hid to take care of that vendor/device-id, as a
temporary workaround?

This issue is also filed in Bugzilla: 
https://bugzilla.kernel.org/show_bug.cgi?id=60816

lsusb-snippet:
https://bugzilla.kernel.org/attachment.cgi?id=107362

Greetings,
Sebastian Dalfuß
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2013-08-30 18:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 17:59 Sebastian Dalfuß [this message]
2013-08-30 18:45 ` hid: egalax 0x0eef:0x0001 no longer detected by hid-multitouch Forest Bond
2013-08-30 23:23   ` Sebastian Dalfuß

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=20130830175946.GA17584@sedf.de \
    --to=sd@sedf.de \
    --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).