From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 32511] glDrawPixels broken on savage
Date: Thu, 6 Jan 2011 15:15:01 -0800 (PST) [thread overview]
Message-ID: <20110106231502.6E06213004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-32511-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=32511
--- Comment #7 from Tormod Volden <bugzi09.fdo.tormod@xoxy.net> 2011-01-06 15:15:01 PST ---
I googled up a discussion I had 9 months ago and have totally forgotten about
(scary), which points to format reworks causing the regression:
(dri-devel-2010-04-15.log)
11:50 #dri-devel: < tormod> when a GL-application splats blue spots into other
windows (savage, no compiz), is that likely a drm bug?
11:52 #dri-devel: <+ajax> savage! retro.
11:54 #dri-devel: <+ajax> it's likely to be a bug in the dri driver
12:28 #dri-devel: < eosie> how large are these blue spots?
12:29 #dri-devel: < tormod> eosie, I'll try to get a screenshot
12:34 #dri-devel: < tormod> eosie, http://imagebin.ca/view/ZNojCc4.html
12:38 #dri-devel: < eosie> cool
12:40 #dri-devel: < agd5f> tormod: tiling issue
12:41 #dri-devel: < agd5f> I suspect somthing isn't using the right aperture
12:42 #dri-devel: < agd5f> IIRC, savage had several apertures exposed via the
PCI BARs
12:42 #dri-devel: < agd5f> the first was the linear view, the others were tiled
12:45 #dri-devel: < tormod> I am not using that savage laptop much any longer,
but I think this is new since mesa 7.6
12:45 #dri-devel: < agd5f> tormod: I'd guess a problem is the savage span code
12:46 #dri-devel: < agd5f> *in
12:46 #dri-devel: < tormod> where is the span code?
12:46 #dri-devel: < agd5f> savage_span.c
12:46 #dri-devel: < agd5f> IIRC
12:47 #dri-devel: < agd5f> but it's been ages since I looked at savage
12:47 #dri-devel: < tormod> it's been ages since anyone looked at it :)
12:48 #dri-devel: < agd5f> probably one of the format reworks broke something
12:54 #dri-devel: < tormod> yes I remember format reworks broke some other
stuff, that got fixed
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-01-06 23:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-19 21:11 [Bug 32511] New: glDrawPixels broken on savage bugzilla-daemon
2010-12-19 21:13 ` [Bug 32511] " bugzilla-daemon
2010-12-19 21:14 ` bugzilla-daemon
2010-12-19 21:15 ` bugzilla-daemon
2010-12-19 21:18 ` bugzilla-daemon
2010-12-20 18:34 ` bugzilla-daemon
2010-12-20 18:53 ` bugzilla-daemon
2010-12-22 0:39 ` bugzilla-daemon
2011-01-06 23:01 ` bugzilla-daemon
2011-01-06 23:15 ` bugzilla-daemon [this message]
2011-01-06 23:31 ` bugzilla-daemon
2011-01-08 12:09 ` bugzilla-daemon
2011-01-08 22:40 ` bugzilla-daemon
2011-01-09 12:42 ` bugzilla-daemon
2011-01-17 21:57 ` bugzilla-daemon
2011-01-25 19:23 ` bugzilla-daemon
2011-02-12 12:13 ` bugzilla-daemon
2011-04-03 21:43 ` bugzilla-daemon
2011-04-05 14:53 ` bugzilla-daemon
2011-06-14 21:32 ` 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=20110106231502.6E06213004E@annarchy.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;
as well as URLs for NNTP newsgroup(s).