http://bugs.freedesktop.org/show_bug.cgi?id=27339





--- Comment #2 from Mathias Fröhlich <mathias.froehl...@web.de>  2010-03-27 
08:07:58 PST ---
(In reply to comment #1)
> I think the classic driver shouldn't set those regs on KMS. Some time ago I
> removed the emission of the regs in classic and it didn't really add any
> regressions.

Hmm, looking again deeper into the code I just observed that r300 used
R300_CLIPRECT* to do scissor clipping to viewport boundaries whereas r300g uses
R300_SCISSOR*.

> Please try this:
> Change src/gallium/drivers/r300/r300_state_invariant.c:134 to:
> 
>     OUT_CS_REG(R300_SC_CLIP_RULE, 0);
> 
> and please let me know if it helps.
> 
I have reverted to master and applied that change but:
That does not help.
With that change the whole window is not painted at all - you just see stale
buffer content.
I believe that this value is some kind of bitmask to tell the card which side
of the R300_CLIPRECT* coordinate to clip away.
It appeared to me that you can not easily switch those off, rather than just
'clip the other side'. ... not looked into the documentation.

Don't know if r300 should or should not use these registers, but it seems to me
that r300 just still uses them as well as the kms kernel lets r300 classic set
those registers.

So altogether It would be good to have something that helps testing r300g as an
alternative to r300 classic in an easy way.

Greetings

Mathias


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to