All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 35312] New: r600g: Automatic mipmap generation doesn't work properly
Date: Mon, 14 Mar 2011 13:04:35 -0700 (PDT)	[thread overview]
Message-ID: <bug-35312-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: r600g: Automatic mipmap generation doesn't work
                    properly
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: wielkiegie@gmail.com


Automatic mipmap generation using glGenerateMipmap (util_gen_mipmap) fills
mipmaps with wrong rendering. Piglit tests fbo-generatemipmap* are failing.
Software fallback works properly, as does llvmpipe.

Hardware:
rv670 (HD3870), amd64
Software:
kernel 2.6.38rc8, mesa from git, libdrm from git

-- 
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:[~2011-03-14 20:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 20:04 bugzilla-daemon [this message]
2011-04-14  5:36 ` [Bug 35312] r600g: Automatic mipmap generation doesn't work properly bugzilla-daemon
2011-04-15  7:40 ` bugzilla-daemon
2011-04-15 11:30 ` bugzilla-daemon
2011-04-16  7:08 ` bugzilla-daemon
2011-05-06  5:57 ` bugzilla-daemon
2011-05-11  9:00 ` bugzilla-daemon
2011-05-11 16:15 ` 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-35312-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.