unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andy Wingo <wingo@igalia.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Xorg tearing fix on Intel HD Graphics 4000
Date: Wed, 28 Jun 2017 10:24:48 +0200	[thread overview]
Message-ID: <8737ak5xkf.fsf@igalia.com> (raw)
In-Reply-To: <87lgodfhru.fsf@netris.org> (Mark H. Weaver's message of "Tue, 27 Jun 2017 13:43:33 -0400")

On Tue 27 Jun 2017 19:43, Mark H Weaver <mhw@netris.org> writes:

> Andy Wingo <wingo@igalia.com> writes:
>
>> On Wed 21 Jun 2017 09:55, Roel Janssen <roel@gnu.org> writes:
>>
>>> For a long time now, I have a tearing issue on GuixSD (parts of the
>>> screen do not get updated while others do, resulting in dissapearing
>>> text in Emacs).
>>
>> I wonder if it makes sense to update the intel driver to see if it fixed
>> it?  Then perhaps we could avoid the hack.  There are commits here that
>> touch SNA and things that look like they could be relevant:
>>
>>   https://cgit.freedesktop.org/xorg/driver/xf86-video-intel/log/
>
> It's a good idea, but we're already using HEAD (6babcf1) from their
> repo, and have been since June 11 (guix commit e2de6bbdd5).  I can
> confirm that this didn't solve the problem for me.
>
> In the meantime, how would you feel about pushing the following commit
> to master?  It would still allow the use of SNA by explicitly asking for
> it in xorg.conf, but auto-configuration would choose UXA by default.
>
> What do you think?

Looks good to me.  We should report the problem though... ok I did that
here:

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

Looking forward to having a normal Emacs again :)

Andy

  reply	other threads:[~2017-06-28  8:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21  7:55 Xorg tearing fix on Intel HD Graphics 4000 Roel Janssen
2017-06-21 10:38 ` Ricardo Wurmus
2017-06-21 13:26   ` Roel Janssen
2017-06-21 16:27     ` Kei Kebreau
2017-06-21 17:23     ` Mark H Weaver
2017-06-21 22:21       ` Roel Janssen
2017-06-21 23:23         ` William
2017-06-25 11:59           ` Marius Bakke
2017-06-25 17:13             ` Roel Janssen
2017-06-25 17:39               ` Marius Bakke
2017-06-25  5:47       ` Chris Marusich
2017-06-25  8:31         ` Roel Janssen
2017-06-25 11:38           ` Mark H Weaver
2017-06-25 11:08         ` Mark H Weaver
2017-08-07 21:48           ` Clément Lassieur
2017-06-25  5:46     ` Chris Marusich
2017-06-25  8:28       ` Roel Janssen
2017-07-20  2:43         ` Chris Marusich
2017-07-20 10:57           ` Roel Janssen
2017-06-23 18:00 ` Christopher Baines
2017-06-26  8:55 ` Andy Wingo
2017-06-27 17:43   ` Mark H Weaver
2017-06-28  8:24     ` Andy Wingo [this message]
2017-06-28 18:14       ` Mark H Weaver

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8737ak5xkf.fsf@igalia.com \
    --to=wingo@igalia.com \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).