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 23:07:28 +0200 [thread overview]
Message-ID: <BA82E1E583C@vcnet.vc.cvut.cz> (raw)
On 22 Jul 02 at 23:00, Sven wrote:
> > Just put it into vc_screenbuf after register_framebuffer() returns, and
> > force redraw...
>
> mmm, will try.
>
> BTW, how can i force a redraw from pm3fb ?
>
> > If you'll override save_screen, and you'll put set_origin() into visual_init,
>
> NO, just tried, i got no more display, and the box hanged ...
Oops. fbcon_set_origin will call scrolldelta which ... So what about simple
origin = screenbuf in visual_init ? It should have no side effects.
> How i do it :
>
> i copy the data in pm3fb just after i first map the framebuffer. i hold it in a special
> array in pm3fb (for now).
>
> But then, maybe i should see if the location of the set_origin should be changed, maybe i could do it in vc_resize for now.
>
> BTW, in the first case, i will see the screen flashing shortly with the garbage i see now, and then work ok, isn't it ?
Yes.
> And i would need to handle resolution changes myself ?
Yes. Or you can copy data just line by line, instead of like one big chunk.
Yes, it is duplicating of vc_resize code.
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 21:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 21:07 Petr Vandrovec [this message]
2002-07-22 21:10 ` Re: board with broken vga Sven
2002-07-23 14:35 ` Sven LUTHER
-- strict thread matches above, loose matches on Subject: below --
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:54 Petr Vandrovec
2002-07-22 19:58 ` 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=BA82E1E583C@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).