On Mon, Sep 06, 2010 at 09:24:03AM +0400, Nikolai Kondrashov wrote: > On 09/06/2010 03:06 AM, Peter Hutterer wrote: > >depends. there is some advantage to having the same driver handle both > >devices in that a button can change properties on the stylus and the other > >way round. You're losing this ability when you have multiple kernel devices > >because then you need an extra property to match the devices up. > I just want to be absolutely sure: are we talking about the buttons on the > stylus itself or about the buttons located around the tablet working area, > on the frame? I'm inclined to think it's the latter, but still. Surely, I > don't want a separate device for the former. As for the latter, could you > please provide an exampe of the properties which these buttons could change, > which would need them to be on the same device?
the buttons on the frame. one example would be having a button switch the stylus between screens in a multi-screen setup (I don't think that works right now, but it used to). all that can be worked around in the client side, provided we actually have a client that handles this :) > >it's currently the only X driver with driver-internal hotplugging support > >anyway. > Are you going to do anything about it, or does it have a reason to be there? tbh, I'm not quite sure what the question here is. the wacom kernel driver exposes a single kernel device. we need multiple X devices for it, hence we have in-driver device creation/hotplugging/whatever you want to call it. I've got some preliminary code for evdev to do the same but not ready yet. Cheers, Peter ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
