From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
airlied@linux.ie, LKML <linux-kernel@vger.kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Eric Anholt <eric@anholt.net>,
pm list <linux-pm@lists.linux-foundation.org>,
dri-devel@lists.sourceforge.net,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [linux-pm] [PATCH] PM / i915: Skip kernel VT switch during suspend/resume if KMS is used
Date: Wed, 3 Feb 2010 15:24:43 +0100 [thread overview]
Message-ID: <20100203152443.7ce8b340@strolchi> (raw)
In-Reply-To: <20100131085419.GI2238@elf.ucw.cz>
On Sun, 31 Jan 2010 09:54:19 +0100
Pavel Machek <pavel@ucw.cz> wrote:
> On Thu 2010-01-28 00:07:51, Stefan Seyfried wrote:
> > Hi,
> >
> > On Tue, 26 Jan 2010 15:58:43 +0100 Pavel Machek <pavel@ucw.cz> wrote:
> > > We need vt switch when display is controlled by userland app directly
> > > accessing hw. It may or may not be X (svgalib anyone?,
> > > gtk-on-framebuffer? qtopia?).
> >
> > anything-on-framebuffer should not be different from plain framebuffer
> > console, or am I missing something?
>
> It is. At least svgalib accesses hw directly. It probably can run even
> on framebuffer.
If it accesses hw directly, it's not really "anything-on-framebuffer"
anymore, is it? The framebuffer device is there to abstract the
hardware.
> Well, for now the "shadow buffer" contains only text, not graphics
> images. So you'd need to enlarge it a lot. Doable but more than one liner.
Yes, noticed this today. I was using bootsplash-patched kernels, which
are obviously different in this aspect, so that shifted my view on
reality ;)
--
Stefan Seyfried
"Any ideas, John?"
"Well, surrounding them's out."
next prev parent reply other threads:[~2010-02-03 14:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 23:55 [PATCH] PM / i915: Skip kernel VT switch during suspend/resume if KMS is used Rafael J. Wysocki
2010-01-24 0:18 ` Alan Cox
2010-01-24 0:18 ` Alan Cox
2010-01-24 19:04 ` Rafael J. Wysocki
2010-01-24 19:04 ` Rafael J. Wysocki
2010-01-25 17:22 ` Eric Anholt
2010-01-25 17:22 ` Eric Anholt
2010-01-25 18:35 ` Jesse Barnes
2010-01-25 18:43 ` Alan Cox
2010-01-25 18:49 ` Jesse Barnes
2010-01-25 21:17 ` Rafael J. Wysocki
2010-01-25 21:27 ` Alan Cox
2010-01-25 21:54 ` Rafael J. Wysocki
2010-01-25 22:23 ` Alan Cox
2010-01-25 22:23 ` Alan Cox
2010-01-26 14:17 ` Pavel Machek
2010-01-26 18:47 ` Rafael J. Wysocki
2010-01-26 14:58 ` Pavel Machek
2010-01-26 21:46 ` H. Peter Anvin
2010-01-26 21:46 ` H. Peter Anvin
2010-01-26 22:08 ` Pavel Machek
2010-01-26 22:08 ` Pavel Machek
2010-01-27 23:07 ` [linux-pm] " Stefan Seyfried
2010-01-31 8:54 ` Pavel Machek
2010-02-03 14:24 ` Stefan Seyfried
2010-02-03 14:24 ` Stefan Seyfried [this message]
2010-01-31 8:54 ` Pavel Machek
2010-01-27 23:07 ` Stefan Seyfried
2010-01-26 14:58 ` Pavel Machek
2010-01-26 18:47 ` Rafael J. Wysocki
2010-01-26 14:17 ` Pavel Machek
2010-01-25 21:54 ` Rafael J. Wysocki
2010-01-25 21:27 ` Alan Cox
2010-01-25 21:17 ` Rafael J. Wysocki
2010-01-25 18:49 ` Jesse Barnes
2010-01-25 18:43 ` Alan Cox
2010-01-25 18:35 ` Jesse Barnes
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=20100203152443.7ce8b340@strolchi \
--to=stefan.seyfried@googlemail.com \
--cc=airlied@linux.ie \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.sourceforge.net \
--cc=eric@anholt.net \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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.