From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Sven LUTHER <luther@lambda.u-strasbg.fr>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: board with broken vga ...
Date: Mon, 22 Jul 2002 19:35:00 +0200 [thread overview]
Message-ID: <BA4A3C769DD@vcnet.vc.cvut.cz> (raw)
On 22 Jul 02 at 19:23, Sven LUTHER wrote:
> Petr wrote :
> > your drivers's init
> > --> look and init devices
> > --> call register_framebuffer
> > --> VGACON reads contents of VGA buffer
> > --> call to fbdev setvar
> > --> upper layer restores screen
> > ...
>
> Mmm, i did manage to override the vga save_screen function, and copy the
> good values into vc_sceenbuf, but to no avail.
>
> What frustrates me is that i cannot find any reference to some piece of
> code using the data in vc_sceenbuf to write to the screen again.
>
> How exactly does the upper layer restore the screen ?
I thought that:
take_over_console -> update_screen(x) -> redraw_screen(x,0) ->
(1) set vc_origin to vc_screenbuf in set_origin()
(2) paint picture through do_update_region() -> con_getxy, con_putcs
vc_screenbuf is accessed through screenbuf macro from console_macros.h.
It is very hard to find anything in console.c. I use simple rule:
all X variables you see in function are vc_X members of vt struct unless
you see definition of X on your screen.
Petr Vandrovec
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next reply other threads:[~2002-07-22 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 17:35 Petr Vandrovec [this message]
2002-07-22 17:46 ` Re: board with broken vga Sven
-- strict thread matches above, loose matches on Subject: below --
2002-07-22 17:54 Petr Vandrovec
2002-07-22 19:58 ` Sven
2002-07-22 20:18 Petr Vandrovec
2002-07-22 20:40 ` Sven
2002-07-22 20:45 Petr Vandrovec
2002-07-22 21:00 ` Sven
2002-07-22 21:07 Petr Vandrovec
2002-07-22 21:10 ` Sven
2002-07-23 14:35 ` Sven LUTHER
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=BA4A3C769DD@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=luther@lambda.u-strasbg.fr \
/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).