All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Ser <contact@emersion.fr>
To: Pekka Paalanen <ppaalanen@gmail.com>
Cc: Dennis Filder <d.filder@web.de>,
	dri-devel@lists.freedesktop.org,
	Hans de Goede <hdegoede@redhat.com>
Subject: Re: Handling DRM master transitions cooperatively
Date: Tue, 07 Sep 2021 10:19:03 +0000	[thread overview]
Message-ID: <Kh2hM9odvPcbqNUxhSEwQbnUCLt6nyrAzGhxnQ0JO1CcAzI6y31enf8_AmgAynFxWo3E1QUlW1m8UvKPDAq0gFLQi2CF1b3FFNMRfiUzOAI=@emersion.fr> (raw)
In-Reply-To: <20210907130746.7b667dac@eldfell>

FWIW, I've just hit a case where a compositor leaves a "rotation" KMS
prop set behind, then Xorg tries to startup and fails because it doesn't
reset this prop. So none of this is theoretical.

I still think a "reset all KMS props to an arbitrary default value" flag
in drmModeAtomicCommit is the best way forward. I'm not sure a user-space
protocol would help too much.

  reply	other threads:[~2021-09-07 10:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 19:08 Handling DRM master transitions cooperatively Dennis Filder
2021-09-07 10:07 ` Pekka Paalanen
2021-09-07 10:19   ` Simon Ser [this message]
2021-09-07 12:52     ` Pekka Paalanen
2021-09-07 15:52       ` Sebastian Wick
2021-09-08 16:21         ` Dennis Filder
2021-09-09  8:20           ` Pekka Paalanen
2021-09-08  9:51       ` Simon Ser
2021-09-08 11:13         ` Pekka Paalanen
2021-09-08 16:14         ` Dennis Filder
2021-09-07 12:42   ` Hans de Goede
2021-09-08  7:36     ` Pekka Paalanen
2021-09-08  7:49       ` Hans de Goede
2021-09-08 16:27       ` Daniel Vetter
2021-09-09  7:37         ` Pekka Paalanen
2021-09-14 13:45           ` Daniel Vetter
2021-09-22  8:56             ` Pekka Paalanen
2021-09-22  9:21               ` Hans de Goede
2021-09-23  8:23                 ` Pekka Paalanen
2021-09-23  8:52                   ` Hans de Goede
2021-09-30  9:26                   ` Daniel Vetter
2021-10-01 16:33                 ` Simon Ser
2021-10-02 17:27                   ` Hans de Goede

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='Kh2hM9odvPcbqNUxhSEwQbnUCLt6nyrAzGhxnQ0JO1CcAzI6y31enf8_AmgAynFxWo3E1QUlW1m8UvKPDAq0gFLQi2CF1b3FFNMRfiUzOAI=@emersion.fr' \
    --to=contact@emersion.fr \
    --cc=d.filder@web.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hdegoede@redhat.com \
    --cc=ppaalanen@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.