All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Carlos Rafael Giani <dv@pseudoterminal.org>,
	 Boszormenyi Zoltan <zboszor@pr.hu>,
	"meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>
Subject: Sync to V-blank
Date: Sun, 11 May 2014 17:49:25 -0700	[thread overview]
Message-ID: <53701A95.8050902@boundarydevices.com> (raw)

On Thu Apr 3 03:32:06 PDT 2014, Carlos Rafael Giani wrote:
 >
> This X11 vsync problem has been bugging several people, and to date,
> there is no proper solution (other than to use framebuffer directly
> instead, or switch to Wayland).
>
> Eric Nelson mentioned details about this, as well as a possible
> workaround. I appended his email here:
>
> =================================================

I haven't had much of a chance to look into this, but just found
this in "Freescale_XServer_Video_Driver_Users_Guide.pdf" in the
documents package of the documentation package of the 3.10.17-ga
release:

	https://community.freescale.com/docs/DOC-100787


	1.7 Tearing
	XServer (and early Microsoft Windows) does not support double
	buffering for the screen. There will be a copy from off-screen
	buffer to target on-screen area (or direct rendering to
	on-screen). The operation cannot be completed in the blank time
	of the display, and the IPU cannot provide an ideal VSYNC
	signal.
	Therefore, there will be tearing.

	To remove tearing, a GLES compositor is needed. This tearing
	free feature will be described in next release.

Regards,


Eric


             reply	other threads:[~2014-05-12  0:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12  0:49 Eric Nelson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-04-03 10:28 Sync to V-blank Boszormenyi Zoltan
2014-04-03 10:32 ` Carlos Rafael Giani

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=53701A95.8050902@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=dv@pseudoterminal.org \
    --cc=meta-freescale@yoctoproject.org \
    --cc=zboszor@pr.hu \
    /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.