From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jagan Teki <jagannadh.teki@gmail.com>
Date: Wed, 8 Mar 2017 16:30:19 +0530
Subject: [Buildroot] QT5.8 buid failure on master
In-Reply-To: <CAAMH-ytGnurAFt=BcfK53qJ8OR09o8LAZK2UdCH7nO-1Q=2aQg@mail.gmail.com>
References: <CAOMZO5D_R7_zEzL-X2zPViU+-SZ060JA3hpnE9S01x2PRazUsQ@mail.gmail.com>
 <trinity-a4f8806b-d789-4dea-928a-2d7bb2fad531-1488871993989@3capp-gmx-bs12>
 <20170307114826.lend2f2evnob3lya@t450s.lan>
 <trinity-b0ce3807-d5c4-4ccf-9b54-628667f6d805-1488895453975@3capp-gmx-bs26>
 <CAD6G_RQiqhvnYX3L9wh64K5inCSNr4G-vPDzU_9BbLqzrw=fyQ@mail.gmail.com>
 <CAOMZO5CPz7tLtLeLpC82koCrWx-gYRUGrZ-v-qjuZOZ3wbkaXw@mail.gmail.com>
 <20170307202950.61328dd5@gmx.net>
 <CAAMH-ytGnurAFt=BcfK53qJ8OR09o8LAZK2UdCH7nO-1Q=2aQg@mail.gmail.com>
Message-ID: <CAD6G_RQGO966C1cxp6gG05xC0vu72uUDH56AJEoDi=R8wJMzOA@mail.gmail.com>
List-Id: <buildroot.busybox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: buildroot@busybox.net

Hi Garry,

On Wed, Mar 8, 2017 at 4:15 PM, Gary Bisson
<gary.bisson@boundarydevices.com> wrote:
> Hi Peter, Fabio, All,
>
> On Tue, Mar 7, 2017 at 8:29 PM, Peter Seiderer <ps.report@gmx.net> wrote:
>> Hello Fabio,
>>
>> On Tue, 7 Mar 2017 13:57:39 -0300, Fabio Estevam <festevam@gmail.com> wrote:
>>
>>> Hi Jagan,
>>>
>>> On Tue, Mar 7, 2017 at 1:15 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>>>
>>> > Able to see the application but 'Black screen' on 'Lord of the Ring' widget
>>>
>>> Thanks for testing.
>>>
>>> I think we should treat this issue on a separate thread as I also see
>>> the same with Qt5.6.2.
>>>
>>> It seems we made progress with Qt5.8 with Peter's patches.
>>>
>>> Peter,
>>>
>>> Do you plan to submit your two patches formally?
>>
>> Yes can do. No problem with the first one, for the second one I need
>> to investigate first on which additional configure option the building
>> of libQt5EglFsKmsSupport.so depends...
>
> Actually I wonder why the first patch is needed in this case. How does
> the eglfs plugin build for Vivante for instance since the failure
> happens in a common file?
>
> Otherwise, I confirm I have "black picture" issues on Qt5.8 with the
> Cinematic demo.
>
> However, I've made a discovery regarding the DRI configuration (to
> avoid hardcoding the device). It is actually documented well on Qt
> website:
> http://doc.qt.io/qt-5/embedded-linux.html#eglfs-with-eglfs-kms-backend
> "The KMS/DRM backend also supports custom configurations via a JSON
> file. Set the environment variable QT_QPA_EGLFS_KMS_CONFIG to the name
> of the file to enable this."
>
> Here is my JSON file for Hannstar display:
> {
>   "device": "/dev/dri/card1",
>   "hwcursor": false,
>   "pbuffers": true,
>   "outputs": [
>     {
>       "name": "VGA-1",
>       "mode": "off"
>     },
>     {
>       "name": "HDMI-1",
>       "mode": "off"
>     },
>     {
>       "name": "LVDS-1",
>       "mode": "1024x768"
>     }
>   ]
> }
>
> This avoids the patch mentioned before:
> http://lists.busybox.net/pipermail/buildroot/2017-March/185842.html

Don't know but I never find to explicitly mentioned the kmscube ran
w/o any device argument for 5.6.2 and 5.8

thanks!
-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.