All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28614] New: [r300g] Hypertorus hack from XScreenSaver has triangles visible
Date: Sat, 19 Jun 2010 07:42:57 -0700 (PDT)	[thread overview]
Message-ID: <bug-28614-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=28614

           Summary: [r300g] Hypertorus hack from XScreenSaver has
                    triangles visible
           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.freedesktop.org
        ReportedBy: jlp.bugs@gmail.com


Created an attachment (id=36367)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=36367)
hypertorus.png

Today I've pulled and recompiled Mesa from git and noticed a regression since
the 2010-06-14. The hypertorus hack from XScreenSaver has triangles visible on
strips, that were not visible before. This is on HP Compaq nx6325 laptop with
integrated graphics with RS482. The same problem does not happen on my desktop
computer with Radeon 9600 Pro (RV350 AR).

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2010-06-19 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-19 14:42 bugzilla-daemon [this message]
2010-06-19 14:50 ` [Bug 28614] [r300g] Hypertorus hack from XScreenSaver has triangles visible bugzilla-daemon
2010-06-19 17:27 ` bugzilla-daemon
2010-06-19 19:08 ` [Bug 28614] [Gallium/Draw][r300g] " 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-28614-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --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.