From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesse Barnes Subject: Re: VT switchless v3 Date: Tue, 19 Feb 2013 10:13:42 -0800 Message-ID: <20130219101342.0f671895@jbarnes-desktop> References: <1360963394-8663-1-git-send-email-jbarnes@virtuousgeek.org> <20130218150320.GN5813@phenom.ffwll.local> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from oproxy13-pub.unifiedlayer.com (oproxy13-pub.unifiedlayer.com [69.89.16.30]) by gabe.freedesktop.org (Postfix) with SMTP id 7479DE5DBA for ; Tue, 19 Feb 2013 10:13:01 -0800 (PST) In-Reply-To: <20130218150320.GN5813@phenom.ffwll.local> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Daniel Vetter Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Mon, 18 Feb 2013 16:03:20 +0100 Daniel Vetter wrote: > On Fri, Feb 15, 2013 at 01:23:08PM -0800, Jesse Barnes wrote: > > A few more fixes from Daniel. > > So one thing that crossed my mind which we should at least quickly > discuss: How is userspace supposed to notice the resume? On a lot of > desktops (and even Androids) the normal thing seems to be to draw the > screensave/lock after resume, which means that we'll show the desktop for > a frame or so. Which is not too nice. Is userspace simply supposed to draw > the screen lock before sleep, or does it need a helping hand from the > kernel to fix this issue? Userspace initiates the suspend, so GNOME or whatever is supposed to lock things at that point. I've heard talk of a uevent or dbus thing to broadcast it as well, but I'm not sure of the status of that. IIRC Android already has a hack like this; they don't want the fbcon to ever be visible during usage... -- Jesse Barnes, Intel Open Source Technology Center