From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 39010] New: better handling of large pixmaps
Date: Wed, 6 Jul 2011 12:18:05 -0700 (PDT) [thread overview]
Message-ID: <bug-39010-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=39010
Summary: better handling of large pixmaps
Product: xorg
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: shiningxc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=48831)
--> (https://bugs.freedesktop.org/attachment.cgi?id=48831)
possible workaround for 64mb vram cards
Large images in Firefox only show up as black rectangles.
At the same time, the following errors appear in dmesg :
[ 590.075369] [drm] nouveau 0000:01:00.0: fail ttm_validate
[ 590.075371] [drm] nouveau 0000:01:00.0: validate vram_list
[ 590.075374] [drm] nouveau 0000:01:00.0: validate: -12
Test cases :
-
http://geoeyemediaportal.s3.amazonaws.com/assets/images/gallery/ge1/hires/tehran_iran_02_11_10.jpg
- http://xkcd.com/802_large/
-
http://upload.wikimedia.org/wikipedia/commons/5/55/Futuregen_DOE_Concept_art.jpg
References :
- https://bugs.freedesktop.org/show_bug.cgi?id=28763#c15
- http://lists.freedesktop.org/archives/nouveau/2010-February/005125.html
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-07-06 19:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 19:18 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-39010-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-07-06 19:26 ` [Bug 39010] better handling of large pixmaps bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-26 16:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-27 3:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-30 7:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-30 8:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-30 9:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-09 17:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-20 1:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-20 2:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-20 2:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-20 3:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-25 19:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-39010-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.