On Thu, 06 Aug 2009, Dmitry Torokhov wrote: > >But don't we have a crapload of implementation weirdness work- > >arounds in the > >i8042 drivers, including some for problems with the raw protocol > >itself? We > >wouldn't want to duplicate THAT... > > There actually not many quirks there, once we identified all ports > on i8042; mostly we need to deal with keys not sending release > events. > > >will the filter be placed somewhere that > >doesn't have to deal with that kind of bogosity? > > The problem with doing this on input core level is that we don't It doesn't have to be on the input core, it could be on i8042, but the hook should be AFTER i8042 did all the processing and cleanup that we want to take place... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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
