From: izumi <izumi2005@soft.fujitsu.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][BUG] Fix the graphic corruption issue on IA64 machines
Date: Fri, 29 Jun 2007 12:27:52 +0900 [thread overview]
Message-ID: <46847C38.7000104@soft.fujitsu.com> (raw)
In-Reply-To: <4670A759.7090206@soft.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
HI,
As a result of the discussion with Pete Zaitcev(zaitcev@redhat.com),
I re-create a patch. This attached patch is revised version.
He pointed out that the former patch may violate the assumptions and
was not safe. Concretely speaking, he concerned that an unexpected
problem may arise somewhere if "blank_state", which is intended to
reflect the state of timer, was shuffled arround.
This revised patch reflects his pointed out. I confirmed this also fixed
the problem.
Regards,
Taku Izumi <izumi.taku@jp.fujitsu.com>
[-- Attachment #2: vt-blank-rev2.patch --]
[-- Type: text/plain, Size: 1649 bytes --]
Fix the graphic corruption issue on IA64 machines.
VGA console driver can misunderstand the current mode(Text/Graphic) under
"disable console blanking" setting. When "disable console blank" is set (blankinterval=0),
"do_unblank_screen()" function returns without changing "blank_state", and when
"blank_state" is "blank_off", "do_blank_screen() function returns without
invoking sw->con_blank() function. That's why VGA console driver can misunderstand
the current mode.
Signed-off-by: Nobuhiro Tachino <tachino@jp.fujitsu.com>
Signed-off-by: Pete Zaitcev <zaitcev@redhat.com>
Signed-off-by: Taku Izumi <izumi.taku@jp.fujitsu.com>
---
drivers/char/vt.c | 8 +++++---
1 files changed, 5 insertions(+), 3 deletions(-)
Index: linux-2.6.22/drivers/char/vt.c
=============================================================================
--- linux-2.6.22.org/drivers/char/vt.c 2007-06-27 11:40:03.000000000 -0400
+++ linux-2.6.22/drivers/char/vt.c 2007-06-27 11:24:32.000000000 -0400
@@ -3491,9 +3491,6 @@ void do_blank_screen(int entering_gfx)
}
return;
}
- if (blank_state != blank_normal_wait)
- return;
- blank_state = blank_off;
/* entering graphics mode? */
if (entering_gfx) {
@@ -3501,10 +3498,15 @@ void do_blank_screen(int entering_gfx)
save_screen(vc);
vc->vc_sw->con_blank(vc, -1, 1);
console_blanked = fg_console + 1;
+ blank_state = blank_off;
set_origin(vc);
return;
}
+ if (blank_state != blank_normal_wait)
+ return;
+ blank_state = blank_off;
+
/* don't blank graphics */
if (vc->vc_mode != KD_TEXT) {
console_blanked = fg_console + 1;
prev parent reply other threads:[~2007-06-29 3:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 2:26 [PATCH][BUG] Fix the graphic corruption issue on IA64 machines izumi
2007-06-29 3:27 ` izumi [this message]
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=46847C38.7000104@soft.fujitsu.com \
--to=izumi2005@soft.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
/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