From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Sven <luther@dpt-info.u-strasbg.fr>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: board with broken vga ...
Date: Mon, 22 Jul 2002 19:54:43 +0200 [thread overview]
Message-ID: <BA4F7734912@vcnet.vc.cvut.cz> (raw)
On 22 Jul 02 at 19:46, Sven wrote:
> 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.
drivers/char/console.c:set_origin(), vc_resize(), ...
> is vc_screenbuf still part of the framebuffer memory, i thought it was some other main memory, a ...
vc_screenbuf is alloc_bootmem() or kmalloc(if screen resize happens) memory.
vgacon uses its own vgacon_set_origin(), which sets vc_origin to
VGA framebuffer, while with fbcon it sets vc_origin to vc_screenbuf.
> 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 ?).
scr_write() will take a care of byteswapping. If in 8bit characters,
upper 8 bits are attr, low 8 bits is character.
> 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.
Just idea: force your fbdev to use same resolution as vgacon
(80x25, 640x400, or change vgacon resolution to 80x30 if your fbdev uses
640x480) so that vc_resize path is not triggered. It does some copying
too.
Petr
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next reply other threads:[~2002-07-22 17:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 17:54 Petr Vandrovec [this message]
2002-07-22 19:58 ` Re: board with broken vga Sven
-- strict thread matches above, loose matches on Subject: below --
2002-07-22 21:07 Petr Vandrovec
2002-07-22 21:10 ` Sven
2002-07-23 14:35 ` Sven LUTHER
2002-07-22 20:45 Petr Vandrovec
2002-07-22 21:00 ` Sven
2002-07-22 20:18 Petr Vandrovec
2002-07-22 20:40 ` Sven
2002-07-22 17:35 Petr Vandrovec
2002-07-22 17:46 ` Sven
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=BA4F7734912@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=luther@dpt-info.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).