linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Finally found why 2.6.x has troubles with taking over vgacon
Date: Sun, 4 Jul 2004 08:58:22 +0800	[thread overview]
Message-ID: <200407040858.22088.adaplas@hotpop.com> (raw)
In-Reply-To: <20040703195613.GA30739@vana.vc.cvut.cz>

On Sunday 04 July 2004 03:56, Petr Vandrovec wrote:
> Hi Antonio,
>   yesterday I finally found why 2.6.x has problems with taking over vgacon.
> Problem is that take_over_console does:
>
>
>   if (IS_VISIBLE)
>     save_screen(i);
>   ...
>   visual_init(i, 0);
>   ...
>
> so code nicely saves screen contents, and calls visual_init, which calls
> fbcon's init, which in turn can issue vc_resize. And this vc_resize will
> trigger read from vc->vc_origin. But vc_origin still points to videomemory,
> not to the buffer where save_screen() copied its data.
>
>   In my fbcon
> (http://platan.vc.cvut.cz/ftp/pub/linux/matrox-latest/matroxfb-2.6.7-c1784.
>tar.gz) after I put
>
>   origin = visual_origin = screenbuf;
>
> below save_screen call, and removed clearing screen from radeon sources
> both radeonfb and matroxfb were able to take over vgacon, without any
> randomly colored characters on screen.

Petr, excellent detective work :-) .  I was suspecting vc_resize() was partly
causing the corruption, but never knew the reason until you pointed this

>
>   It also allows for removing special fillrect clear, as now code
> which clears upper few lines of logo area actually works...

Yes, I can now finally remove that ugly fillrect code.  I'll submit a patch on the
next batch of mm or BK release. 

Thanks.

Tony




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

      reply	other threads:[~2004-07-04  0:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-03 19:56 Finally found why 2.6.x has troubles with taking over vgacon Petr Vandrovec
2004-07-04  0:58 ` Antonino A. Daplas [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=200407040858.22088.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=vandrove@vc.cvut.cz \
    /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).