All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: Rainer Hochecker <fernetmenta@kodi.tv>
Cc: "Peter Frühberger" <fritsch@kodi.tv>,
	"DRI Development" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/3] RFC: drm: Restrict vblank ioctl to master
Date: Mon, 25 Jul 2016 16:38:12 +0900	[thread overview]
Message-ID: <10c289ca-31ec-d1a1-4d93-ac345f91bf4d@daenzer.net> (raw)
In-Reply-To: <CAH0Sn6F7AUghVWUM3fUxuJ_Qqf=Bw-7WtjHeo64DLCyWoe2ebw@mail.gmail.com>

On 13.07.2016 18:49, Rainer Hochecker wrote:
> We have been using this for years now and did not observe issues you
> mentioned. I would be surprised if a child window refreshes in a
> different rate than the main window

The Xorg driver decides which CRTC to synchronize with based on the
window geometry. For a window with no visible geometry, it may choose a
different CRTC than for the visible output window. In the case of DRI3,
the Xorg Present extension code may even fall back to the fake CRTC in
that case, which only generates a fake vblank event once every second.


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-07-25  7:38 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14  9:03 [PATCH 1/3] RFC: drm: Restrict vblank ioctl to master Daniel Vetter
2016-06-14  9:03 ` [PATCH 2/3] drm: Mark authmagic ioctls as unlocked Daniel Vetter
2016-06-14  9:03 ` [PATCH 3/3] drm: Mark set/drop master ioctl " Daniel Vetter
2016-06-14 16:10   ` Daniel Vetter
2016-06-14  9:09 ` [PATCH 1/3] RFC: drm: Restrict vblank ioctl to master Michel Dänzer
2016-06-14  9:35   ` Daniel Vetter
2016-06-15  7:29     ` Michel Dänzer
2016-06-15  8:57       ` Daniel Vetter
2016-06-16 13:02         ` Rainer Hochecker
2016-06-16 16:17           ` Daniel Vetter
2016-06-17 12:00             ` Rainer Hochecker
2016-06-20 14:46               ` Daniel Stone
2016-06-20 18:24                 ` Rainer Hochecker
2016-06-20 23:27                   ` Daniel Stone
2016-06-21  4:57                     ` Rainer Hochecker
2016-06-21  5:01                       ` Daniel Stone
2016-06-21  5:15                         ` Rainer Hochecker
2016-06-23 19:54                           ` Rainer Hochecker
2016-06-23 20:55                             ` Daniel Stone
2016-07-12 10:29                               ` Daniel Vetter
2016-07-13  6:50                                 ` Rainer Hochecker
2016-07-13  9:43                                   ` Michel Dänzer
2016-07-13  9:48                                     ` Daniel Vetter
     [not found]                                       ` <CAH0Sn6G3RqaKWF8CiNC65ZNGm0m=ROBjwk8j_KBZwbokS+kS-g@mail.gmail.com>
2016-07-13  9:54                                         ` Rainer Hochecker
     [not found]                                     ` <CAH0Sn6EAtoVDZUwYyYVLT3dsdN52T1VQtA0hBUbjNvzbMwJLgQ@mail.gmail.com>
2016-07-13  9:49                                       ` Rainer Hochecker
2016-07-25  7:38                                         ` Michel Dänzer [this message]
2016-07-25 11:15                                           ` Rainer Hochecker
2017-05-05 19:35                                             ` Daniel Vetter
2017-05-05 21:41                                               ` Mario Kleiner
2017-05-06  5:43                                                 ` Rainer Hochecker
  -- strict thread matches above, loose matches on Subject: below --
2016-06-14  9:02 Daniel Vetter
2018-08-08 15:35 ` Rainer Hochecker
2018-08-08 16:59   ` Daniel Vetter
2018-08-08 17:41     ` Rainer Hochecker

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=10c289ca-31ec-d1a1-4d93-ac345f91bf4d@daenzer.net \
    --to=michel@daenzer.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fernetmenta@kodi.tv \
    --cc=fritsch@kodi.tv \
    /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.