[Development] iMX6 EGLGS 2D (QtWidgets) painting acceleration

[Denis Shienkov]

Ok, I have compiled my Qt 5.11.1 with native XCB painting support, using
following configure options:

-system-freetype \
-fontconfig \
-xcb-native-painting \

but I don't see any differences using the QT_XCB_NATIVE_PAINTING=1 or
without of it.
The CPU usage still is a big ~71% in both cases.

How I can know that the QT_XCB_NATIVE_PAINTING are applied?

Denis


пн, 10 сент. 2018 г. в 14:36, Denis Shienkov <denis.shienkov at gmail.com>:

> I even have added this:
>
> -xcb-native-painting \
>
> as described in qtbase/dist/changes-5.10.0 , but it has not effect too..
> no any errors printed out.
>
>
>
> пн, 10 сент. 2018 г. в 14:29, Denis Shienkov <denis.shienkov at gmail.com>:
>
>> > --feature-xcb-native-painting
>>
>> I have added this to my configure script, but it has not any effects, it
>> does not show an additional errors at configure time.
>> Besides, I have not found this 'feature-xcb-native-painting' pattern in
>> qt5 sources:
>>
>>  grep -rn . -e 'feature-xcb-native-painting'
>>
>> Denis
>>
>>
>> пн, 10 сент. 2018 г. в 14:04, Dominik Holland <
>> dominik.holland at pelagicore.com>:
>>
>>> Hi,
>>>
>>> try to pass --feature-xcb-native-painting to configure. That should
>>> enable it or atleast explain what's missing.
>>>
>>> Dominik
>>>
>>>
>>> Am 09/10/2018 um 12:59 PM schrieb Denis Shienkov:
>>> > Hi guys,
>>> >
>>> > does this mean (for Qt 5.11.1 config output):
>>> >
>>> >   X11:
>>> >     Using system-provided XCB libraries .. no
>>> >     EGL on X11 ........................... yes
>>> >     Xinput2 .............................. no
>>> >     XCB XKB .............................. yes
>>> >     XLib ................................. yes
>>> >     XCB render ........................... yes
>>> >     XCB GLX .............................. yes
>>> >     XCB Xlib ............................. yes
>>> >     Using system-provided xkbcommon ...... no
>>> >     Native painting (experimental) ....... no
>>> >
>>> > that this required *native painting* feature is not configured
>>> > successfully?
>>> >
>>> > Denis
>>> >
>>> > чт, 6 сент. 2018 г. в 0:02, Thiago Macieira <thiago.macieira at intel.com
>>> > <mailto:thiago.macieira at intel.com>>:
>>> >
>>> >     On Wednesday, 5 September 2018 12:57:39 PDT Uwe Rathmann wrote:
>>> >     > On Wed, 05 Sep 2018 09:55:41 -0700, Thiago Macieira wrote:
>>> >     > >> It also raises questions about the status of the X11 paint
>>> >     engine.
>>> >     > >> Several bugs have been closed because of not fixing the X11
>>> paint
>>> >     > >> engine anymore.
>>> >     > >
>>> >     > > This being the reason why the X11 engine is not good for
>>> everyone.
>>> >     >
>>> >     > O.k. - but that does not answer my question regarding the status
>>> >     of the
>>> >     > code ?
>>> >
>>> >     I'm guessing it's
>>> >     "Experimental, use at your own risk, please report bugs, don't
>>> >     expect quick
>>> >     turnaround time."
>>> >
>>> >     --
>>> >     Thiago Macieira - thiago.macieira (AT) intel.com <http://intel.com
>>> >
>>> >       Software Architect - Intel Open Source Technology Center
>>> >
>>> >
>>> >
>>> >     _______________________________________________
>>> >     Development mailing list
>>> >     Development at qt-project.org <mailto:Development at qt-project.org>
>>> >     http://lists.qt-project.org/mailman/listinfo/development
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > Development mailing list
>>> > Development at qt-project.org
>>> > http://lists.qt-project.org/mailman/listinfo/development
>>>
>>> _______________________________________________
>>> Development mailing list
>>> Development at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/development
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20180910/bbe66f4b/attachment.html>