Messages in this thread | | | Date | Sat, 27 Sep 2003 22:19:51 +0200 | From | Pavel Machek <> | Subject | Re: [PATCH 8/8] Add BTN_TOUCH to Synaptics driver. Update mousedev. |
| |
Hi!
> > IMHO we should let input device driver explicitly request which input > > handler it wishes to bind to (for example by passing a bitmap of desired > > input handlers when registering input device and everyone binds to evdev). > > It is not as flexible as capabilities checking solution but much more > > simple and predictable. I do not thing that there will be that many handlers > > implemented... > > No, it won't work. It assumes that all the handlers are known > beforehand. Someone may want to load their own input handler module and > it wouldn't bind to any device, because it wouldn't be on the list. > > Also, we need to communicate the information not just to kernel > handlers, but also to userspace programs/drivers ... > > One thing I tried to avoid is a 'device class' kind of field, that'd > tell if a device is a mouse a touchpad, touchscreen, tablet, whatever. > I tried to avoid it because there are devices that don't fall into any > predefined class and if we make enough classes, someone someday will > make a device that won't fit again.
I believe having "is overlaid over screen" bit gets it right :-).
Pavel -- When do you have a heart between your knees? [Johanka's followup: and *two* hearts?] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |