From: Knut Petersen <Knut_Petersen@t-online.de>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
Andrew Morton <akpm@osdl.org>,
benh@kernel.crashing.org
Subject: Re: BUG: fb_imageblit called before fb_check_var and fb_set_par function
Date: Fri, 26 Aug 2005 20:21:06 +0200 [thread overview]
Message-ID: <430F5D92.4080300@t-online.de> (raw)
In-Reply-To: <430F4AC2.70403@gmail.com>
> This has been discussed before. Not all hardware can do a set_par()
> instantaneously, some may require seconds. And that will become a
> usability
> problem. Just imagine switching from one console to another and it takes
> 5 seconds.
That would be unacceptable, agreed. But it´s also not really acceptable
to risk to execute a few
dozend imageblits in redraw_screen() while the hardware might be in an
unusable state. Checking
for that situation every imageblit would have a big performance penalty.
knut
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-26 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 12:26 BUG: fb_imageblit called before fb_check_var and fb_set_par function Knut Petersen
2005-08-25 14:05 ` Antonino A. Daplas
2005-08-25 15:59 ` Knut Petersen
2005-08-25 18:09 ` Antonino A. Daplas
2005-08-26 8:23 ` Knut Petersen
2005-08-26 14:01 ` Antonino A. Daplas
2005-08-26 16:30 ` Knut Petersen
2005-08-26 17:00 ` Antonino A. Daplas
2005-08-26 18:21 ` Knut Petersen [this message]
2005-08-27 0:36 ` Antonino A. Daplas
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=430F5D92.4080300@t-online.de \
--to=knut_petersen@t-online.de \
--cc=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.