linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel FAIVRE <webmaster@geomaticien.com>
To: Rafi Rubin <rafi@seas.upenn.edu>
Cc: Jiri Kosina <jkosina@suse.cz>, Stephane Chatty <chatty@enac.fr>,
	linux-input@vger.kernel.org
Subject: N-trig support
Date: Wed, 21 Oct 2009 06:39:07 +0200	[thread overview]
Message-ID: <200910210639.08138.webmaster@geomaticien.com> (raw)
In-Reply-To: <4AD6BEF8.6040308@seas.upenn.edu>

Hi,

After our last mails about n-trig support, I have :

- reported a bug for  OBS HEAD kernel-desktop (some opensuse build service 
kernels do not include drivers as modules)
https://bugzilla.novell.com/show_bug.cgi?id=548445

- reported a bug for outdated n--trig.c , suggesting is replacement by the one 
from git as suggested by Rafi.
https://bugzilla.novell.com/show_bug.cgi?id=548463

- tested the last linuxwacom-dev from cvs, patched to support n-trig :
the touch support is far better with the dev version : a touch tap is a click 
far more easily than with the last release. Touch beacame very smooth, as 
much as comfortable as under windows !
Last commit on linuxwacom was "Support Tablet PCs 0xE2 and 0xE3 as well as 
touch only tablet 0x9F" : THE NTRIG PATCH IS STILL MISSING !!!

Multitouch support :
In wcmUSB.c, we can see that support for multitouch is now included, waiting 
an event BTN_TOOL_TRIPLETAP.
A new option for xorg.conf, "Gesture", is used. 
Actually, this could not work for n-trig because hid-ntrig.ko does NOT send 
any BTN_TOOL_TRIPLETAP event, but it may be something to investigate ?

Screen buttons support :
Among patches for linuxwacom on sourceforge, one is used to detect and convert 
events from these three buttons.

X crashes : I encounter some X crashes with wacom_drv.so :
The system log reports :
wacom: v1.49-pc-1:USB Wacom Graphire and Wacom Intuos tablet driver
[Xorg[2694]: segfault at 6a0000000f ip 00007fded576e5c5 sp 00007fff73602780 
error 4 in wacom_drv.so [7fded578000+18000]

Wacom X drivers compiled from last release or from cvs have the same issue. 
That happens always when quitting an X session, and freeze display and all 
input devices, including keyboard. That also sometimes happens at boottime 
when starting X.
When X crash after booting, logs always reports things like :
0 is not supported by linuxwacom or 
1F is not supported by linuxwacom ...
When closing the X session, it seems to be related to :
X(deleteInputDeviceRequest+0x3b) [0x47713b]

In both cases, this issue seems related to wrong device vendor/product used in 
linuxwacom. Any idea to fix that ?

Best regards,
-- 
Daniel FAIVRE

  reply	other threads:[~2009-10-21  4:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4AD5DEF5.9020401@suse.com>
     [not found] ` <20091014205745.GC5623@suse.de>
     [not found]   ` <alpine.LSU.2.00.0910142342190.8582@wotan.suse.de>
2009-10-15  3:47     ` [opensuse-kernel] Re: Fwd: OBS HEAD kernel-desktop Daniel FAIVRE
2009-10-15  6:19       ` Rafi Rubin
2009-10-21  4:39         ` Daniel FAIVRE [this message]
2009-10-21 10:14           ` N-trig support Rafi Rubin

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=200910210639.08138.webmaster@geomaticien.com \
    --to=webmaster@geomaticien.com \
    --cc=chatty@enac.fr \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=rafi@seas.upenn.edu \
    /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).