All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85696] r600g+nine: Bioshock shader failure after 7b1c0cbc90d456384b0950ad21faa3c61a6b43ff
Date: Mon, 08 Dec 2014 23:09:42 +0000	[thread overview]
Message-ID: <bug-85696-502-cKllLUGnFH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-85696-502@http.bugs.freedesktop.org/>


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

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

--- Comment #6 from David Heidelberg (okias) <david@ixit.cz> ---
In testing repository [1] fixed by commit:

st/nine: Rewrite LOOP implementation, and a0 aL handling

Now it also passes wine tests without killing driver (r600g).


[1] https://github.com/iXit/Mesa-3D/commits/master

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

[-- Attachment #1.2: Type: text/html, Size: 1308 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

  parent reply	other threads:[~2014-12-08 23:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 12:08 [Bug 85696] New: [regression] r600g+nine: Bioshock shader failure after recent changes bugzilla-daemon
2014-10-31 12:19 ` [Bug 85696] " bugzilla-daemon
2014-10-31 12:53 ` bugzilla-daemon
2014-10-31 13:29 ` bugzilla-daemon
2014-10-31 16:51 ` [Bug 85696] [regression] r600g+nine: Bioshock shader failure after 7b1c0cbc90d456384b0950ad21faa3c61a6b43ff bugzilla-daemon
2014-11-01 23:43 ` bugzilla-daemon
2014-11-20  1:17 ` [Bug 85696] " bugzilla-daemon
2014-11-20  1:29 ` bugzilla-daemon
2014-12-08 23:09 ` bugzilla-daemon [this message]
2015-02-06  1:48 ` 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-85696-502-cKllLUGnFH@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 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.