linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: John Zielinski <grim@undead.cc>
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 09:47:38 +1100	[thread overview]
Message-ID: <1072306057.15476.19.camel@gaston> (raw)
In-Reply-To: <3FEA0E0D.3030001@undead.cc>


> I'll take a look.  This fits well with what I'm trying to do with the 
> mode switching between virtual terminals.  The callback will definately 
> be neccessarry to tell the driver to save any driver specific data that 
> I'm not already saving (ie anything that's not defined in fb.h).

I don't think we need to "save" anything, there is no way I want any
knowledge of fbcon-specific stuff to go back into fbdev's, it was
hard enough to split these properly (that's a good thing James did).

I think we just need to instruct the fbdev to restore it's mode via
a set_var with an activate flag FB_ACTIVATE_FORCE, that bypass any
test inside the driver about the mode changing from the current info-var,
that is basically forcing it to re-apply it's current var. Most drivers
will also reset the accel engine properly if any when doing so.

Ben.




-------------------------------------------------------
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

  reply	other threads:[~2003-12-24 22:48 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 [this message]
2003-12-25  1:22       ` John Zielinski
2003-12-25 10:37         ` Benjamin Herrenschmidt
2003-12-25 16:28           ` John Zielinski

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=1072306057.15476.19.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=grim@undead.cc \
    --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).