public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 502] New: Broken cursor when using neofb
Date: Tue, 25 Mar 2003 11:57:42 -0800	[thread overview]
Message-ID: <1352210000.1048622262@flay> (raw)

http://bugme.osdl.org/show_bug.cgi?id=502

           Summary: Broken cursor when using neofb
    Kernel Version: 2.5.66
            Status: NEW
          Severity: normal
             Owner: jsimmons@infradead.org
         Submitter: jochen@jochen.org


Distribution: Debian sarge
Hardware Environment: IBM Thinkpad 600

Problem Description:

I use neofb, the boot messages are:
Mar 25 20:04:58 gswi1164 kernel: neofb: mapped io at c680d000
Mar 25 20:04:58 gswi1164 kernel: Autodetected internal display
Mar 25 20:04:58 gswi1164 kernel: Panel is a 1024x768 color TFT display
Mar 25 20:04:58 gswi1164 kernel: neofb: mapped framebuffer at c6a0e000
Mar 25 20:04:58 gswi1164 kernel: neofb v0.4.1: 2048kB VRAM, using 1024x768, 48.361kHz, 60Hz
Mar 25 20:04:58 gswi1164 kernel: fb0: MagicGraph 128XD frame buffer device
Mar 25 20:04:58 gswi1164 kernel: Console: switching to colour frame buffer device 128x48

On a vc the line cursor looks like
****** ** ********
instead of
****************** (the normally continous line is broken).
Emacs uses a block cursor that is broken similar, the block
is broken by two vertical bars.


             reply	other threads:[~2003-03-25 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25 19:57 Martin J. Bligh [this message]
2003-03-25 23:42 ` [Bug 502] New: Broken cursor when using neofb Alex Goddard
  -- strict thread matches above, loose matches on Subject: below --
2003-03-25 21:32 Petr Vandrovec

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=1352210000.1048622262@flay \
    --to=mbligh@aracnet.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