Re: platform/x86/peaq-wmi on non-peaq devices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 31-10-17 10:13, Mantas Mikulėnas wrote:
Hello,

Recently I have seen quite a few people (in Linux support channels I frequent) have issues with the peaq-wmi driver being autoloaded on *non* PEAQ devices and subsequently flooding the user with ghost keypresses. They end up having to blacklist the module locally.

I noticed that the WMI GUID used by the driver, {ABBC0F6F-8EA1-11D1-00A0-C90629100000}, is identical to a GUID used in *Windows driver examples* published by Microsoft. (For example, it shows up on Google at <https://github.com/Microsoft/Windows-driver-samples/blob/master/wmi/wmiacpi/device.asl>.)

So I'm guessing that quite a few manufacturers decided to copy&paste this GUID into their own drivers/firmwares, but use it for completely different things. Given that, instead of trying to build a DMI blacklist in the module, perhaps the right thing would be to add a DMI *whitelist*?

Correct this is already queued for 4.15, with a Cc: stable:

http://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git/shortlog/refs/heads/for-next

Regards,

Hans




[Index of Archives]     [Linux Kernel Development]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux