From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 77966] Trails / Tracks when rendering OpenGL ES 2 moving objects (Android-x86 / Mesa 10.0.4/5)
Date: Mon, 28 Apr 2014 23:48:18 +0000 [thread overview]
Message-ID: <bug-77966-502-zfcQB9A9Ws@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-77966-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 619 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=77966
--- Comment #8 from pstglia@gmail.com ---
Created attachment 98144
--> https://bugs.freedesktop.org/attachment.cgi?id=98144&action=edit
Patch
Thanks for the info. I did the changes attached on native_android.cpp and they
worked for me.
I based this on Martin Andersson patch (bug 72889) and on commit
6349b3235cc07d396325863ece9ca6261daf8e77.
Although it worked for me, don't know if this is the best way of doing this
fix.
Some of you guys could check it out please?
Thanks!
pstglia
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1827 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-04-28 23:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-26 12:10 [Bug 77966] New: Trails / Tracks when rendering OpenGL ES 2 moving objects (Android-x86 / Mesa 10.0.4/5) bugzilla-daemon
2014-04-26 12:13 ` [Bug 77966] " bugzilla-daemon
2014-04-26 12:15 ` bugzilla-daemon
2014-04-26 12:21 ` bugzilla-daemon
2014-04-26 12:42 ` bugzilla-daemon
2014-04-26 12:45 ` bugzilla-daemon
2014-04-26 12:45 ` bugzilla-daemon
2014-04-26 12:49 ` bugzilla-daemon
2014-04-26 12:51 ` bugzilla-daemon
2014-04-28 3:40 ` bugzilla-daemon
2014-04-28 9:03 ` bugzilla-daemon
2014-04-28 23:48 ` bugzilla-daemon [this message]
2014-05-02 3:52 ` bugzilla-daemon
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=bug-77966-502-zfcQB9A9Ws@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox