3573 2012-12-12 16:54:22 +0000 LVDS Touch Screen is missing on imx6qsabreauto 2014-05-15 13:27:31 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-meta-fsl-arm 1.5 Other arm RESOLVED FIXED Medium normal 1.5.1 1 angolini angolini disabled.leonardo.sandoval florian.2.ludwig otavio sgw --- New (Never tested) Don't know oldest_to_newest 28195 0 angolini 2012-12-12 16:54:22 +0000 LVDS touchscreens does not work on imx6qsabreauto. Support needs to be included in kernel (from linux-imx-3.0.35) 28962 1 otavio 2013-01-18 23:11:51 +0000 Applied in bcea664dcc53be5dc6c5d95c6b2313f9ebb0756f 38329 2 florian.2.ludwig 2013-10-31 08:35:18 +0000 At the moment I try to get the LVDS Touch Screen (MCIMX-LVDS1) working on the imx6qsabreauto. But it doesn't seem to be fixed... evtest already gets input and the device is registered as /dev/input/event1 and /dev/input/mouse0 I built the latest branch (dora) and the layer fsl-image-gui. The Xorg.conf doesn't show the touch screen and also the Sato UI doesn't recognize the touchScreen (because it is not registered in XServer). So can we reopen this ticket? 38346 3 otavio 2013-10-31 14:49:05 +0000 Right; I reopened it. Leonardo, are you able to test this? 38443 4 florian.2.ludwig 2013-11-03 00:05:23 +0000 Thanks for reopening. I could also provide logs and step-by-step for reproducing the bug. I really need this feature and would like to support you as much as I can. 38471 5 disabled.leonardo.sandoval 2013-11-04 15:23:05 +0000 (In reply to comment #3) > Right; I reopened it. > > Leonardo, are you able to test this? Hi Otavio/Florian I have not tested it yet. I am about to finish two pending issues so during perhaps Wednesday I start testing/debugging this issue. Leo 38616 6 disabled.leonardo.sandoval 2013-11-06 18:31:49 +0000 (In reply to comment #4) > Thanks for reopening. > > I could also provide logs and step-by-step for reproducing the bug. I really > need this feature and would like to support you as much as I can. Florian, right now I do not have a board to test but for the moment, please try the following On the sources/meta-fsl-arm/recipes-kernel/linux/linux-imx_3.0.35.bb, REMOVE the line where this patch is indicated file://0005-ENGR00271359-Add-Multi-touch-support.patch Bake and test please. 38687 7 disabled.leonardo.sandoval 2013-11-08 15:43:23 +0000 (In reply to comment #6) > (In reply to comment #4) > > Thanks for reopening. > > > > I could also provide logs and step-by-step for reproducing the bug. I really > > need this feature and would like to support you as much as I can. > > Florian, right now I do not have a board to test but for the moment, please > try the following > > On the sources/meta-fsl-arm/recipes-kernel/linux/linux-imx_3.0.35.bb, REMOVE > the line where this patch is indicated > > file://0005-ENGR00271359-Add-Multi-touch-support.patch > > > Bake and test please. I have tested removing this patch and the touch-screen works. Due to time restrictions, I did not test this issue on a clean image (by clean I mean no changes on any branch, just dora HEADS), what I just did is what I indicated in the last msg and boot it. Arrow Pointer is following my finger's touch so I believe this fixes the issue. Florian, Help me to confirm the latter so I can send a patch. 38703 8 florian.2.ludwig 2013-11-11 11:19:47 +0000 Ok thanks for the advice - I will test it in the next few days! 38765 9 florian.2.ludwig 2013-11-14 12:12:10 +0000 Yes, indeed - after removing the Multitouch-Patch everything works in the fsl-image-gui image. Btw: Does anyone know if this patch also adds multitouch support for QtQuick 4.8? Thanks a lot everybody! 38766 10 otavio 2013-11-14 12:17:15 +0000 I think we need to better understand this issue so we can proper fix it. Florian, can you check if changing: CONFIG_TOUCHSCREEN_EGALAX_SINGLE_TOUCH = n makes it work? 38770 11 florian.2.ludwig 2013-11-14 12:33:55 +0000 You mean I should add the patch back in again and then add CONFIG_TOUCHSCREEN_EGALAX_SINGLE_TOUCH = n to the .bb file, right? 38771 12 otavio 2013-11-14 12:52:13 +0000 No; to the defconfig of kernel. 39094 13 florian.2.ludwig 2013-11-26 13:10:00 +0000 Sorry but I have to admit, that I didn't do this before - where can I set this variable in the defconfig? Thanks Florian 39099 14 disabled.leonardo.sandoval 2013-11-26 15:50:53 +0000 (In reply to comment #13) > Sorry but I have to admit, that I didn't do this before - where can I set > this variable in the defconfig? > > Thanks > Florian Hi Florian, Create a patch adding the CONFIG into the defconfig, then just the kernel and deploy. % modify the defconfig under meta-fsl-arm % bitbake -c compile -f imx-linux % bitbake -c deploy imx-linux % dd if ....... % boot the board. If worked, then create the patch. Leo 39103 15 1649 florian.2.ludwig 2013-11-26 16:43:15 +0000 Created attachment 1649 Defconfig patch Oh ok, thanks. Didn't find the defconfig before. The patch is attached and yes, it works the way Otavio suggested! 43259 16 sgw 2014-05-12 16:15:49 +0000 Please close this out if this is fixed in your branch, thanks 43262 17 otavio 2014-05-12 16:29:30 +0000 Daiane, can you try it in Daisy and check if it can be reproducable? 43361 18 angolini 2014-05-15 13:27:31 +0000 Tested on daisy, with core-image-x11 and default DISTRO_FEATURES It worked for me. I'm going to close this issue 1649 2013-11-26 16:43:15 +0000 2013-11-26 16:43:15 +0000 Defconfig patch mxcimx-lvds1-touchscreen-fix.patch text/plain 595 florian.2.ludwig cHJvamVjdCBzb3VyY2VzL21ldGEtZnNsLWFybS8KZGlmZiAtLWdpdCBhL3JlY2lwZXMta2VybmVs L2xpbnV4L2xpbnV4LWlteC0zLjAuMzUvbXg2cS9kZWZjb25maWcgYi9yZWNpcGVzLWtlcm5lbC9s aW51eC9saW51eC1pbXgtMy4wLjM1L214NnEvZGVmY29uZmlnCmluZGV4IDU0MmU5NDkuLjZiOGNk YTQgMTAwNjQ0Ci0tLSBhL3JlY2lwZXMta2VybmVsL2xpbnV4L2xpbnV4LWlteC0zLjAuMzUvbXg2 cS9kZWZjb25maWcKKysrIGIvcmVjaXBlcy1rZXJuZWwvbGludXgvbGludXgtaW14LTMuMC4zNS9t eDZxL2RlZmNvbmZpZwpAQCAtMTMwLDcgKzEzMCw3IEBAIENPTkZJR19LRVlCT0FSRF9HUElPPXkK ICMgQ09ORklHX0lOUFVUX01PVVNFIGlzIG5vdCBzZXQKIENPTkZJR19JTlBVVF9UT1VDSFNDUkVF Tj15CiBDT05GSUdfVE9VQ0hTQ1JFRU5fRUdBTEFYPXkKLUNPTkZJR19UT1VDSFNDUkVFTl9FR0FM QVhfU0lOR0xFX1RPVUNIPXkKK0NPTkZJR19UT1VDSFNDUkVFTl9FR0FMQVhfU0lOR0xFX1RPVUNI PW4KIENPTkZJR19UT1VDSFNDUkVFTl9FTEFOPXkKIENPTkZJR19UT1VDSFNDUkVFTl9NQVgxMTgw MT15CiBDT05GSUdfSU5QVVRfTUlTQz15Cg==