Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@inai.de>
To: linux-fbdev@vger.kernel.org
Subject: fbdev: on-screen character cell corruption
Date: Wed, 31 Oct 2012 13:47:30 +0000	[thread overview]
Message-ID: <alpine.LNX.2.01.1210311423100.29232@nerf07.vanv.qr> (raw)

Hi,


I have here a 9x16 font (for use with e.g. videor0x400 on KMS to get 
80x25 tty size) that fbcon seems to have a problem correctly rendering. 
When backspacing, the pixels from the character under the cursor not 
only gets moved to one character cell to the left (as it should), but 
the leftmost pixel column of the char also leaks to the rightmost pixel 
column previous glyph.

LKML being a text/plain medium, I have taken pictures of the screen for 
better understanding on how to reproduce, and have placed them at 
http://inai.de/keyb/ . The font file is also provided there.

The kernel I run is 3.4.11 on x86_64. There is no known good version to 
me (IOW, it is not a regression), as I just started using a 9x16 font 
on fbcon.

                 reply	other threads:[~2012-10-31 13:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LNX.2.01.1210311423100.29232@nerf07.vanv.qr \
    --to=jengelh@inai.de \
    --cc=linux-fbdev@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