From: Antonino Daplas <adaplas@pol.net>
To: Jochen Hein <jochen@jochen.org>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [2.5.42] screen corruption with vesafb
Date: 15 Oct 2002 02:47:45 +0800 [thread overview]
Message-ID: <1034621170.570.54.camel@daplas> (raw)
In-Reply-To: <874rbqzerv.fsf@gswi1164.jochen.org>
On Sun, 2002-10-13 at 20:47, Jochen Hein wrote:
>
> When running Emacs on a framebuffer console and inserting characters
> in the middle of a line, the character after the cursor get corrupted
> in two of three tries. A redraw (Ctrl-L) fixes it, so I suspect a
> framebuffer bug. I can provide a screenshot if there is a need.
>
I experienced similar problems before. In my case, this was due to
problems with cfbfillrect.c and cfbcopyarea.c.
Geert wrote similar routines in the CVS version of fbtest. I modified
them so they can be used as drop-in replacements for the kernel
framebuffer. See the thread "Console Rotation" last month.
Tony
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
parent reply other threads:[~2002-10-14 18:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <874rbqzerv.fsf@gswi1164.jochen.org>]
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=1034621170.570.54.camel@daplas \
--to=adaplas@pol.net \
--cc=jochen@jochen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).