From: Knut Petersen <Knut_Petersen@t-online.de>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Detect switching to X?
Date: Mon, 28 Nov 2005 09:12:35 +0100 [thread overview]
Message-ID: <438ABBF3.20104@t-online.de> (raw)
In-Reply-To: <438AB24C.60405@gmail.com>
Hi Tony,
>The patch is not really palatable. It is a patch that attempts to fix
>bugs in X, not fbcon. Unless the problem is really widespread, then maybe
>I'll go for it for mainline.
>
>
>
>You need not do that (do a periodic check). A set_par() will always be
>called by fbcon whenever the console transitions from KD_GRAPHICS to
>KD_TEXT. So all you need to do is possibly check some register that says
>the hardware is in legacy mode.
>
>
The problem is _not_ the transition KD_GRAPHICS to KD_TEXT, that is handled
perfectly well. The problem is that after switching from KD_TEXT to
KD_GRAPHICS
the trident X driver is unable to set the correct screen start address
because cyblafb
disabled the bits of several registers the trident driver uses for that
purpose.
If I would submit a patch to the X team to enhance the trident driver,
that would only
solve the problem for those that use that new driver. I would have to
wait several years
until I could be reasonably sure not to break the system of too many people.
Even without that problem it would be nice to inform the framebuffer
drivers about
an ongoing switch to/from KD_GRAPHICS. Now there often is garbage displayed
for some fractions of a second while switching to X, that could be
prevented if the
framebuffer drivers would have the chance to e.g. clear the whole
framebuffer memory
before the X driver starts to switch video mode etc.
Today framebuffer drivers are limited by the fact that they need to
leave the graphics
engine in a state that current and older (but still used) X drivers can
handle. That
unreasonable limitation should be removed, and it can be removed by
those optional
fb_save_state() and fb_restore_state() hooks.
cu,
Knut
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2005-11-28 8:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-27 6:12 Detect switching to X? Knut Petersen
2005-11-27 22:38 ` Antonino A. Daplas
2005-11-28 5:54 ` Knut Petersen
2005-11-28 7:31 ` Antonino A. Daplas
2005-11-28 8:12 ` Knut Petersen [this message]
2005-11-28 8:27 ` Antonino A. Daplas
2005-11-28 8:50 ` Antonino A. Daplas
2005-11-28 13:46 ` Knut Petersen
2005-11-28 14:25 ` Antonino A. Daplas
2005-11-28 15:12 ` Knut Petersen
2005-11-28 15:39 ` Antonino A. Daplas
2005-11-28 22:17 ` Knut Petersen
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=438ABBF3.20104@t-online.de \
--to=knut_petersen@t-online.de \
--cc=adaplas@gmail.com \
--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.