From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] new problem with memcpy_mck routines
Date: Wed, 24 Jul 2002 23:59:37 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905830@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905782@msgid-missing>
It turns out that the screen corruption that Jesse and Alex saw was due to a
bug in generic console vga code. The scrup() functions uses memcpy to copy
overlapping memory area. By definition, memcpy() must not be used for
overlapping memory areas. This patch changed that to memmove() which
handles overlapping areas gracefully. This also fixes the same screen
corruption when switching from X server to text mode.
There is nothing wrong with new memcpy function.
--- drivers/char/console.c.orig Wed Jul 24 14:47:20 2002
+++ drivers/char/console.c Wed Jul 24 14:47:55 2002
@@ -259,7 +259,7 @@
return;
d = (unsigned short *) (origin+video_size_row*t);
s = (unsigned short *) (origin+video_size_row*(t+nr));
- scr_memcpyw(d, s, (b-t-nr) * video_size_row);
+ scr_memmovew(d, s, (b-t-nr) * video_size_row);
scr_memsetw(d + (b-t-nr) * video_num_columns, video_erase_char,
video_size_row*nr);
}
One other question, who is the maintainer for the console code? This should
go into the base as it is not ia64 specific and could potentially trigger on
other architectures.
- Ken Chen
-----Original Message-----
From: Jesse Barnes [mailto:jbarnes@sgi.com]
Sent: Friday, July 19, 2002 9:37 AM
To: alex_williamson@hp.com
Cc: IA64 mailinglist; Chen, Kenneth W
Subject: Re: [Linux-ia64] new problem with memcpy_mck routines
I've run into this too on the console of the McKinley SDV machines. A
Control-L cleans it up, but it's really annoying nonetheless.
Jesse
On Thu, Jul 18, 2002 at 08:56:48PM -0600, Alex Williamson wrote:
>
> Using the latest memcpy_mck (20020622 + Ken's 7/10 patch) I'm seeing
> problems with screen corruption on VGA. Here's the test; on a VGA
> console, start vim (colorized syntax highlighting and all), edit a
> large file (several screens). Scroll down through the file. You'll
> notice the screen gets corrupted, appears to be columns down the screen
> that scroll faster than others. I'm using an HP McKinley system and
> have light switched tested by building w/ the old Itanium routines.
> Other apps like less, nvi, etc... don't seem to trigger this. Thanks,
>
> Alex
next prev parent reply other threads:[~2002-07-24 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 2:56 [Linux-ia64] new problem with memcpy_mck routines Alex Williamson
2002-07-19 16:37 ` Jesse Barnes
2002-07-24 23:59 ` Chen, Kenneth W [this message]
2002-07-26 16:42 ` David Mosberger
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=marc-linux-ia64-105590701905830@msgid-missing \
--to=kenneth.w.chen@intel.com \
--cc=linux-ia64@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