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 94414] Radeon RV370 w/ acceleration enabled exhibits problem with resolutions above 1440x900
Date: Thu, 10 Mar 2016 14:47:11 +0000	[thread overview]
Message-ID: <bug-94414-502-fCmYTYgbHx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94414-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1688 bytes --]

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

Jean-Philippe Gariépy <gawix@yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NOTOURBUG                   |---

--- Comment #11 from Jean-Philippe Gariépy <gawix@yahoo.com> ---
(In reply to Alex Deucher from comment #10)

> The problem is that the max texture and render target coordinate limits on
> R3xx hardware is 2048 pixels.  If your desktop is larger than 2048 pixels in
> either dimension, you will see corruption if you compositor attempts to
> accelerate it.  The desktop compositor should check the GL limits of the
> underlying driver before blindly specifying surfaces larger than them.

Hi Alex, you've responded to Felix comment but this is not the original
problem. 

As far as I know, my desktop size is 1920x1200 and doesn't exceed 2048 in
either dimension.  My card only has a 2 physical outputs DVI and S-video.  Only
DVI-0 is connected, so there is no "other monitor" left open that would change
the desktop size.

(II) RADEON(0): Output VGA-0 disconnected
(II) RADEON(0): Output DVI-0 connected
(II) RADEON(0): Output S-video disconnected

Nevertheless...

The only hint that I have so far is the "r300: CS space validation failed."
message. If it's a problem with the desktop compositor violating the contract,
which Gnome component is reponsible? Just trying to log the bug at the right
level.

I'll try using another desktop environment tonight.

Thanks

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3336 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

  parent reply	other threads:[~2016-03-10 14:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-94414-502@http.bugs.freedesktop.org/>
2016-03-10  3:29 ` [Bug 94414] Radeon RV370 w/ acceleration enabled exhibits problem with resolutions above 1440x900 bugzilla-daemon
2016-03-10  9:05 ` bugzilla-daemon
2016-03-10 14:02 ` bugzilla-daemon
2016-03-10 14:47 ` bugzilla-daemon [this message]
2016-03-10 18:09 ` bugzilla-daemon
2016-03-11  3:01 ` bugzilla-daemon
2016-03-11  3:15 ` bugzilla-daemon
2016-03-11  3:46 ` bugzilla-daemon
2016-03-11  8:48 ` bugzilla-daemon
2016-03-11  9:05 ` bugzilla-daemon
2016-03-11  9:37 ` bugzilla-daemon
2019-09-18 18:53 ` 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-94414-502-fCmYTYgbHx@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