All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Jackson <ajax@redhat.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [RFC][PATCH 0/10] Atomic modesetting v2
Date: Wed, 27 Jun 2012 13:11:00 -0400	[thread overview]
Message-ID: <1340817060.12912.45.camel@atropine> (raw)
In-Reply-To: <20120627094826.0f27c10c@jbarnes-desktop>


[-- Attachment #1.1: Type: text/plain, Size: 835 bytes --]

On Wed, 2012-06-27 at 09:48 -0700, Jesse Barnes wrote:

> The other thing I'm worried about with atomic mode setting is handling
> the legacy case properly.  We'll still need to handle apps that want to
> change one CRTC at a time without altering the state of other CRTCs.

Fortunately that's not true, you can flag-day it (per drm device even,
if we want).  If the first thing userspace asks for is atomic modeset
then you simply disallow subsequent non-atomic modesets, and the
reverse.  Userspace code will need to grow atomic support anyway, so can
simply treat -EINVAL from trying it as meaning "no kernel support,
revert to the older thing".

This does mean you have to update all of userspace to do the new call
instead of the old one, but that's fine, there's only a handful of
clients for this API.

- ajax

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

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

  reply	other threads:[~2012-06-27 17:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27 10:24 [RFC][PATCH 0/10] Atomic modesetting v2 ville.syrjala
2012-06-27 10:24 ` [RFC][PATCH 01/10] drm: Export drm_property_create_blob() and drm_property_destroy_blob() ville.syrjala
2012-06-27 10:24 ` [RFC][PATCH 02/10] drm: Allow signed values for range properties ville.syrjala
2012-06-27 10:24 ` [RFC][PATCH 03/10] drm: Allow drm_mode_object_find() to look up an object of any type ville.syrjala
2012-06-27 10:24 ` [RFC][PATCH 04/10] drm: Export drm_encoder_crtc_ok ville.syrjala
2012-06-27 10:24 ` [RFC][PATCH 05/10] drm: Export drm_crtc_prepare_encoders() ville.syrjala
2012-06-27 10:24 ` [RFC][PATCH 06/10] drm: Refactor object property check code ville.syrjala
2012-06-27 10:24 ` [RFC][PATCH 07/10] drm: Add MODE_IDS property to connectors ville.syrjala
2012-06-27 10:24 ` [RFC][PATCH 08/10] WIP: drm: Atomic modeset ioctl ville.syrjala
2012-08-31 22:47   ` Rob Clark
2012-09-01 11:12     ` Daniel Vetter
2012-09-01 15:58       ` Rob Clark
2012-09-01 16:56         ` Daniel Vetter
2012-09-01 18:05           ` Rob Clark
2012-06-27 10:24 ` [RFC][PATCH 09/10] drm/i915: Split clipping and checking from update_plane hook ville.syrjala
2012-06-27 10:24 ` [RFC][PATCH 10/10] WIP drm/i915: "Atomic" modeset test implementation ville.syrjala
2012-06-27 16:48 ` [RFC][PATCH 0/10] Atomic modesetting v2 Jesse Barnes
2012-06-27 17:11   ` Adam Jackson [this message]
2012-06-27 17:50     ` Dave Airlie
2012-06-27 18:37   ` Ville Syrjälä

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=1340817060.12912.45.camel@atropine \
    --to=ajax@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.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 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.