On Friday 03 July 2015 15:50:47 Michał Kępień wrote: > > There are two different things: > > > > 1) Vendor said that laptop models with specific DMI should be handled by > > code XYZ... > > > > 2) Vendor said that all laptop models which report in register ABC value > > 47 should be handled by code XYZ. > > > > And we are thing to fix above facts with solution: > > > > 3) See how one model reacts and from this information create specific > > hook for that one model. > > > > I'm really against solution 3) if we already know that every model uses > > different event handling. > > > > If for model Dell Vostro V131 vendor say 1) I'm fine with solution to > > hardcode DMI name and hook for it. 2) is of course better, but 3) for > > lot of machines is non go. > > I couldn't agree more. Here's the thing, though: the vendor doesn't seem > to be saying anything. I guess I'll have to get over it. > Yes, "vendor does not say anything" is also what could happen... Then in your case, I would need to know format of *all* events which can your laptop via WMI receive. If we collect as more as possible events from different laptops we can try to abstract format/interface. -- Pali Rohár pali.rohar@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
