From: Andriy Gapon <avg@icyb.net.ua>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: g33 + dual head = problems
Date: Mon, 07 May 2012 16:49:43 +0300 [thread overview]
Message-ID: <4FA7D2F7.5040606@icyb.net.ua> (raw)
In-Reply-To: <1336080801_134462@CP5-2952>
on 04/05/2012 00:33 Chris Wilson said the following:
> On Thu, 03 May 2012 17:23:09 -0400, Adam Jackson <ajax@redhat.com> wrote:
>> On 5/3/12 1:11 PM, Andriy Gapon wrote:
>>
>>> Can the problem be related to some 2048x2048 limitation in G33?
>>
>> Yes, the problem is exactly that limitation.
>
> Except that even UXA on gen3 has workarounds for that limit, so XRender
> based desktop effects should, in theory, work.
I tried Fedora 17-Beta live CD to test the newer code. It's not the very latest
stuff, though. E.g. xf86-video-intel is at 2.18.0.
OpenGL still creates massive corruption.
XRender is almost usable, but there are quite annoying small corruptions here and
there.
There are some log files, pictures and screenshots here:
http://www.icyb.net.ua/~avg/g33-dualhead/
Sorry for the bad quality of the pictures taken with my phone camera. The
pictures demonstrate the corruption from OpenGL.
The screenshots are taken with XRender enabled. On the first two there are small
corruptions near menu button area. The third one shows how an obscured window
partially shows through a window above it.
Hope this information is of use.
--
Andriy Gapon
prev parent reply other threads:[~2012-05-07 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 17:11 g33 + dual head = problems Andriy Gapon
2012-05-03 21:23 ` Adam Jackson
2012-05-03 21:33 ` Chris Wilson
2012-05-07 13:49 ` Andriy Gapon [this message]
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=4FA7D2F7.5040606@icyb.net.ua \
--to=avg@icyb.net.ua \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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