All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29851] New: [r300g] HyperZ on RS690 not work correctly
Date: Sat, 28 Aug 2010 02:45:12 -0700 (PDT)	[thread overview]
Message-ID: <bug-29851-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: [r300g] HyperZ on RS690 not work correctly
           Product: Mesa
           Version: unspecified
          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: d.okias@gmail.com


Created an attachment (id=38235)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=38235)
glxgears.jpeg

Incoretly rendering.
Kernel: 2.6.36-rc2
Mesa/libdrm/ddx: git
xorg: 1.9.0

~ $ RADEON_HYPERZ=1 glxgears
radeon: Successfully grabbed chipset info from kernel!
radeon: DRM version: 2.6.0 ID: 0x791f GB: 1 Z: 1
radeon: GART size: 509 MB VRAM size: 128 MB
radeon: HyperZ: YES
couldn't open libtxc_dxtn.so, software DXTn compression/decompression
unavailable
Mesa: Mesa 7.9-devel DEBUG build Aug 28 2010 10:23:14
Mesa warning: couldn't open libtxc_dxtn.so, software DXTn
compression/decompression unavailable
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
293 frames in 5.0 seconds = 58.480 FPS

P.S. On screenshot is glxgears area, only small part fast blinking gear

-- 
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-08-28  9:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-28  9:45 bugzilla-daemon [this message]
2010-09-02  0:10 ` [Bug 29851] [r300g] HyperZ on RS690 not work correctly bugzilla-daemon
2010-09-10 22:18 ` bugzilla-daemon
2010-09-23 10:13 ` bugzilla-daemon
2010-09-24 20:50 ` bugzilla-daemon
2010-09-27  9:12 ` bugzilla-daemon
2010-09-27  9:16 ` bugzilla-daemon
2010-12-24 20:48 ` bugzilla-daemon
2010-12-28  2:04 ` bugzilla-daemon
2011-01-23 22:19 ` bugzilla-daemon
2011-01-25  4:57 ` bugzilla-daemon
2011-01-25 14:08 ` bugzilla-daemon
2011-01-25 15:48 ` bugzilla-daemon
2011-01-25 15:49 ` bugzilla-daemon
2011-01-27 16:06 ` bugzilla-daemon
2011-01-28  0:11 ` bugzilla-daemon
2011-02-05 11:44 ` bugzilla-daemon
2011-02-28 11:34 ` 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-29851-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.