public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] new problem with memcpy_mck routines
Date: Fri, 26 Jul 2002 16:42:23 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905838@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905782@msgid-missing>

>>>>> On Wed, 24 Jul 2002 16:59:37 -0700, "Chen, Kenneth W" <kenneth.w.chen@intel.com> said:

  Ken> It turns out that the screen corruption that Jesse and Alex saw
  Ken> was due to a bug in generic console vga code.  The scrup()
  Ken> functions uses memcpy to copy overlapping memory area.  By
  Ken> definition, memcpy() must not be used for overlapping memory
  Ken> areas.  This patch changed that to memmove() which handles
  Ken> overlapping areas gracefully.  This also fixes the same screen
  Ken> corruption when switching from X server to text mode.

  Ken> There is nothing wrong with new memcpy function.

Ah, that's good!  Thanks for confirming this.


  Ken> One other question, who is the maintainer for the console code?
  Ken> This should go into the base as it is not ia64 specific and
  Ken> could potentially trigger on other architectures.

Have you tried Martin Mares?  He is listed as SVGA maintainer and has
at least on occasion hacked on that file.  In any case, I'd definitely
cc lkml so that others can see this report, too.

	--david


      parent reply	other threads:[~2002-07-26 16:42 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
2002-07-26 16:42 ` David Mosberger [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=marc-linux-ia64-105590701905838@msgid-missing \
    --to=davidm@napali.hpl.hp.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