From: "Mike Folcik" <mike@folcik.com>
To: <meta-freescale@yoctoproject.org>
Subject: Any hope of vblank-synchronized rendering (from vivante) on i.MX6 soon?
Date: Thu, 2 Oct 2014 10:21:52 -0600 [thread overview]
Message-ID: <005d01cfde5c$fa0039b0$ee00ad10$@folcik.com> (raw)
I have been up against this problem for a few weeks now, and it is
definitely a show stopper for me using the i.MX6 for my application. I,
too, am using Chromium atop X11 and need smooth CSS3 accelerated animations.
I have seen the Bugzilla bug; and am wondering, is this definitely in the
pipeline for the 1.8 release? Is there any chance to increase the severity
to get it sooner?
From Gerard's original post, this IS a critical defect. My application is
high volume, and I'm sure others interested in this defect also have high
volume, which should motivate Freescale & Vivante to act on this.
Mike
next reply other threads:[~2014-10-02 17:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 16:21 Mike Folcik [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-23 4:31 Any hope of vblank-synchronized rendering (from vivante) on i.MX6 soon? Gerard Bucas
2014-09-23 11:45 ` Daiane Angolini
2014-09-23 13:04 ` Gerard Bucas
2014-09-23 13:09 ` Daiane Angolini
2014-09-23 14:00 ` Carlos Rafael Giani
2014-09-23 14:29 ` Eric Nelson
2014-09-23 14:31 ` Gerard Bucas
2014-09-23 14:50 ` Daiane Angolini
2014-09-23 14:55 ` Carlos Rafael Giani
2014-09-23 16:48 ` Prabhu S
[not found] ` <9623C504-372D-4750-9A84-7A8ADF7679A3@tames.com>
2014-09-23 17:51 ` Carlos Rafael Giani
2014-09-23 17:52 ` Carlos Rafael Giani
2014-09-23 18:46 ` Eric Nelson
2014-09-23 18:50 ` Prabhu S
2014-09-23 19:35 ` Eric Nelson
2014-09-23 20:09 ` Carlos Rafael Giani
2014-09-24 15:36 ` Daiane Angolini
2014-09-25 10:03 ` Carlos Rafael Giani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='005d01cfde5c$fa0039b0$ee00ad10$@folcik.com' \
--to=mike@folcik.com \
--cc=meta-freescale@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.