linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Andrej Gelenberg <andrej.gelenberg@googlemail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: GPen 340 Pen Tablet input
Date: Tue, 18 Mar 2008 14:10:45 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0803181409200.30831@jikos.suse.cz> (raw)
In-Reply-To: <alpine.LNX.1.00.0803170006240.22151@localhost>

On Mon, 17 Mar 2008, Andrej Gelenberg wrote:

> By moving and pressing keys report dmesg right values, but i have 
> problem by using my Tablet under Xorg. Xorg try evdev driver for it and 
> evdev report wrong codes.
> example for move:
> Mar 17 00:03:32 [kernel] [  446.045131] hid-debug: input GenericDesktop.X =
> 6742
> Mar 17 00:03:32 [kernel] [  446.045136] hid-debug: input GenericDesktop.Y =
> 17272
> Mar 17 00:03:32 [kernel] [  446.045139] hid-debug: input
> Digitizers.TipPressure = 0
> Mar 17 00:03:32 [kernel] [  446.048669] hid-debug: input Button.0001 = 0
> Mar 17 00:03:32 [kernel] [  446.048675] hid-debug: input Button.0002 = 0
> Mar 17 00:03:32 [kernel] [  446.048678] hid-debug: input Button.0003 = 0

[ restored linux-input in CC ]

So, and the problem is where? How are the values (mis)interpreted in X? 
Switched axes? Buttons mixup? Please be more specific.

Thanks,

-- 
Jiri Kosina
SUSE Labs

  parent reply	other threads:[~2008-03-18 13:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-16 18:22 GPen 340 Pen Tablet input Andrej Gelenberg
2008-03-16 18:57 ` Jiri Kosina
     [not found]   ` <alpine.LNX.1.00.0803162005320.32475@localhost>
2008-03-16 21:45     ` Jiri Kosina
     [not found]       ` <alpine.LNX.1.00.0803170006240.22151@localhost>
2008-03-18 13:10         ` Jiri Kosina [this message]
     [not found]           ` <alpine.LNX.1.00.0803181518200.3013@localhost>
2008-03-20  9:29             ` Jiri Kosina

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=Pine.LNX.4.64.0803181409200.30831@jikos.suse.cz \
    --to=jkosina@suse.cz \
    --cc=andrej.gelenberg@googlemail.com \
    --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).