From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id F28DDE00566 for ; Mon, 3 Feb 2014 10:11:51 -0800 (PST) Received: by mail-pb0-f54.google.com with SMTP id uo5so7366234pbc.13 for ; Mon, 03 Feb 2014 10:11:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=LxFxMEz940nwLf2U0BS+GithWs/9FE711gxAXMoxHYY=; b=cYLoPRJDE8d3xQmBGJJoEaRu/3r2m9zvb+3H8tvjBxv1KpoZQ0tH1H7AB8UT52YPw3 6PtQDAKkyaKfyk/BVpiTV6fGsM9R+1w1nFzfpN0hdXhZ2bdYnFImt2udS0+of++bI0Yv SGpuPDd5sOER/AxStqczgu1rD2JpMRovNnGBRdSTfArDUt3sFUtrpk+6AK41UtxbxWt8 y/dmZvtfxqZUvhamALv3NrSicC+FZJquCHotscj++dAVx8dzKfvmOpRtCccUgcq8u4VR akQpky3MGTcNzed7r+uPt4OyKE4Tdo6AnoISsDB6ZVueFU6ZiUIY1xJxBuzePqLSzcVW gW+w== X-Gm-Message-State: ALoCoQlYgYMWKqRX4r1v08gyxgsPYJRsAHYPc5BuR+jvOPBypxvlE+ZkGy09JCSxkyXfYCxn8IWi X-Received: by 10.68.162.66 with SMTP id xy2mr38904904pbb.46.1391451111237; Mon, 03 Feb 2014 10:11:51 -0800 (PST) Received: from [192.168.0.53] ([63.226.49.26]) by mx.google.com with ESMTPSA id xn12sm150423640pac.12.2014.02.03.10.11.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Feb 2014 10:11:49 -0800 (PST) Message-ID: <52EFDBE1.1040709@boundarydevices.com> Date: Mon, 03 Feb 2014 11:11:45 -0700 From: Eric Nelson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Otavio Salvador References: <1389967366-2718-1-git-send-email-mario@ossystems.com.br> <52E6FCC1.3030009@boundarydevices.com> <87y51wxoy8.fsf@parenteses.org> <52EFD1FF.7080800@boundarydevices.com> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" Subject: Re: [meta-fsl-demos][PATCH 1/2] qt-in-industrial-embedded-common: add init script for the smarthome demo 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, 03 Feb 2014 18:11:53 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Otavio, On 02/03/2014 10:38 AM, Otavio Salvador wrote: > Hello Eric, > > On Mon, Feb 3, 2014 at 3:29 PM, Eric Nelson > wrote: >> On 02/03/2014 07:44 AM, Rogerio Nunes wrote: >>> On Fri, Jan 31, 2014 at 8:26 AM, Mario Domenech Goulart >>> wrote: >>>> I suppose packagegroup-core-tools-testapps should check for >>>> "touchscreen" in MACHINE_FEATURES to avoid the dependency on tslib for >>>> boards that don't have touch devices. >>> >>> >>> Agree. >>> >> >> I suspect that this leaves us in the same position, since essentially >> all i.MX6 boards support some form of touch screen, yet they can >> also be used without touch (e.g. with HDMI + mouse/keyboard), right? >> >> It seems that a run-time test may be the right thing here for the >> most common case. On our Nitrogen boards, and I expect on Freescale >> boards with Hannstar displays, we could test /dev/input/ to see >> whether a a touch screen is present because the I2C touch controller >> is essentially a part of the display. > > This is handled already. If no /dev/input/touchscreen0 is found it > will not start the ts_calibrate. > Hmmm. I'll have to re-test this. I thought I saw ts_calibrate running on a Nitrogen6X, though it may have been Nitrogen6_Lite. >> This doesn't work on other boards like our Nitrogen6_Lite though. >> On that board, a resistive touch controller is a part of the main >> board, so a touch-screen input device will be present even if no >> touch screen is physically connected. > > This complicates things. I also see another missing point in the > puzzle ... we cannot decide if we intend to use tslib or xinput. > Right. Does a machine saying it **supports** tslib mean that it always wants it? > Do you have any idea how we can workaround it in Nitrogen6_Lite case? > In general, we've been moving away from tslib for use with X. Since all of our machines support Android, we've added kernel-driver calibration to each of the resistive touch drivers we support, and only want tslib when the target image doesn't include X (Qt, DirectFB). It seems that at a minimum, there should be a way to disable the automatic ts_calibrate in X startup. Regards, Eric