From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Cc: Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2/6] fbcon: Stop framebuffer operations before hardware is properly initialized
Date: Mon, 14 Mar 2005 10:07:15 +1100 [thread overview]
Message-ID: <1110755235.5787.189.camel@gaston> (raw)
In-Reply-To: <200503130833.44469.adaplas@hotpop.com>
On Sun, 2005-03-13 at 08:33 +0800, Antonino A. Daplas wrote:
> Accessing the hardware before it is properly initialized can lead to crashes
> or screen corruption. This happens when switching to X then back to console.
> When console comes back from X, the device is in an undefined state. During
> this window, accessing the hardware is disallowed.
>
> A new field in fbcon_par is added (graphics), which will be set to nonzero
> just before initialization of the framebuffer and when coming back from
> KD_GRAPHICS, then unset when an fb_set_var/fb_set_par is done. While this
> field is set, no accesses to the hardware is done. The consequence of
> this change is, hopefully, more robust switching between KD_GRAPHICS<->
> KD_TEXT.
>
> An added benefit coming from this change is that the MODESWITCHLATE hack
> is not needed anymore and thus removed. This hack is used by savagefb,
> rivafb and nvidiafb.
Excellent ! That should fix some nasty issues I've been dealing with as
well !
Ben.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
prev parent reply other threads:[~2005-03-13 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 0:33 [PATCH 2/6] fbcon: Stop framebuffer operations before hardware is properly initialized Antonino A. Daplas
2005-03-13 23:07 ` Benjamin Herrenschmidt [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=1110755235.5787.189.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.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 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.