Done. See https://bugzilla.yoctoproject.org/show_bug.cgi?id=6760
On 2014-09-24 17:36, Daiane Angolini wrote:
On Tue, Sep 23, 2014 at 5:09 PM, Carlos Rafael Giani
d...@pseudoterminal.org wrote:
While this is correct for output that is drawn directly to the framebuffer
(with damage regions
On Tue, Sep 23, 2014 at 5:09 PM, Carlos Rafael Giani
d...@pseudoterminal.org wrote:
While this is correct for output that is drawn directly to the framebuffer
(with damage regions etc.), it isn't for compositor-based output, such as
what Weston does. There, it is not uncommon to repaint the
On Tue, Sep 23, 2014 at 1:31 AM, Gerard Bucas gerar...@tekmagic.net wrote:
On X.11 and Chromium there is still tearing of videos played back in
Chromium (on X11). From what I have read and been told by others this is
caused by the lack of DRI2 support in the Vivante graphics libraries (even
in
Thanks Daiane - will do.
When is the next such meeting and who is actually the interface with Vivante
that could put some pressure on them!?
DRI2 is used all over in the X11 code according to this so I think this is a
critical area to solve the serious shortcomings and performance in the
On Tue, Sep 23, 2014 at 10:04 AM, Gerard Bucas gerar...@tekmagic.net wrote:
Thanks Daiane - will do.
When is the next such meeting and who is actually the interface with Vivante
that could put some pressure on them!?
Next meeting is going to be something near 10th, next moth, more or
Perhaps there is still time left to notify Freescale how critical this
feature is for several people. Imagine tearing on huge displays for
example ... this can easily become a showstopper. Freescale should
consider this one of the most critical features to introduce in 3.10.31 GA.
On
On 09/23/2014 07:00 AM, Carlos Rafael Giani wrote:
Perhaps there is still time left to notify Freescale how critical this
feature is for several people. Imagine tearing on huge displays for
example ... this can easily become a showstopper. Freescale should
consider this one of the most
-freescale-boun...@yoctoproject.org
[mailto:meta-freescale-boun...@yoctoproject.org] On Behalf Of Carlos Rafael
Giani
Sent: Tuesday, September 23, 2014 10:00 AM
To: meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] Any hope of vblank-synchronized rendering (from
vivante) on i.MX6 soon
On Tue, Sep 23, 2014 at 11:31 AM, Gerard Bucas gerar...@tekmagic.net wrote:
I agree Carlos!
This is a show-stopper for applications in markets like the Digital Signage
market - which could be huge for the i.MX6. The i.MX6 could be the best
media player out there but the problems related to
On 09/23/2014 04:55 PM, Carlos Rafael Giani wrote:
On 09/23/2014 04:50 PM, Daiane Angolini wrote:
On Tue, Sep 23, 2014 at 11:31 AM, Gerard Bucas
gerar...@tekmagic.net wrote:
I agree Carlos!
This is a show-stopper for applications in markets like the Digital
Signage market - which could be
i.MX6 X11 EGL is single buffered and there is no support for VSYNC. The
tearing with X11 is a known issue. We did investigate to fix this, but the
solution becomes too hacky and cannot be used in production systems.
We are adding VSYNC support in Wayland. eglSwapInterval will be supported
for
This is probably because v4l somehow uses vsync directly. Keep in mind
that v4l bypasses X11.
Also, you can use qt5 with pure framebuffer output. There, vsync works.
On 2014-09-23 19:19, Alfonso Tamés wrote:
Yes, the attached test video is tearing in EGL FB without X11/wayland.
This tears:
I wonder why it is single buffered. is it because of the memory
consumption for a second buffer? The buffers could be flipped,
eliminating any need for blits, so the memory bandwidth should not be an
issue.
On 2014-09-23 18:48, Prabhu S wrote:
i.MX6 X11 EGL is single buffered and there is no
Hi Carlos,
On 09/23/2014 10:52 AM, Carlos Rafael Giani wrote:
I wonder why it is single buffered. is it because of the memory
consumption for a second buffer? The buffers could be flipped,
eliminating any need for blits, so the memory bandwidth should not be an
issue.
There is a memory
On Tue, Sep 23, 2014 at 1:46 PM, Eric Nelson
eric.nel...@boundarydevices.com wrote:
Hi Carlos,
On 09/23/2014 10:52 AM, Carlos Rafael Giani wrote:
I wonder why it is single buffered. is it because of the memory
consumption for a second buffer? The buffers could be flipped,
eliminating
Hi Prabhu,
On 09/23/2014 11:50 AM, Prabhu S wrote:
On Tue, Sep 23, 2014 at 1:46 PM, Eric Nelson
eric.nel...@boundarydevices.com
mailto:eric.nel...@boundarydevices.com wrote:
snip
We are adding VSYNC support in Wayland. eglSwapInterval will be
supported for FBDEV and Wayland
While this is correct for output that is drawn directly to the
framebuffer (with damage regions etc.), it isn't for compositor-based
output, such as what Weston does. There, it is not uncommon to repaint
the entire screen. If it uses GLES as the backend, this is the only way
to do it, unless
17 matches
Mail list logo
