dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 50325] Glyphy bad render on r600g (software render is fine) - too many registers?
Date: Fri, 01 Jul 2016 13:31:15 +0000	[thread overview]
Message-ID: <bug-50325-502-RQU67RJrtr@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-50325-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 380 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=50325

--- Comment #7 from cyberkm@gmail.com ---
Yep, latest mesa git.

05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Antilles [Radeon HD 6990]

mesa r600 gallium.

The app works fine if i switch to software renderer.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1187 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-07-01 13:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 21:56 [Bug 50325] New: Glyphy bad render on r600g (software render is fine) bugzilla-daemon
2012-05-24 21:57 ` [Bug 50325] " bugzilla-daemon
2012-05-24 21:57 ` bugzilla-daemon
2012-05-25  7:22 ` bugzilla-daemon
2012-05-26  8:52 ` [Bug 50325] Glyphy bad render on r600g (software render is fine) - too many registers? bugzilla-daemon
2016-06-24 12:56 ` bugzilla-daemon
2016-06-24 15:42 ` bugzilla-daemon
2016-07-01 13:31 ` bugzilla-daemon [this message]
2017-10-08 16:11 ` bugzilla-daemon
2018-03-06 18:33 ` bugzilla-daemon
2018-03-06 18:41 ` 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-50325-502-RQU67RJrtr@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