dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dieter Nützel" <Dieter@nuetzel-hh.de>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "Michel Dänzer" <michel@daenzer.net>,
	"Dri Devel" <dri-devel@lists.freedesktop.org>
Subject: r600 - NI/Turks: flickering with 'geom-outlining-150'
Date: Fri, 20 Feb 2015 16:54:07 +0100	[thread overview]
Message-ID: <2fcea8124ecd2280f4fd137fb208e4ba@mail.ud03.udmedia.de> (raw)

Hello Alex,

I get _today_ flickering with Mesa-demo 'geom-outlining-150'.
It worked OK last night and I've reseted Mesa git back to 5c1aac1 but NO 
success.
Only thing is I've used LLVM  git of today, too and for GOOD result LLVM 
from 18th.
Any hints?

For the record:

'geom-outlining-150'
'gsraytrace' (both Mesa-demo)
and
'gl-320-primitive-shading' (ogl-samples)

GS stuff works on r600 - NI/Turks nearly perfect (only the above 
flickering) which show corruption (first and last) or crash 'gsraytrace' 
with r600 - RV730 (AGP).

Maybe I've to add this on the open bug reports...

Great 'experience' with Evergreen+ on PCIE (Xeon X3430/16GB/all 
SSD/Fujitsu PRIMERGY TX150 S7 server-workstation) ;-)

-Dieter

PS I use ccache linked to /dev/shm/.ccache for LLVM as Michel suggested.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2015-02-20 15:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 15:54 Dieter Nützel [this message]
2015-02-20 16:29 ` r600 - NI/Turks: flickering with 'geom-outlining-150' Alex Deucher
2015-02-25  4:04   ` Dieter Nützel
2015-02-25  8:31     ` Michel Dänzer
2015-02-25 21:50       ` Dieter Nützel
2015-02-26  6:40         ` Dieter Nützel

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=2fcea8124ecd2280f4fd137fb208e4ba@mail.ud03.udmedia.de \
    --to=dieter@nuetzel-hh.de \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=michel@daenzer.net \
    /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