dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Michlmayr <tbm-R+vWnYXSFMfQT0dZR+AlfA@public.gmane.org>
To: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Flicker with fb on Jetson TK1
Date: Tue, 26 Jul 2016 18:03:07 -0700	[thread overview]
Message-ID: <20160727010307.GA20706@jirafa.cyrius.com> (raw)
In-Reply-To: <20160725142151.GP21170-EkSeR96xj6Pcmrwk2tT4+A@public.gmane.org>

* Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> [2016-07-25 16:21]:
> What version of X do you use? Recent versions, I think starting with
> 1.18, the modesetting driver is built-in and is what you should use with
> Tegra (and on top of an DRM/KMS driver, really).
> 
> The problem with fbdev is that it doesn't do double-buffering and hence
> you can often see the kind of tearing as in the video. The modesetting
> driver (which is also available as xf86-video-modesetting pre-1.18) can
> do double-buffering (and I think will do by default), hence removing
> the cause of such tearing.
> 
> Can you try running the test with the modesetting driver and report if
> you're still experiencing the issue?

This is with 1.18.4.  The Xorg.log suggests that glx, modesetting,
fbdev, fbdevhw and glamoregl were loaded (although glamor
initialization failed).  Modesetting is used according to the log.

I'm not very familiar with the graphics subsystem, so I'd appreciate
it if someone could take a look at the log:
http://www.cyrius.com/tmp/tk1/Xorg.0.log

-- 
Martin Michlmayr
http://www.cyrius.com/

      parent reply	other threads:[~2016-07-27  1:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25  2:02 Flicker with fb on Jetson TK1 Martin Michlmayr
     [not found] ` <20160725020234.GA25839-IRMp5PtgtdoigzW5ZibpNwC/G2K4zDHf@public.gmane.org>
2016-07-25 14:21   ` Thierry Reding
     [not found]     ` <20160725142151.GP21170-EkSeR96xj6Pcmrwk2tT4+A@public.gmane.org>
2016-07-27  1:03       ` Martin Michlmayr [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=20160727010307.GA20706@jirafa.cyrius.com \
    --to=tbm-r+vwnyxsfmfqt0dzr+alfa@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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