Hi William, > > Hi Abraham - > What were the compile errors you got? Were they only for building on Omap or > do you get them when compiling for other Linux (x86 for example)? I would like > to know because we didn't get any compile errors. > A minor one when compiled as modules ERROR: "FN_11_report" [drivers/input/touchscreen/rmi_core.ko] undefined! ERROR: "FN_11_config" [drivers/input/touchscreen/rmi_core.ko] undefined! ERROR: "FN_11_init" [drivers/input/touchscreen/rmi_core.ko] undefined! ERROR: "FN_11_detect" [drivers/input/touchscreen/rmi_core.ko] undefined! but no issues when working built-in after some changes input: RMI4 Touchpad as /devices/virtual/input/input1 rmi_register_phys_driver: rmi4_ts: Registering phys driver rmi4_i2c_ts omap_device: i2c_omap.2: new worst case activate latency 0: 61035 rmi_register_phys_driver: rmi4_ts: could not find support for function 0x34 rmi_register_phys_driver: rmi4_ts: could not find support for function 0x8 probe: Found 301 data sources for : dfb56974 match_and_bind: rmi4_ts is rmi4_touchpad bound to rmi4_i2c_ts config: could not find support for function 0x32 config: could not find support for function 0xff config: could not find support for function 0xff The link to my changes is below so I could have all layers registered without kernel panics, this is a diff between initial commit in input tree and initial commit + my changes in linux omap. http://pastebin.com/54d7d3b0 I have not dig into details and fixes, I'll wait for your patch after review to make it my baseline. Please let me know any other request, thanks for your help! Best Regards Abraham -- 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
