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@xxxxxxxxxxx> 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html