Re: Re: board with broken vga ...

On 22 Jul 02 at 19:23, Sven LUTHER wrote:

Petr wrote :

quoted

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

PEtr wrote : 

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.

Well, i did search for screenbuf and not vc_screenbuf, and i did find the macros.

I did not find any reference in anything excepth vgacon_switch and vgacon_save_screen.

Also :

is vc_screenbuf still part of the framebuffer memory, i thought it was some other main memory, a ...

Mmm, i will have to look more at it, thanks for the info thpugh.

BAsically, i am now sure that i copy the right data to the screenbuf (well for the character data, i just use empty attributes, is that ok for now ?, where can i find the attribute format ?).

But it seems the problem is when copying the stuff back to the screen that something goes wrong.

I suspect that it is not the correct data (the one in screenbuf) that is taken or something like that.

But then, maybe i am worng (well most probably i am wrong).

Friendly,

Sven Luther:wq


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf