From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71789] [r300g] Visuals not found in (default) depth = 24
Date: Fri, 06 May 2016 09:48:16 +0000 [thread overview]
Message-ID: <bug-71789-502-4HkIts2MUr@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-71789-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1029 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71789
--- Comment #30 from Marek Olšák <maraeo@gmail.com> ---
(In reply to Michel Dänzer from comment #29)
> That piglit sanity is failing with the patch may confirm my suspicion that
> something doesn't add up yet I'm afraid: Since the kernel driver and
> xf86-video-ati EXA code are using the same hardware formats for
> display/rendering with BE & LE, I was wondering how the patch could result
> in both display and glReadPixels working correctly for winsys buffers. Looks
> like indeed only display works correctly, which indicates that the GPU is
> effectively writing/reading PIPE_FORMAT_x8R8G8B8_* pixels like
> PIPE_FORMAT_B8G8R8x8_* (which is what the kernel driver and EXA code are
> using).
The patch is correct from the LE perspective. It simply adds ARGB support and
was tested thoroughly on LE. The side effect is that BE can use the format now
too, but there may be other issues with BE.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1892 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-05-06 9:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 14:05 [Bug 71789] New: [r300g] Visuals not found in (default) depth = 24 bugzilla-daemon
2013-11-19 14:06 ` [Bug 71789] " bugzilla-daemon
2014-01-06 15:47 ` bugzilla-daemon
2015-06-04 3:10 ` bugzilla-daemon
2015-06-04 3:15 ` bugzilla-daemon
2015-11-18 4:11 ` bugzilla-daemon
2015-11-18 4:12 ` bugzilla-daemon
2015-11-18 4:13 ` bugzilla-daemon
2015-11-18 4:14 ` bugzilla-daemon
2015-12-19 12:16 ` bugzilla-daemon
2016-02-13 15:05 ` bugzilla-daemon
2016-02-14 13:49 ` bugzilla-daemon
2016-04-12 21:45 ` bugzilla-daemon
2016-04-25 6:06 ` bugzilla-daemon
2016-04-26 7:45 ` bugzilla-daemon
2016-04-26 19:38 ` bugzilla-daemon
2016-04-27 15:13 ` bugzilla-daemon
2016-04-27 16:55 ` bugzilla-daemon
2016-04-30 18:52 ` bugzilla-daemon
2016-05-01 10:22 ` bugzilla-daemon
2016-05-01 16:39 ` bugzilla-daemon
2016-05-02 1:02 ` bugzilla-daemon
2016-05-02 18:56 ` bugzilla-daemon
2016-05-03 1:20 ` bugzilla-daemon
2016-05-03 6:48 ` bugzilla-daemon
2016-05-05 20:07 ` bugzilla-daemon
2016-05-06 8:51 ` bugzilla-daemon
2016-05-06 9:23 ` bugzilla-daemon
2016-05-06 9:48 ` bugzilla-daemon [this message]
2016-05-08 6:17 ` bugzilla-daemon
2016-05-09 7:47 ` bugzilla-daemon
2016-05-09 11:22 ` bugzilla-daemon
2017-02-06 21:26 ` bugzilla-daemon
2017-04-08 13:01 ` bugzilla-daemon
2017-04-08 13:05 ` bugzilla-daemon
2017-04-08 16:41 ` 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-71789-502-4HkIts2MUr@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;
as well as URLs for NNTP newsgroup(s).