dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36608] New: Corrupt GL rendering
Date: Tue, 26 Apr 2011 08:10:41 -0700 (PDT)	[thread overview]
Message-ID: <bug-36608-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: Corrupt GL rendering
           Product: Mesa
           Version: git
          Platform: IA64 (Itanium)
        OS/Version: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/Gallium/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: emeric.maschino@gmail.com


Created an attachment (id=46090)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=46090)
Screenshot showing corrupt GL rendering in glxgears as an example

Hi,

I was asked there (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622299#67)
to report this bug upstream.

GL rendering is currently corrupt on IA-64 with Gallium r300 driver (cf.
attached screenshot with running glxgears as an example). Classic driver
renders display correctly.

Regards,

    Émeric

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2011-04-26 15:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-26 15:10 bugzilla-daemon [this message]
2011-05-09 13:57 ` [Bug 36608] Corrupt GL rendering bugzilla-daemon
2011-08-18 23:25 ` bugzilla-daemon
2011-08-18 23:26 ` bugzilla-daemon
2011-08-19  7:30 ` bugzilla-daemon
2011-09-12 18:35 ` 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-36608-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox