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