Gregor Riepl

I'm afraid that's the only way to actually make the driver recognise the hardware properly. Originally, there was an effort by an Intel engineer to build proper ACPI-based configuration for...

This is what you should match: > System Information > Manufacturer: Insignia > Product Name: NS-P11W7100 and possibly: > SKU Number: 5255800 With the `firmware.fw` in https://github.com/onitake/gsl-firmware/tree/master/firmware/insignia/flex11 , can you...

I'm afraid that you do have to recompile the kernel. The part that does driver pre-initialisation is not part of any kernel modules or easily replaceable code. You really have...

Thats's promising! It looks like you finally got the right firmware. You still need to tweak the parameters though. Determine what range the X and Y coordinates have and put...

If possible, put roughly correct values into you kernel patch. That will save others from needing to recalibrate later. Note that the value range doesn't necessarily to correspond with what...

Can you verify if the kernel is loading your "custom" firmware? You should see a line like > firmware: direct-loading firmware silead/gsl3670-insignia_flex11.fw somewhere in dmesg output. I think we should...

Oh, and the second most common case of mismatches are trailing spaces or other unprintables.

Yes, I saw it. But I don't see anything about the firmware in your dmesg output. Can you check again?

Ah... I think I know what's going on. `request_firmware` only prints a warning when the firmware can't be found. Otherwise, you get debug messages. Can you run `dmesg -n 8`...

Please don't use fwtool any more. It's for my older driver, as indicated in the readme. silead.ko needs "vanilla" firmware that was simply extracted, but not converted with fwtool.