From: Chris Wilson <chris@chris-wilson.co.uk>
To: Gabriel Torreiro de Moraes <gtmoraes1@gmail.com>,
Intel-gfx <Intel-gfx@lists.freedesktop.org>
Subject: Re: Dual Monitor Issue. One monitor is partly visible on another
Date: Wed, 23 Mar 2011 20:55:33 +0000 [thread overview]
Message-ID: <849307$c4ig2o@azsmga001.ch.intel.com> (raw)
In-Reply-To: <1300913234.2074.5.camel@GTMoraes-Aspire>
On Wed, 23 Mar 2011 17:47:14 -0300, Gabriel Torreiro de Moraes <gtmoraes1@gmail.com> wrote:
> So, after some Intel Drivers update, some programs started to work
> nicely, faster and beautifully. But it corrupted my Dual-Monitor Setup.
> I don't know what to say, I'm totally desperate. I had to show one of my
> programs to my teacher using a projector, but with the dual monitor
> corruption, I called in sick today. I need to use the netbook screen to
> make changes on the program and the second monitor/projector to show the
> program working.
Good news! We fixed this bug 7 months ago.
commit 52e68630d13f9668f8f4dd6978fa41039bacfaf6
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Sun Aug 8 10:15:59 2010 +0100
drm/i915: Fix offset page-flips on i965+
i965 uses the Display Registers to compute the offset from the display
base so the new base does not need adjusting when flipping. The older
chipsets use a fence to access the display and so do perceive the
surface as linear and have a single base register which is reprogrammed
using the flip.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
Reported-by: Marty Jack <martyj19@comcast.net>
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-03-23 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 20:47 Dual Monitor Issue. One monitor is partly visible on another Gabriel Torreiro de Moraes
2011-03-23 20:55 ` Chris Wilson [this message]
2011-03-23 20:59 ` Gabriel Torreiro de Moraes
2011-03-23 23:57 ` Marc Deop
2011-03-24 0:49 ` Gabriel Torreiro de Moraes
2011-03-24 2:43 ` Gabriel Torreiro de Moraes
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='849307$c4ig2o@azsmga001.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=gtmoraes1@gmail.com \
/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.