Gregor Riepl

Ok - this is very interesting! It looks like your machine has a touch screen device id that is different from others. Can you replace `.acpi_name = "MSSL1680:00",` with `.acpi_name...

Then I'm at my wit's end... If you don't get any message at all, that means no driver has matched your hardware. If you can't get silead.ko to at least...

Good point... Never thought of that. But it totally makes sense: ``` config SILEAD_DMI bool "Tablets with Silead touchscreens" depends on ACPI && DMI && I2C=y && TOUCHSCREEN_SILEAD ``` @Split7fire...

I just updated the readme with better instructions for adding support to silead_ts. Any corrections/improvements are welcome.

I just updated the readme with better instructions for adding support to silead_ts. Perhaps they may help you.

You will very likely not succeed with these. Silead touchscreen controllers are terribly misdesigned and require firmware and hardware parameters that are precisely matched for each device. The Linux kernel...

Sorry about the confusion. The touch is a separate piece of hardware from the display, and may have a completely different resolution. There is not straightforward way to determine that...

I added a short note: "(or similar)" Naming _THREE explicitly doesn't seem to make sense to me, this looks more like a mess made by the vendor, not firmware file...

Yeah, it's something I've seen myself. I don't know how to solve that problem. Perhaps a high jitter value helps. If you have to means to hack the driver code,...

That means the configured touch area does not cover what the controller sends, or the firmware does not match the panel. As mentioned elsewhere, the firmware image contains device specific...