From: John Zielinski <grim@undead.cc>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
James Simmons <jsimmons@infradead.org>
Subject: Re: Restoring Screen when coming back from KD_GRAPHICS
Date: Thu, 25 Dec 2003 11:28:36 -0500 [thread overview]
Message-ID: <3FEB1034.10801@undead.cc> (raw)
In-Reply-To: <1072348661.15461.31.camel@gaston>
Benjamin Herrenschmidt wrote:
>I think we don't need (nor want) to go down that path. And I fail to
>see what state info would matter anyway.
>
>
>The fbdev's can restore what they need. What I mean is they can restore the
>whole state needed for the mode, the palette and their own accel ops to
>behave properly. That's all they have to care about. If a gfx app need
>more engine state, it's up to this app to save/restore it.
>
>
Good. Then I don't have to worry about that then.
John
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
prev parent reply other threads:[~2003-12-25 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 8:11 Restoring Screen when coming back from KD_GRAPHICS John Zielinski
2003-12-24 8:26 ` Benjamin Herrenschmidt
2003-12-24 22:07 ` John Zielinski
2003-12-24 22:47 ` Benjamin Herrenschmidt
2003-12-25 1:22 ` John Zielinski
2003-12-25 10:37 ` Benjamin Herrenschmidt
2003-12-25 16:28 ` John Zielinski [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=3FEB1034.10801@undead.cc \
--to=grim@undead.cc \
--cc=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@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;
as well as URLs for NNTP newsgroup(s).