From: Knut Petersen <Knut_Petersen@t-online.de>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Andrew Morton <akpm@osdl.org>,
"Antonino A. Daplas" <adaplas@gmail.com>,
benh@kernel.crashing.org
Subject: Re: BUG: fb_imageblit called before fb_check_var and fb_set_par function
Date: Fri, 26 Aug 2005 18:30:31 +0200 [thread overview]
Message-ID: <430F43A7.5000103@t-online.de> (raw)
In-Reply-To: <430F20D2.4060601@gmail.com>
Hi Antonino,
> ...and the driver happily draws to the screen. No bug.
> I believe, from here on, everything will work as expected.
>
> So it seems that when kdm loads the first time, it failed to set the
> mode to KD_GRAPHICS which triggered the bug. Maybe it's a bug in
> kdm then?
Well, it might be a kdm bug, but that bug is widely spread then. SuSE
9.2 and Debian Sarge
are affected at least. I would call it a kernel design flaw / bug if we
allow this kind of
situation to happen. But why does this happen only if kdm is started
early? This question
must be answered. Even if the answer is that kdm does something wrong,
it would be
a good idea to call e.g. *fb_set_par() unconditionally for every console
switch ...
cu,
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 16:27 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 [this message]
2005-08-26 17:00 ` Antonino A. Daplas
2005-08-26 18:21 ` Knut Petersen
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=430F43A7.5000103@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.