From: Pavel Machek <pavel@suse.cz>
To: James Simmons <jsimmons@infradead.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.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: [Linux-fbdev-devel] [PATCH] Framebuffer: 2nd try: client notification mecanism & PM
Date: Thu, 7 Aug 2003 22:29:51 +0200 [thread overview]
Message-ID: <20030807202951.GB413@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0308071822270.13973-100000@phoenix.infradead.org>
Hi!
> > 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)
>
> Not very helpful on embedded systems that use the framebuffer without the
> VT console.
Okay, that might be a problem. But such system will need some special
notification... Is VT so much overhead?
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
prev parent reply other threads:[~2003-08-07 20:30 UTC|newest]
Thread overview: 18+ 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-08-01 10:04 ` [Linux-fbdev-devel] " 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 ` James Simmons
2003-08-07 21:38 ` Nigel Cunningham
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 ` Pavel Machek
2003-08-07 17:23 ` James Simmons
2003-08-07 20:29 ` Pavel Machek [this message]
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=20030807202951.GB413@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=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).