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

Otavio Salvador otavio at ossystems.com.br
Mon Feb 3 09:38:52 PST 2014


Hello Eric,

On Mon, Feb 3, 2014 at 3:29 PM, Eric Nelson
<eric.nelson at 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 at 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.

> 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.

Do you have any idea how we can workaround it in Nitrogen6_Lite case?


-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


More information about the meta-freescale mailing list