On Tue, 17 Apr 2012, Tvrtko Ursulin wrote: > > > It is unlikely to be me unless someone explains to me in detail what > > > needs to be done, at which point it is probably quicker for that person > > > to do it. I for example don't even understand why this, allegedly HID > > > Multitouch class compliant, device needs explicit adding? Is it not > > > compliant after all? Is it that multiple HID devices it exposes a > > > non-standard thing? Does it then need a vendor specific class (looking > > > at hid-multitouch.c). Sorry this whole area is just new and unknown to > > > me. > > > > Could you please verify that the patch below works for you? Thanks. > > Works fine. I made a typo in the thread subject, one too many 'o' in vendor's > name - Baanto is correct. Thanks, I will fix that up before applying. > P.S. I still do not understand why it is needed to explicitly add this device > for it to work, but nevermind, I asked this enough time to know when to give > up. Because currently there is no way how to auto-load proper module if the device is multitouch. Henrik is working in this area. -- Jiri Kosina SUSE Labs -- 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
