You'll only get them for devices handled by HID drivers. On my
tablet, thats only 1 touchscreen. I was in fact assuming you only
have 1 HID device.
The other one is my bluetooth keyboard.
Can you retry this and do the exact filename? Also, you will need to
cat the rdesc
On Thu, Nov 17, 2011 at 06:26:04PM -0600, Chris Bagwell wrote:
On Thu, Nov 17, 2011 at 3:54 AM, Cedric Sodhi man...@gmx.net wrote:
I updated to GIT and it appears that the wacom now works both, clicks
and absolute mode correctly. On the other hand, the precedence does not
(any
Hello, do you have an idea how to decrease the sensitivity? Currently, a
touch is already registered before I even touch the screen.
--
All the data continuously generated in your IT infrastructure
contains a definitive
On Fri, Nov 18, 2011 at 2:28 AM, Cedric Sodhi man...@gmx.net wrote:
On Thu, Nov 17, 2011 at 06:26:04PM -0600, Chris Bagwell wrote:
On Thu, Nov 17, 2011 at 3:54 AM, Cedric Sodhi man...@gmx.net wrote:
I updated to GIT and it appears that the wacom now works both, clicks
and absolute mode
On Fri, Nov 18, 2011 at 8:22 AM, Cedric Sodhi man...@gmx.net wrote:
Hello, do you have an idea how to decrease the sensitivity? Currently, a
touch is already registered before I even touch the screen.
Are you talking finger touch or stylus touch?
For finger touch, this is a common issue with
On Fri, Nov 18, 2011 at 08:58:29AM -0600, Chris Bagwell wrote:
On Fri, Nov 18, 2011 at 8:22 AM, Cedric Sodhi man...@gmx.net wrote:
Hello, do you have an idea how to decrease the sensitivity? Currently, a
touch is already registered before I even touch the screen.
Are you talking finger
On Thu, Nov 17, 2011 at 08:37:05AM +0100, Cedric Sodhi wrote:
On Thu, Nov 17, 2011 at 08:30:32AM +0100, Cedric Sodhi wrote:
I've got even further good news to report. Although they kind of
question the relation between xinput and xsetwacom again. That is:
I said that the eGalax, if using
On Thu, Nov 17, 2011 at 10:01:11AM +0100, Cedric Sodhi wrote:
On Thu, Nov 17, 2011 at 09:01:07AM +0100, Cedric Sodhi wrote:
On Thu, Nov 17, 2011 at 08:37:05AM +0100, Cedric Sodhi wrote:
On Thu, Nov 17, 2011 at 08:30:32AM +0100, Cedric Sodhi wrote:
I've got even further good news to
On Thu, Nov 17, 2011 at 10:10:49AM +0100, Cedric Sodhi wrote:
On Thu, Nov 17, 2011 at 10:01:11AM +0100, Cedric Sodhi wrote:
On Thu, Nov 17, 2011 at 09:01:07AM +0100, Cedric Sodhi wrote:
On Thu, Nov 17, 2011 at 08:37:05AM +0100, Cedric Sodhi wrote:
On Thu, Nov 17, 2011 at 08:30:32AM
On Thu, Nov 17, 2011 at 3:54 AM, Cedric Sodhi man...@gmx.net wrote:
I updated to GIT and it appears that the wacom now works both, clicks
and absolute mode correctly. On the other hand, the precedence does not
(any longer?) work.
I've attached a patch which I think solves the problem.
On Wed, Nov 16, 2011 at 11:38 AM, Cedric Sodhi man...@gmx.net wrote:
Hello, I can report quite a bit of good news now:
One: Cleanly applying the required quirks and not blindly copying those
of the other DWAV devices as I did it when adding the ID to hid-ids.h
solves the jamming of the clicks
Hello, I can report quite a bit of good news now:
One: Cleanly applying the required quirks and not blindly copying those
of the other DWAV devices as I did it when adding the ID to hid-ids.h
solves the jamming of the clicks and results in a perfectly well working
device, with evdev, that is.
I've got even further good news to report. Although they kind of
question the relation between xinput and xsetwacom again. That is:
I said that the eGalax, if using the Wacom driver, behaves in Relative
Mode, although xsetwacom claims it was Absolute. Using xsetwacom could
not change this, but
On Thu, Nov 17, 2011 at 08:30:32AM +0100, Cedric Sodhi wrote:
I've got even further good news to report. Although they kind of
question the relation between xinput and xsetwacom again. That is:
I said that the eGalax, if using the Wacom driver, behaves in Relative
Mode, although xsetwacom
On Mon, Nov 14, 2011 at 12:22:54PM -0600, Chris Bagwell wrote:
On Mon, Nov 14, 2011 at 1:13 AM, Cedric Sodhi man...@gmx.net wrote:
On Sun, Nov 13, 2011 at 05:11:46PM -0600, Chris Bagwell wrote:
I also find using the kernel hid debug features useful in
understanding whats going on:
On Tue, Nov 15, 2011 at 1:33 PM, Cedric Sodhi man...@gmx.net wrote:
You'll only get them for devices handled by HID drivers. On my
tablet, thats only 1 touchscreen. I was in fact assuming you only
have 1 HID device.
The other one is my bluetooth keyboard.
Can you retry this
On Mon, Nov 14, 2011 at 1:13 AM, Cedric Sodhi man...@gmx.net wrote:
On Sun, Nov 13, 2011 at 05:11:46PM -0600, Chris Bagwell wrote:
I also find using the kernel hid debug features useful in
understanding whats going on:
sudo cat /sys/kernel/debug/hid/*/events
I don't get any output
On Sat, Nov 12, 2011 at 9:42 AM, Cedric Sodhi man...@gmx.net wrote:
Chris, I just compiled from Torvalds' HEAD (adding MULTITOUCH5 as usual)
and the clicking still jams.
Hmm, I just tried that version and its working with my touchscreen (I
got it back). I forget, what X input driver are you
On Sun, Nov 13, 2011 at 09:21:20AM -0600, Chris Bagwell wrote:
On Sat, Nov 12, 2011 at 9:42 AM, Cedric Sodhi man...@gmx.net wrote:
Chris, I just compiled from Torvalds' HEAD (adding MULTITOUCH5 as usual)
and the clicking still jams.
Hmm, I just tried that version and its working with my
On Sun, Nov 13, 2011 at 10:16 AM, Cedric Sodhi man...@gmx.net wrote:
On Sun, Nov 13, 2011 at 09:21:20AM -0600, Chris Bagwell wrote:
On Sat, Nov 12, 2011 at 9:42 AM, Cedric Sodhi man...@gmx.net wrote:
Chris, I just compiled from Torvalds' HEAD (adding MULTITOUCH5 as usual)
and the clicking
On Sun, Nov 13, 2011 at 05:11:46PM -0600, Chris Bagwell wrote:
On Sun, Nov 13, 2011 at 10:16 AM, Cedric Sodhi man...@gmx.net wrote:
On Sun, Nov 13, 2011 at 09:21:20AM -0600, Chris Bagwell wrote:
On Sat, Nov 12, 2011 at 9:42 AM, Cedric Sodhi man...@gmx.net wrote:
Chris, I just compiled from
An apology in advance for my poor conduct with the list. I don't know
how to properly reply to a thread of which I have no mails in my inbox,
so I just copied the threadtitle from the archives. Sorry if it ends up
creating a new thread.
Chris, I just compiled from Torvalds' HEAD (adding
On Tue, Nov 01, 2011 at 01:01:22PM -0500, Chris Bagwell wrote:
On Tue, Nov 1, 2011 at 12:44 PM, Cedric Sodhi man...@gmx.net wrote:
Hello,
unfortunally, I still have trouble with the touchpad. Clicking it
doesn't appear to work correctly. I think this is a bug on the kernel
side
Hello,
unfortunally, I still have trouble with the touchpad. Clicking it
doesn't appear to work correctly. I think this is a bug on the kernel
side (hid-multitouch) of things because it doesn't work in GPM either.
In X11 it appears to be always clicked. From boot on and starting X:
Everything
On Tue, Nov 01, 2011 at 06:44:08PM +0100, Cedric Sodhi wrote:
Hello,
unfortunally, I still have trouble with the touchpad. Clicking it
doesn't appear to work correctly. I think this is a bug on the kernel
side (hid-multitouch) of things because it doesn't work in GPM either.
In X11 it
On Tue, Nov 1, 2011 at 12:44 PM, Cedric Sodhi man...@gmx.net wrote:
Hello,
unfortunally, I still have trouble with the touchpad. Clicking it
doesn't appear to work correctly. I think this is a bug on the kernel
side (hid-multitouch) of things because it doesn't work in GPM either.
In X11 it
On Fri, Oct 28, 2011 at 3:57 AM, Cedric Sodhi man...@gmx.net wrote:
On Thu, Oct 27, 2011 at 11:36:43AM -0500, Chris Bagwell wrote:
Linux tends to require white lists for supported touchscreens. So it
doesn't matter what drivers you compile it... its OK to compile them
ALL in and let whichever
On Fri, Oct 28, 2011 at 9:13 AM, Chris Bagwell ch...@cnpbagwell.com wrote:
On Fri, Oct 28, 2011 at 3:57 AM, Cedric Sodhi man...@gmx.net wrote:
On Thu, Oct 27, 2011 at 11:36:43AM -0500, Chris Bagwell wrote:
Linux tends to require white lists for supported touchscreens. So it
doesn't matter
Darn. I guess that would have been to easy. I've note added an ID
yet to hid-multitouch so I may have got it wrong. I'll see if I can
find more info.
OK, found out what I missed. When you have a driver that is
auto-grabbed by generic-usb then you need to add it to a generic-usb
On Fri, Oct 28, 2011 at 12:04 PM, Cedric Sodhi man...@gmx.net wrote:
Darn. I guess that would have been to easy. I've note added an ID
yet to hid-multitouch so I may have got it wrong. I'll see if I can
find more info.
OK, found out what I missed. When you have a driver that is
On Thu, Oct 27, 2011 at 11:14 AM, Favux ... favux...@gmail.com wrote:
Oh, and I forgot to mention then, at least on Ubuntu, you would be
able to use ginn for multi-touch like we do with the N-trigs having
their touch on evdev while their stylus is on wacom.
And to throw my two cents in...
I recently bought an ASUS EEE Slate which has a eGalax Touchpad and a
WACOM Digitizer (Stylus Erasor). I did not know that. I thought it was
all WACOM, now I'm faced with the prolem that I have no driver for the
eGalax touchpad, I hope you can help, since I don't know any other
people on the
On Thu, Oct 27, 2011 at 7:25 AM, Cedric Sodhi man...@gmx.net wrote:
I recently bought an ASUS EEE Slate which has a eGalax Touchpad and a
WACOM Digitizer (Stylus Erasor). I did not know that. I thought it was
all WACOM, now I'm faced with the prolem that I have no driver for the
eGalax
Thanks Chris for replying, I knew I could rely on you guys :)
On Thu, Oct 27, 2011 at 09:07:37AM -0500, Chris Bagwell wrote:
On Thu, Oct 27, 2011 at 7:25 AM, Cedric Sodhi man...@gmx.net wrote:
I recently bought an ASUS EEE Slate which has a eGalax Touchpad and a
WACOM Digitizer (Stylus
On Thu, Oct 27, 2011 at 10:01 AM, Cedric Sodhi man...@gmx.net wrote:
Thanks Chris for replying, I knew I could rely on you guys :)
On Thu, Oct 27, 2011 at 09:07:37AM -0500, Chris Bagwell wrote:
On Thu, Oct 27, 2011 at 7:25 AM, Cedric Sodhi man...@gmx.net wrote:
I recently bought an ASUS EEE
On Thu, Oct 27, 2011 at 10:31:32AM -0500, Chris Bagwell wrote:
On Thu, Oct 27, 2011 at 10:01 AM, Cedric Sodhi man...@gmx.net wrote:
Kernel Config I:
HID_MULTITOUCH=M
USB_HIDDEV=Y
TOUCHSCREEN_USB_COMPOSITE=N
I do have three mice input devices from udev:
mouse0: The Wacom
Usually e-galax touch screens use an e-galax driver or evdev. Newer
versions of evdev tend to work better.
On the EP121 threads on Ubuntu forums they are using either although
at least some apparently have hacked the evdev code to force it into
touch screen mode. Perhaps the best thing would be
Oh, and I forgot to mention then, at least on Ubuntu, you would be
able to use ginn for multi-touch like we do with the N-trigs having
their touch on evdev while their stylus is on wacom.
Favux
--
The demand for IT
On Thu, Oct 27, 2011 at 10:50 AM, Cedric Sodhi man...@gmx.net wrote:
On Thu, Oct 27, 2011 at 10:31:32AM -0500, Chris Bagwell wrote:
On Thu, Oct 27, 2011 at 10:01 AM, Cedric Sodhi man...@gmx.net wrote:
HID_MULTITOUCH=N
USB_HIDDEV=Y
TOUCHSCREEN_USB_COMPOSITE=M
TOUCHSCREEN_USB_EGALAX=Y
On Thu, Oct 27, 2011 at 11:11 AM, Favux ... favux...@gmail.com wrote:
Usually e-galax touch screens use an e-galax driver or evdev. Newer
versions of evdev tend to work better.
On the EP121 threads on Ubuntu forums they are using either although
at least some apparently have hacked the evdev
On Thu, Oct 27, 2011 at 11:11:42AM -0500, Favux ... wrote:
Quote deadland:
Section InputClass
Identifier eGalax virtual class
MatchProduct eGalaxTouch Virtual Device
MatchDevicePath /dev/input/event*
Driver evdev
Option InvertY true
EndSection
And finally reboot you system.
41 matches
Mail list logo
