[Interest] redirecting Qt pixel data to designated buffer
Thiago Macieira
thiago.macieira at intel.com
Tue Jan 6 17:27:13 CET 2015
On Tuesday 06 January 2015 17:10:35 Selmeci, Tamás wrote:
> On Tue, 2015-01-06 at 07:56 -0800, Thiago Macieira wrote:
> > > Maybe the best would be to refactor 'linuxfb' so it doesn't write
> > > to /dev/fb*, but to my buffer. I'm just hesitating to begin this work
> > > until someone says there's no simpler solution...
> >
> > You'll probably need that and patching Mesa too.
>
> At this phase of development my intention is to disable any OpenGL etc.
> extension of Qt to force it to use software rendering/blitting. Why do I
> have to patch Mesa (which is a kind of OpenGL implementation if I'm not
> wrong) if my Qt doesn't use OpenGL/EGL at all?
See what Shawn said:
"QtQuick 2 items have no built-in support for rendering via QPainter, so it
normally doesn’t work without OpenGL."
Qt as a whole doesn't require OpenGL. Qt Quick 2 does and you mentioned Qt
Quick 2 classes that you wanted to use. So you have to make a choice here.
> In a very simplyfied approach, what I only have to do in 'linuxfb'
> platform plugin is copying the buffer data not to /dev/fb*, but into my
> buffer... is it correct?
I don't know.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
More information about the Interest
mailing list