From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 69543] New: Radeon EXAPixmaps don't work with stretched XRender pictures
Date: Wed, 18 Sep 2013 18:56:53 +0000 [thread overview]
Message-ID: <bug-69543-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1121 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69543
Priority: medium
Bug ID: 69543
Assignee: dri-devel@lists.freedesktop.org
Summary: Radeon EXAPixmaps don't work with stretched XRender
pictures
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: jujibo@gmail.com
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
There is garbage on screen with some stretched XRender pictures with radeon
driver and enabled EXAPixmaps, see for example MSEide without xorg.conf
http://sourceforge.net/projects/mseide-msegui/
MSEgui uses stretched one pixel width or height pixmaps in order to draw linear
color gradients.
If you add Option "EXAPixmaps" "off" in Section "Device" of xorg.conf display
is OK but performance falls.
Same problem using NOUVEAU driver. I can't figure out how disable EXAPixmaps
for nouveau driver.
Reproducible: Always
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2508 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-09-18 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 18:56 bugzilla-daemon [this message]
2013-09-18 19:11 ` [Bug 69543] Radeon EXAPixmaps don't work with stretched XRender pictures bugzilla-daemon
2013-09-18 19:12 ` bugzilla-daemon
2013-09-18 19:13 ` bugzilla-daemon
2013-09-18 19:14 ` bugzilla-daemon
2013-09-18 19:17 ` bugzilla-daemon
2013-09-18 20:08 ` 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-69543-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;
as well as URLs for NNTP newsgroup(s).