[trsqr]

That's no surprise at all - as you know from the posted bugreport here - it's a kernel driver issue and as long as the referenced bugreport does not get any news nothing won't happen.

Well, we did see the same problem in Windows 10 and it started to work after the LSPCon firmware update without any change to the driver. Thus I don't think it was unreasonable to assume that there was a slight chance that it'd start working on Linux as well after the firmware update.

But yes, that was not the case, so you must be right.