Gregor Riepl

I'm almost 100% sure that this is a firmware issue, not a driver one. The driver pretty much takes whatever it gets from the hardware, scales it and passes it...

Yes, the problem is almost certainly in the firmware or in the device parameters. If any of them aren't correct, you will experience all kinds of problems with the touchscreen....

As far as I know, there is no hardware register or firmware parameter that reports the resolution. You'll have to experiment a bit to find it out. It's not terribly...

I just updated the readme with better instructions and added a tool for SileadTouch.sys firmware extraction. Please give them a try!

There is no point in changing fwtool, because gslx680_acpi doesn't support xmin/ymin. I recommend switching to the silead_ts driver that is available in mainline Linux - it supports standard input...

There is, please look at the readme. I agree, it's a bit technical, but the process is very tedious and technical, especially if you want to add support for your...

`silead.ko` uses firmware in "vanilla" format, so https://github.com/onitake/gsl-firmware/blob/master/firmware/chuwi/hibook/firmware.fw should work. If you need to convert Windows driver firmware instead, please use https://github.com/onitake/gsl-firmware/blob/master/tools/unscramble .

Have you tried unloading the module (`modprobe -r silead`) before re-insmoding it? You should also make sure that no other silead modules are loaded (i.e. gslx680-acpi, ...).

Hmm... If you unload and reload the module, you should at least see that it's matching the device. If the DMI info is wrong, it will still try to initialise...

Well, there's gslx680-acpi, and possibly other competing drivers. I think there's a way to check which driver has claimed a device, but I don't remember how exactly. Possibly through sysfs?...