On Thu, Apr 29, 2010 at 09:54:08PM -0000, Dmitry Torokhov wrote: > I am guessing you are looking into something similar to ALPS driver > options but I am not sure if this is really needed.
Actually I wasn't aware of the internals of the ALPS driver, or the existance of an ALPS driver, for that matter, but yes. That certainly looks like what I had in mind. > Currently we only have 2 options in the driver: main is hardware version > (1 or 2, 4-byte or 6-byte packets), the second is "jumpy cursor" which > is indeed tied to hardware version 1. I would be interested to see if we > can pinpoint the transition from hardware version 1 to 2 better, and I > suspect we'll have to take into account middle byte for it. Yes, I completely agree. We only seem to disagree on the method to figure out a proper way to identify v2 hardware. I suggested hardcoding a list of known firmware ids, and giving the user a way to override the decicions made with that. That way it seems reasonably easy to obtain more data points on firmware and hardware versions. Once we have enough of those, pinpointing the v1->v2 transition will hopefully be trivial, and even if it isn't, we'd still have have an infrastructure we can easily add new devices as reported by users to. All that, while not introducing any regressions in detection. You seem to suggest the same thing, except before "3. profit!", you've got "2. ???", instead of "2. make collecting datapoints easier". Am I misunderstanding you? > Have you tried talking to Arjan about it? No, I haven't. Based on the feedback of others he seemed unresponsive on this issue. I'll try tho. > For .34 I'd appreciate a patch simply forcing Viking's full (3-byte) > firmware version to map to hw 2 to minimize regressions. It'll show up on the -input list shortly. -- BOFH excuse #305: IRQ-problems with the Un-Interruptible-Power-Supply -- Can't configure Elan tech touchpad on Dell Inspiron 11z, Asus K7I0C and maybe also Dell Mini 10 (not V), ASUS k40in, Asus U81A and ASUS UL80-VT. https://bugs.launchpad.net/bugs/512192 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
