All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: "Dieter Nützel" <Dieter@nuetzel-hh.de>,
	"Alex Deucher" <alexdeucher@gmail.com>
Cc: Dri Devel <dri-devel@lists.freedesktop.org>
Subject: Re: r600 - NI/Turks: flickering with 'geom-outlining-150'
Date: Wed, 25 Feb 2015 17:31:01 +0900	[thread overview]
Message-ID: <54ED8845.4020409@daenzer.net> (raw)
In-Reply-To: <6a40c14e9bed496a781aebf8715f7c5e@mail.ud03.udmedia.de>

On 25.02.2015 13:04, Dieter Nützel wrote:
> Am 20.02.2015 17:29, schrieb Alex Deucher:
>> On Fri, Feb 20, 2015 at 10:54 AM, Dieter Nützel <Dieter@nuetzel-hh.de>
>> wrote:
>>> 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?
>>>
>>
>> Please narrow it down to what update caused the issue and then use git
>> to bisect.
>>
>> Alex
> 
> Couldn't find a GOOD version (Mesa/LLVM) for bisect start so far.
> I've to search further.

Note that the r600g driver doesn't use LLVM for graphics shader
compilation, so you should only need to search in Mesa and maybe the
kernel or libdrm.


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-02-25  8:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 15:54 r600 - NI/Turks: flickering with 'geom-outlining-150' Dieter Nützel
2015-02-20 16:29 ` Alex Deucher
2015-02-25  4:04   ` Dieter Nützel
2015-02-25  8:31     ` Michel Dänzer [this message]
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=54ED8845.4020409@daenzer.net \
    --to=michel@daenzer.net \
    --cc=Dieter@nuetzel-hh.de \
    --cc=alexdeucher@gmail.com \
    --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.