Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx> writes: > Given how unwilling they are to share details of their protocol I would > not be surprised if they tried to detect virtual environment on purpose. > Sadly, you very well could be right. That being said, I don't know what they could be checking for. I'm passing "-cpu host" to qemu which should eliminate the CPUID hint. Otherwise, the only obvious hint I can find is the hard drive which mentions Qemu in its vendor string. Taking a quick look at the apfiltr.sys I can't find any strings that might imply it's looking at device/vendor strings. Perhaps they could be using ACPI tables (although I see no ACPI-ish strings in the driver)? I guess SMBIOS and DMI are also targets although I know little about their implementation. Anyways, I suppose at this point it is probably time to bring this discussion over to the qemu list to discuss future directions for virtualization. Unfortunately, it becomes very difficult to maintain motivation on problems like this when Alps will likely render whatever reverse engineering knowledge gained now obsolete in the next iteration of hardware. It seems clear that the only sustainable way to get open-source support for these and future Alps devices is with some cooperation from Alps and/or a major customer. It seems that Dell is in an ideal position to help here. Cheers, - Ben -- 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
