From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 7875CE00786; Mon, 6 Oct 2014 09:11:22 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (swexru[at]gmail.com) * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.215.46 listed in list.dnswl.org] Received: from mail-la0-f46.google.com (mail-la0-f46.google.com [209.85.215.46]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 4E691E004D8 for ; Mon, 6 Oct 2014 09:11:13 -0700 (PDT) Received: by mail-la0-f46.google.com with SMTP id gi9so4677447lab.19 for ; Mon, 06 Oct 2014 09:11:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=e6IJSs5c2Sat6aAkLIEgVpZ46znGsIvR5VVOVExtbcE=; b=RmSpZdOFUJHdkuU1fmjaBNFrFXaOy3JYByLARz6RW7hgGkC7eyW4MGWwzRfE77OZcH IOJeRtrVFHb1GDkj7S0lpyF/797c7uEE/Klff9UzozcElxZVjfe15NV9HPnjX8GZdbsY phrH4aV6pRwpUy/ru6twtDBpW88qGLSLh0/ViHCqOkRnFw+ct6GnSiVJ1SbKyqrnOPyR lnWyJU5F+IooVgfy5MN5SoGl6DqvsLkohh5Ih6x3S0UpUzTscZ7Y7r727xCCOyB1tPRH J8z7XGJ4aUNZE7ZmBwZVbpvdrCiHWuLSUyUzPzeHTHzv9zg2a6L/dJ8lO/bXRLcVoEaJ u5RQ== X-Received: by 10.152.28.167 with SMTP id c7mr3920735lah.27.1412611870978; Mon, 06 Oct 2014 09:11:10 -0700 (PDT) Received: from [10.11.0.226] ([46.28.89.62]) by mx.google.com with ESMTPSA id jp17sm5880140lab.18.2014.10.06.09.11.09 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Oct 2014 09:11:10 -0700 (PDT) Message-ID: <5432BF1C.40706@gmail.com> Date: Mon, 06 Oct 2014 20:11:08 +0400 From: Alexey Mednyy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: meta-freescale@yoctoproject.org Subject: Linux headers version problem/bug? X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Oct 2014 16:11:22 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello everybody! Everything started with problematic touchscreen: We've got mx53 based board. And we're using mc34709 touchscreen on it. Here is output of xinput_calibrator: > root@imx53qsb:~# xinput_calibrator -v > DEBUG: XInputExtension version is 2.3 > DEBUG: Skipping virtual master devices and devices without axis valuato= rs. > DEBUG: Skipping device 'Virtual core XTEST pointer' id=3D4, does not > report Absolute events. > DEBUG: Selected device: mxc_ts > DEBUG: Not usbtouchscreen calibrator: Not a usbtouchscreen device > DEBUG: Read axes swap value of 0. > DEBUG: Read InvertX=3D0, InvertY=3D0. > Calibrating EVDEV driver for "mxc_ts" id=3D9 > current calibration values (from XInput): min_x=3D0, max_x=3D0 = and > min_y=3D0, max_y=3D0 > DEBUG: Adding click 0 (X=3D0, Y=3D0) > DEBUG: Not adding click 1 (X=3D0, Y=3D0): within 7 pixels of previous c= lick > DEBUG: Not adding click 1 (X=3D0, Y=3D0): within 7 pixels of previous c= lick > DEBUG: Not adding click 1 (X=3D0, Y=3D0): within 7 pixels of previous c= lick And Xorg.log: > root@imx53qsb:~# tail /var/log/Xorg.0.log > Divide by Zero in xf86ScaleAxis > Divide by Zero in xf86ScaleAxis > Divide by Zero in xf86ScaleAxis > Divide by Zero in xf86ScaleAxis > Divide by Zero in xf86ScaleAxis > Divide by Zero in xf86ScaleAxis > Divide by Zero in xf86ScaleAxis > Divide by Zero in xf86ScaleAxis > Divide by Zero in xf86ScaleAxis > Divide by Zero in xf86ScaleAxis But evtest /dev/input/touchscreen0 shows right values: > Input driver version is 1.0.0 > Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0 > Input device name: "mxc_ts" > Supported events: > Event type 0 (Sync) > Event type 1 (Key) > Event code 330 (Touch) > Event type 3 (Absolute) > Event code 0 (X) > Value 239 > Min 0 > Max 0 > Event code 1 (Y) > Value 215 > Min 0 > Max 0 > Event code 24 (Pressure) > Value 0 > Min 0 > Max 0 > Testing ... (interrupt to exit) > Event: time 1412607844.642568, type 3 (Absolute), code 0 (X), value 239= > Event: time 1412607844.642581, type 3 (Absolute), code 1 (Y), value 215= X,Y axis values increases\decreases right when I move pointer. So problem in evdev xinput driver. However I remember that I used tslib for touchscreen before. And I've added tslib and xf86-input-tslib to receipt. And I've seen this: > root@imx53qsb:~# ts_calibrate /dev/input/event3 > xres =3D 640, yres =3D 480 > tslib: Selected device uses a different version of the event protocol > than tslib was compiled for We are using custom kernel based on imx_2.6.35_maintain branch, but yocto produces kernel with same headers that our kernel. After baking image I just replace uImage of default mx53qsb with mine and all works fine! So I'm replacing one 2.6.35 image with another 2.6.35 image. But yocto compiling software with what? mainline headers or what? I think that is wrong behavior somewhere in yocto. Why yocto uses wrong headers?