From: Peter Hutterer <peter.hutterer@who-t.net>
To: Chris Bagwell <chris@cnpbagwell.com>
Cc: Henrik Rydberg <rydberg@euromail.se>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Ping Cheng <pingc@wacom.com>,
linux-input@vger.kernel.org
Subject: Re: [PATCH] input: Add support for the Bamboo Touch trackpad
Date: Tue, 31 Aug 2010 15:44:37 +1000 [thread overview]
Message-ID: <20100831054437.GA14760@barra.redhat.com> (raw)
In-Reply-To: <AANLkTikh6r+-aeiqT7nq3Z4jL+WZK22G4zVeUwQFLfr1@mail.gmail.com>
On Mon, Aug 30, 2010 at 11:19:49AM -0500, Chris Bagwell wrote:
> Hi Henrik,
>
> On Mon, Aug 30, 2010 at 4:10 AM, Henrik Rydberg <rydberg@euromail.se> wrote:
> > Hi Chris,
> >
> >>> 1) It uses the MT slot protocol
> >>> 2) It creates two input devices, but only one is useful
> >>
> >> No biggy to userspace. I'm assuming for unused input device that
> >> hardware is still reporting a HID_USAGE_STYLUS and probably you could
> >> catch that and not register that input device.
> >
> >
> > The initial idea was to only use the trackpad usb endnode, but the device does
> > not work at all after boot unless the silent endnode is somehow taken into
> > account. I am not sure what your statement refers to.
> >
> >>> 3) It works well with the synaptics and multitouch X drivers
> >>> 4) It does not work well with the wacom X driver (!)
> >>
> >> Once we finalize input events sent, I'm sure we could get
> >> xf86-input-wacom to play nice with this synaptic-style input events.
> >> The harder part is to develop userspace rules to assign this "wacom"
> >> input device to something other than xf86-input-wacom; especially in
> >> case were tablet has pen and touch input devices.
> >
> >
> > Using udev rules, the pen device is picked up by the wacom X driver and the
> > touch device is picked up by the synaptics X driver. It does not seem anything
> > extra is needed here.
>
> You mean your wacom touch device are being directed to synaptics X
> driver without modifications to udev or similar rules? On my
> unmodified Fedora box, they both go to wacom X driver.
>
> Not that it would be a difficult modification... I'd just need to make
> those and work with distributions to also align.
50-wacom.conf sorts after 50-synaptics.conf and since we apply the wacom
driver to anything with Wacom in the product name, it overrides the
synaptics setting. not a big deal at all, just renaming it to 40-wacom.conf
should already do the job.
Cheers,
Peter
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-08-31 5:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-22 14:10 [PATCH] input: Add support for the Bamboo Touch trackpad Henrik Rydberg
2010-08-23 14:00 ` Ping Cheng
2010-08-23 14:30 ` Henrik Rydberg
2010-08-23 17:02 ` Ping Cheng
2010-08-23 17:02 ` Ping Cheng
2010-08-23 17:30 ` Chris Bagwell
2010-08-30 9:10 ` Henrik Rydberg
2010-08-30 16:19 ` Chris Bagwell
2010-08-31 5:44 ` Peter Hutterer [this message]
2010-09-01 3:16 ` Chris Bagwell
2010-09-01 10:48 ` Ping Cheng
2010-09-01 11:55 ` Henrik Rydberg
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=20100831054437.GA14760@barra.redhat.com \
--to=peter.hutterer@who-t.net \
--cc=chris@cnpbagwell.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=pingc@wacom.com \
--cc=rydberg@euromail.se \
/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).