linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Julian Squires <julian@cipht.net>, linux-input@vger.kernel.org
Subject: Re: [PATCH] input: Add support for Wacom protocol 4 serial tablets
Date: Sat, 19 Jul 2014 16:09:10 -0700	[thread overview]
Message-ID: <20140719230910.GB19006@core.coreip.homeip.net> (raw)
In-Reply-To: <1405787920-3354-1-git-send-email-hdegoede@redhat.com>

On Sat, Jul 19, 2014 at 06:38:39PM +0200, Hans de Goede wrote:
> Hi All,
> 
> Recent version of xf86-input-wacom no longer support directly accessing
> serial tablets. Instead xf86-input-wacom now expects all wacom tablets to
> be driven by the kernel and to show up as evdev devices.
> 
> This has caused old serial Wacom tablets to stop working for people who still
> have such tablets. Julian Squires has written a serio input driver to fix this:
> https://github.com/tokenrove/wacom-serial-iv
> 
> About a year ago Julian submitted this upstream, back then the response by
> Dmitry was:
> 
> > The driver looks quite reasonable, however that would be the 4th Wacom
> > driver in the tree... I wonder if it is time to split out transport
> > parts from core wacom functionality so that it can be shared by USB, I2C
> > and serio devices.
> 
> I've taken a quick look at this, the i2c driver is for touchscreens and in
> the protocol has nothing in common with the other wacom drivers. The w8001
> driver is for serial touchscreens and again a completely different protocol.
> 
> The wacom usb driver already deals with what appears to be a lot of different
> protocol nuances, see for example wacom_wac.c, and non of all the different
> package formats parsed in wacom_wac.c seem to have anything in common with
> the wacom protocol 4 spoken over serial. So it seems that there is nothing
> to be shared since these are really significant different devices which happen
> to be from the same vendor. Moreover the usb wacom bits are being reworked
> to use hid instead of to more or less parse usb hid reports themselves, and
> I certainly don't want this driver to get in the way of that.
> 
> So all in all I believe it is best to keep this as a standalone driver.
> 
> Hence I'm hereby re-submitting this driver for upstream inclusion.
> 
> This is a significantly cleaned up version of the driver initially submitted
> by Julian, with improved Graphire support (I own an old Graphire myself).

OK, fair enough, let's merge it. I sent out some questions in reply to
the patch itself.

Thanks.

-- 
Dmitry

      parent reply	other threads:[~2014-07-19 23:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-19 16:38 [PATCH] input: Add support for Wacom protocol 4 serial tablets Hans de Goede
2014-07-19 16:38 ` Hans de Goede
2014-07-19 23:08   ` Dmitry Torokhov
2014-07-20 14:23     ` Hans de Goede
2014-07-19 23:09 ` Dmitry Torokhov [this message]

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=20140719230910.GB19006@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=julian@cipht.net \
    --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).