On 2013.01.15 at 16:26 +0100, Michel Dänzer wrote:
> On Die, 2013-01-15 at 16:23 +0100, Markus Trippelsdorf wrote:
> > On 2013.01.15 at 15:43 +0100, Michel Dänzer wrote:
> > > On Sam, 2013-01-05 at 11:41 +0100, Markus Trippelsdorf wrote:
> > > > On 2012.12.20 at 14:58 +0100, Markus Trippelsdorf wrote:
> > > > >
> > > > > And just in case it got lost in the noise yesterday:
> > > > > The image corruption is caused by Dave's commit:
> > > > >
> > > > > commit dd54fee7d440c4a9756cce2c24a50c15e4c17ccb
> > > > > Author: Dave Airlie <airl...@redhat.com>
> > > > > Date: Fri Dec 14 21:04:46 2012 +1000
> > > > >
> > > > > radeon: fix regression with eviction since evict caching changes
> > > > >
> > > > > Reverting it 'fixes' the issue.
> > > >
> > > > Ping.
> > > > The issue still happens with todays Linus git tree.
> > >
> > > Does the corruption also occur with
> > > dd54fee7d440c4a9756cce2c24a50c15e4c17ccb applied manually on top of
> > > 0d0b3e7443bed6b49cb90fe7ddc4b5578a83a88d?
> >
> > No.
>
> So, can you bisect which change between those two actually introduced
> the corruption?
86a1881d08f65a42c17071a59c0088dbe2870246 is the first bad commit
commit 86a1881d08f65a42c17071a59c0088dbe2870246
Author: Jerome Glisse <jgli...@redhat.com>
Date: Wed Dec 12 16:43:15 2012 -0500
drm/radeon: fix fence driver for dma ring when wb is disabled
The dma ring can't write to register thus have to write to memory
its fence value. This ensure that it doesn't try to use scratch
register for dma ring fence driver.
Should fix:
https://bugs.freedesktop.org/show_bug.cgi?id=58166
Signed-off-by: Jerome Glisse <jgli...@redhat.com>
Reviewed-by: Alex Deucher <alexander.deuc...@amd.com>
--
Markus
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
