From: Simon Ask Ulsnes <simon@ulsnes.dk>
To: Matt Gibson <gothick@gothick.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Complaint: Wacom driver in 2.6
Date: Tue, 30 Sep 2003 08:59:23 +0200 [thread overview]
Message-ID: <200309300859.23281.simon@ulsnes.dk> (raw)
In-Reply-To: <200309291956.27688.gothick@gothick.org.uk>
Thanks for replying.
You aren't even using the wacom driver!
Mine works too in that way (I think it is some kind of regular PS/2 mouse
emulation or so).
Come to think of it, maybe the problem lies in the XFree86 driver, which I
suppose isn't really compatible with the new kernel. Well, whatayaknow... ;-)
- Simon
On Monday 29 September 2003 20:56, you wrote:
> On Monday 29 Sep 2003 13:21, Simon Ask Ulsnes wrote:
> > Hello there!
> > I am the lucky owner of a Wacom Graphire 2 tablet, which works great with
> > the latest 2.4-kernels. However, the 2.6-drive is unusually and utterly
> > broken. Frankly, it doesn't work at all.
>
> If it's any hope for you, I'm using the Wacom driver with an original
> Graphire, and it's working OK for me. I'm currently on 2.6.0-test5, and
> I'm pretty sure I'm using the vanilla wacom.c (it's version 1.30 according
> to the comments.)
>
> If you want any info about how I've got things configured, feel free to
> give me a shout. In particular, I've got these relevant entries in my
> XF86Config:
>
> # Our ordinary PS/2 and Wacom mice; they're both multiplexed into
> # /dev/mice by the kernel input event handling.
> Section "InputDevice"
> Driver "mouse"
> Identifier "Mouse[1]"
> Option "ButtonNumber" "5"
> Option "Device" "/dev/input/mice"
> Option "Name" "Autodetection"
> Option "Protocol" "imps/2"
> Option "Vendor" "Random"
> Option "ZAxisMapping" "4 5"
> EndSection
>
> Goodness knows if I need half those options set up; it's a
> much-hacked-about-with old file that was originally set up by the SuSE SaX2
> configuration tool, about three years ago! But I tend to live by "if it
> ain't broke, don't fix it." I guess the important thing I did to get it
> working under 2.6.0 was just to drop all the event interface crap and just
> run it off /dev/input/mice, which is where the kernel happily feeds all the
> wacom input through into.
>
> Section "ServerLayout"
> ... other stuff deleted ...
> InputDevice "Mouse[1]" "CorePointer"
> EndSection
>
> That's all I needed to get the mouse and pen working. Of course, to go the
> whole hog and get the pressure sensitive stuff and the pointer vs. eraser
> functionality etc. you'd need to use the X11 wacom driver, but I've never
> actually felt the need.
>
> Cheers,
>
> Matt
next prev parent reply other threads:[~2003-09-30 6:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 12:21 Complaint: Wacom driver in 2.6 Simon Ask Ulsnes
2003-09-29 18:56 ` Matt Gibson
2003-09-30 6:59 ` Simon Ask Ulsnes [this message]
2003-09-30 17:13 ` Matt Gibson
2003-09-30 20:59 ` Simon Ask Ulsnes
2003-09-30 22:19 ` Matt Gibson
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=200309300859.23281.simon@ulsnes.dk \
--to=simon@ulsnes.dk \
--cc=gothick@gothick.org.uk \
--cc=linux-kernel@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