Re: [meta-fsl-demos][PATCH 1/2] qt-in-industrial-embedded-common: add init script for the smarthome demo

[Eric Nelson <eric.nelson@boundarydevices.com>]

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
> <eric.nelson@boundarydevices.com> wrote:
>> On 02/03/2014 07:44 AM, Rogerio Nunes wrote:
>>> On Fri, Jan 31, 2014 at 8:26 AM, Mario Domenech Goulart
>>> <mario@ossystems.com.br> 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