From: Nigel Cunningham <ncunningham@clear.net.nz>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Pavel Machek <pavel@suse.cz>,
James Simmons <jsimmons@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] Framebuffer: 2nd try: client notification mecanism & PM
Date: Fri, 08 Aug 2003 09:38:59 +1200 [thread overview]
Message-ID: <1060292180.3507.27.camel@laptop-linux> (raw)
In-Reply-To: <1060263168.593.77.camel@gaston>
Hi.
Would this play well with the suspend process itself displaying output?
(Eg progress, errors...).
Regards,
Nigel
On Fri, 2003-08-08 at 01:32, Benjamin Herrenschmidt wrote:
> On Thu, 2003-08-07 at 12:03, Pavel Machek wrote:
>
> > I believe solution to this is simple: always switch to kernel-owned
> > console during suspend. (swsusp does it, there's patch for S3 to do
> > the same). That way, Xfree (or qtopia or whoever) should clean up
> > after themselves and leave the console to the kernel. (See
> > kernel/power/console.c)
>
> I admit I quite like this solution. It would also help displaying
> something sane (blank, pattern, whatever) on screen during driver
> teardown instead of the junk left by X...
>
> I'll look into including that switch into my pmac code as well
> and see if it works properly in all cases (I think so). Also,
> recent DRI CVS finally has working suspend/resume (works on
> console switch too).
>
> Ben.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand
You see, at just the right time, when we were still powerless,
Christ died for the ungodly.
-- Romans 5:6, NIV.
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
next prev parent reply other threads:[~2003-08-07 21:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1059484419.8537.19.camel@gaston>
[not found] ` <20030729174919.GC2601@openzaurus.ucw.cz>
[not found] ` <1059567270.8545.70.camel@gaston>
2003-07-30 13:14 ` [PATCH] Framebuffer: 2nd try: client notification mecanism & PM Benjamin Herrenschmidt
2003-08-01 10:04 ` Benjamin Herrenschmidt
2003-08-06 23:52 ` James Simmons
2003-08-07 9:38 ` Benjamin Herrenschmidt
2003-08-07 10:03 ` Pavel Machek
2003-08-07 13:32 ` Benjamin Herrenschmidt
2003-08-07 17:26 ` [Linux-fbdev-devel] " James Simmons
2003-08-07 21:38 ` Nigel Cunningham [this message]
2003-08-07 21:51 ` Pavel Machek
2003-08-07 14:37 ` Benjamin Herrenschmidt
2003-08-07 17:28 ` James Simmons
2003-08-07 20:29 ` [Linux-fbdev-devel] " Pavel Machek
2003-08-07 17:23 ` James Simmons
2003-08-07 20:29 ` Pavel Machek
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=1060292180.3507.27.camel@laptop-linux \
--to=ncunningham@clear.net.nz \
--cc=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=pavel@ucw.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).