All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Ask Ulsnes <simon@ulsnes.dk>
To: linux-kernel@vger.kernel.org
Subject: Complaint: Wacom driver in 2.6
Date: Mon, 29 Sep 2003 14:21:45 +0200	[thread overview]
Message-ID: <200309291421.45692.simon@ulsnes.dk> (raw)

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.

When I load up X11 with the proper /dev-symlinks and all that stuff in place 
(2.6 names the tablet /dev/input/event1 as opposed to 2.4, which names it /
dev/input/event0), the tablet simply doesn't respond. I can see in my 
XFree86.0.log file that the tablet is recognized correctly by the kernel, but 
that's about it.

Of course, I tried the linux-wacom (linux-wacom.sourceforge.net) drivers, but 
they fail to compile most miserably (the beta dev-version). From what I could 
deduce of the compiler output, it is incompatible with 2.6.

I filed a bug report a long time ago (2.5.65-ish), but no one really seemed to 
care.

I would really like some info on what progress is being made in this area, as 
it currently is the only thing stopping me from switching seriously to 2.6.
I suppose it is also one of those drivers that Linus keeps talking about need 
to be ready before 2.6 can be finally released (in which I agree, obviously).

And finally, some relevant system specs:
Distro: Gentoo
Kernel: 2.6.0-test6
X11: XFree86 4.3.99.12

Yours sincerely,
Simon Ask Ulsnes



             reply	other threads:[~2003-09-29 12:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 12:21 Simon Ask Ulsnes [this message]
2003-09-29 18:56 ` Complaint: Wacom driver in 2.6 Matt Gibson
2003-09-30  6:59   ` Simon Ask Ulsnes
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=200309291421.45692.simon@ulsnes.dk \
    --to=simon@ulsnes.dk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.