From: Pavel Machek <pavel@suse.cz>
To: Nigel Cunningham <ncunningham@clear.net.nz>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
James Simmons <jsimmons@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] Framebuffer: 2nd try: client notification mecanism & PM
Date: Thu, 7 Aug 2003 23:51:16 +0200 [thread overview]
Message-ID: <20030807215116.GD413@elf.ucw.cz> (raw)
In-Reply-To: <1060292180.3507.27.camel@laptop-linux>
Hi!
> Would this play well with the suspend process itself displaying output?
> (Eg progress, errors...).
Yes.
Pavel
...
> > > 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/
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
-------------------------------------------------------
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
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@suse.cz>
To: Nigel Cunningham <ncunningham@clear.net.nz>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
James Simmons <jsimmons@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [Linux-fbdev-devel] [PATCH] Framebuffer: 2nd try: client notification mecanism & PM
Date: Thu, 7 Aug 2003 23:51:16 +0200 [thread overview]
Message-ID: <20030807215116.GD413@elf.ucw.cz> (raw)
In-Reply-To: <1060292180.3507.27.camel@laptop-linux>
Hi!
> Would this play well with the suspend process itself displaying output?
> (Eg progress, errors...).
Yes.
Pavel
...
> > > 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/
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-08-07 21:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 13:13 [PATCH] Framebuffer: client notification mecanism & PM Benjamin Herrenschmidt
2003-07-29 17:49 ` Pavel Machek
2003-07-30 12:14 ` Benjamin Herrenschmidt
2003-07-30 13:10 ` [PATCH] Framebuffer: 2nd try: " Benjamin Herrenschmidt
2003-07-30 13:14 ` Benjamin Herrenschmidt
2003-07-30 13:14 ` Benjamin Herrenschmidt
2003-08-01 10:04 ` Benjamin Herrenschmidt
2003-08-01 10:04 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-08-06 23:52 ` James Simmons
2003-08-06 23:52 ` [Linux-fbdev-devel] " James Simmons
2003-08-07 9:38 ` Benjamin Herrenschmidt
2003-08-07 9:38 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-08-07 10:03 ` Pavel Machek
2003-08-07 10:03 ` [Linux-fbdev-devel] " Pavel Machek
2003-08-07 13:32 ` Benjamin Herrenschmidt
2003-08-07 13:32 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-08-07 17:26 ` James Simmons
2003-08-07 21:38 ` Nigel Cunningham
2003-08-07 21:38 ` [Linux-fbdev-devel] " Nigel Cunningham
2003-08-07 21:51 ` Pavel Machek [this message]
2003-08-07 21:51 ` Pavel Machek
2003-08-07 14:37 ` Benjamin Herrenschmidt
2003-08-07 14:37 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-08-07 17:28 ` James Simmons
2003-08-07 17:28 ` [Linux-fbdev-devel] " James Simmons
2003-08-07 20:29 ` Pavel Machek
2003-08-07 17:23 ` James Simmons
2003-08-07 20:29 ` Pavel Machek
2003-08-07 20:29 ` [Linux-fbdev-devel] " 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=20030807215116.GD413@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@clear.net.nz \
/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.