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 22:45:59 +0200 [thread overview]
Message-ID: <BA7D2B624A5@vcnet.vc.cvut.cz> (raw)
On 22 Jul 02 at 22:40, Sven wrote:
>
> What would solve my problem in the easiest way would be to have some
> framebuffer restore hook or something in the fbdev driver, which would get called
> in take_over_screen or something such, after the screen has been resized ?
Just put it into vc_screenbuf after register_framebuffer() returns, and
force redraw...
> Or Maybe simply tell vc_resize that we use a special way of reading the framebuffer.
>
> Or i should implement the trick you use for setting the card in
> graphic mode later on in the setvar stuff ?
If you'll override save_screen, and you'll put set_origin() into visual_init,
I believe that it will work:
(1) in take_over_console, copy data to screenbuf using your own save_screen.
(2) now vc_resize (with prior set_origin) will copy data from old screenbuf
to reallocated screenbuf (instead of from videoram to reallocated
screenbuf).
(3) and update_screen() will just paint data which are already on screen
if resolution changed. If resolutions matched, it will put data on the
screen.
Petr
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next reply other threads:[~2002-07-22 20:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 20:45 Petr Vandrovec [this message]
2002-07-22 21:00 ` 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: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=BA7D2B624A5@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).