From: James Simmons <jsimmons@linux-fbdev.org>
To: Brad Douglas <brad@neruo.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux console project <linuxconsole-dev@lists.sourceforge.net>
Subject: Re: [Linux-fbdev-devel] [RFC] fbdev & power management
Date: Wed, 14 Mar 2001 13:30:03 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.31.0103141321040.779-100000@linux.local> (raw)
>But wouldn't falling back to dummycon prevent the driver specific
>suspend/resume calls from working? Or at a minimum, make handling those
>calls more complex?
Not if suspend/resume are handled on the fbdev driver level. Dummycon
would only shutdown fbcon on explict open of /dev/fb. Also note it will be
possible to have only a serial console and use /dev/fb by itself. In this
case we don't even need dummycon since their is no VT support present.
>No, there does not need to be graphical images of the text console -- a
>simply text buffer would suffice.
See email to Ben.
>But what about things like GTKFb and
>Embedded QT? They would certainly benefit from having a backup screen
>image, right? I do not believe there is any way to determine if the
>console is in fact in a 'text' or graphical state.
Yes and it would not be hard to do this. I have the basic idea in the
email to Ben. As for console in text or graphical state take a look at
vt_ioctl.c:vt_ioctl() for KDGETMODE. You get back KD_TEXT or KD_GRAPHICS.
MS: (n) 1. A debilitating and surprisingly widespread affliction that
renders the sufferer barely able to perform the simplest task. 2. A disease.
James Simmons [jsimmons@linux-fbdev.org] ____/|
fbdev/console/gfx developer \ o.O|
http://www.linux-fbdev.org =(_)=
http://linuxgfx.sourceforge.net U
http://linuxconsole.sourceforge.net
next reply other threads:[~2001-03-15 5:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-14 21:30 James Simmons [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-21 17:02 James Simmons
2001-03-21 22:09 ` Benjamin Herrenschmidt
2001-03-14 21:20 James Simmons
2001-03-15 11:31 ` Benjamin Herrenschmidt
2001-03-15 12:03 ` Geert Uytterhoeven
2001-03-14 20:48 James Simmons
2001-03-15 8:21 ` Geert Uytterhoeven
[not found] <E14d6Ee-00009a-00@usw-sf-list1.sourceforge.net>
2001-03-14 13:17 ` Benjamin Herrenschmidt
2001-03-14 13:39 ` Geert Uytterhoeven
2001-03-14 14:05 ` Benjamin Herrenschmidt
2001-03-14 14:51 ` Geert Uytterhoeven
2001-03-14 20:57 ` Brad Douglas
2001-03-13 21:25 Benjamin Herrenschmidt
2001-03-14 8:02 ` [Linux-fbdev-devel] " Brad Douglas
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=Pine.LNX.4.31.0103141321040.779-100000@linux.local \
--to=jsimmons@linux-fbdev.org \
--cc=benh@kernel.crashing.org \
--cc=brad@neruo.com \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxconsole-dev@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®