@Fernando l ask for your help to add a FeatureScore value of “00”+Signing to the I2C driver (iaioi2c.inf) inside this package:
Is the last version for the Intel I2C devices with HwID:
Almost all Intel ValleyView2System.inf CHIPSET drivers install a NULL driver and the 2 other nothing for this CoincidentDeviceID=ACPI\VEN_8086&DEV_0F41:
i2cNULLdriver?: Version: Date:
YES 10.1.1.7 2015-0616
YES 10.1.1.8 2015-0626
NO 10.1.1.13 2015-1028 (Installed by WinUpdate)
NO 10.1.1.18 2016-0404
YES 10.1.1.40 2017-0103
YES 10.1.1.42 1970-0101
YES 10.1.1.44 2017-1111 (has another version with 1968-0718)
YES 10.1.1.45 1968-0718
YES 10.1.3.1 1968-0718
Since the last version of the functional Intel I2C controller driver (linked above) has a date of:
Can be replaced by any Chipset's NULL driver with a newer date than it, making unusable the TouchPad of the laptop in advanced mode (Established in BIOS). Sure its posible to install an older Chipset driver but it feel like in any moment for watever reason can be installed a newer one:
So Fernando I ask you for help to add the value to make the I2C controller always the top choice no matter what. I hope you can do it and thank you in advance.
The I2C device is the only one device, other than the chipset devices, that is configured inside the ValleyView2 Chipset driver. No other devices are configured by it, not the GPIO, MBI, USB3, etc.
And this problem seems to be the cause for many complains in the web for NOT working TouchPads and TouchScreens.
Off course the Chipset driver install functional drivers too for certain devices in a mode that I think is called RAW mode, that do not need a .SYS file from the manufacturer and that seems to interact directly with the Windows HAL or the Inbox drivers.