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 Rogerio,

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:
>> Hi Eric,
>>
>> Sorry for taking so long to reply.  Please, see some comments below.
>>
>> On Mon, 27 Jan 2014 17:41:37 -0700 Eric Nelson <eric.nelson@boundarydevices.com> wrote:
>>
>>> On 01/17/2014 07:02 AM, Mario Domenech Goulart wrote:
>>>> Currently, qt-in-industrial-embedded starts no demo automatically when
>>>> installed.  This patch adds an init script so that the smarthome demo
>>>> can be automatically started on boot.
>>>>
>>>>  <snip>
>>>>
>>>> +SRC_URI = "git://gitorious.org/qt-in-use/qt-in-industrial-embedded.git \
>>>> +           file://smarthome \
>>>> +          "
>>>>
>>>>    PR = "r3"
>>>>
>>>> @@ -18,6 +20,10 @@ do_configure_prepend() {
>>>>    do_install_append () {
>>>>        # Set the correct smarthome binary path
>>>>        sed -i -e 's:Exec=.*:Exec=${bindir}/smarthome:g' ${D}${datadir}/applications/smarthome.desktop
>>>
>>> This should only be installed when not using X, right?
>>
>> I'm not sure.  I actually haven't touched that recipe part.
>>
>>
>>>> +
>>>> +    install -d ${D}${sysconfdir}/init.d
>>>> +    install -m 755 ${WORKDIR}/smarthome ${D}${sysconfdir}/init.d/
>>>> +    sed -i -e 's:__BINDIR__:${bindir}:g; s:__SYSCONFDIR__:${sysconfdir}:g' ${D}${sysconfdir}/init.d/smarthome
>>>>    }
>>>>
>>>
>>> When testing using fsl-image-gui on the master branch today, I
>>> immediately got a ts_calibrate prompt on my HDMI monitor, which was
>>> frustrating since it doesn't happen to have a touch screen.
>>>
>>> Please advise,
>>
>> It seems that packagegroup-core-tools-testapps is dragging
>> tslib-calibrate into the image (via RDEPENDS).
>> packagegroup-core-tools-testapps is added to the image because
>> fsl-image-gui.bb has
>>
>>      SOC_EXTRA_IMAGE_FEATURES ?= "tools-testapps"
>>
>>      EXTRA_IMAGE_FEATURES += " \
>>         ${SOC_EXTRA_IMAGE_FEATURES} \
>>         ...
>>
>> The "tools-testapps" feature makes core-image.bbclass add
>> packagegroup-core-tools-testapps to the image.
>>
>> To work around that, you can add
>>
>>     EXTRA_IMAGE_FEATURES_remove = "tools-testapps"
>>
>> to local.conf.  However, a bunch of other packages will be removed from
>> the image (don't know if they are relevant for your purposes, though --
>> they sould be "testapps").
>
> Actually packagegroup-fsl-tools-testapps is explicitly included in
> IMAGE_INSTALL...
>
>>
>> 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 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.

Regards,


Eric