All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 27339] New: Problem with stale cliprects from the classic r300 in r300g
Date: Sat, 27 Mar 2010 00:09:26 -0700 (PDT)	[thread overview]
Message-ID: <bug-27339-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: Problem with stale cliprects from the classic r300 in
                    r300g
           Product: Mesa
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/r300
        AssignedTo: dri-devel@lists.sourceforge.net
        ReportedBy: Mathias.Froehlich@web.de


Hi,

When using the classic r300 driver together with r300g in the same session, the
cliprect registers used to clip the viewport in classic r300 seem to bleed into
the r300g environment.
The problem I observe is that when I start an application with the classic r300
driver and stop that  application. Then switch to the r300g driver by setting
the LIBGL_DRIVERS_PATH environment variable, the r300g context is always
clipped to the viewport of the previous classic r300 viewport.
This happens on my mesa test account which uses non composited X11 on rawhide.

The attached patch fixes this by initializing these clip rects on context
startup.
I am not sure which registers should be initialized by which different
component, which means I am not sure if this is the right place to fix this.
But I provide that here as a hopefully good hint what goes wrong.

Please fix

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
--

             reply	other threads:[~2010-03-27  7:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-27  7:09 bugzilla-daemon [this message]
2010-03-27 13:57 ` [Bug 27339] Problem with stale cliprects from the classic r300 in r300g bugzilla-daemon
2010-03-27 15:07 ` bugzilla-daemon
2010-03-27 16:09 ` bugzilla-daemon
2010-03-27 21:19 ` bugzilla-daemon
2010-03-27 21:49 ` bugzilla-daemon
2010-03-28  7:34 ` bugzilla-daemon
2010-03-28  7:57 ` 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-27339-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.sourceforge.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 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.