linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ondrej Zajicek <santiago@mail.cz>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Two bugs in fbcon?
Date: Tue, 23 May 2006 23:11:05 +0200	[thread overview]
Message-ID: <20060523211105.GA2190@localhost.localdomain> (raw)
In-Reply-To: <446E630E.9060500@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 930 bytes --]

On Sat, May 20, 2006 at 08:30:06AM +0800, Antonino A. Daplas wrote:
> Ondrej Zajicek wrote:
> > Now second strangeness - I am still on vt0 (immediately after modprobe fbcon),
> > but during calls to bitblit.c/bit_cursor display structure associated with
> > vt3 is used (in bitblit.c:244 - ops->p). Combined with previous strangeness
> > (bad vrows values in vt1-vt3) i get cursor visible on bad row.
> 
> Might be fixed in Linus's latest git tree.  Try applying this changeset:
> 
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=1a37d5f51020b9967d4b4094f6d627d0873a6469
> 
> Tony

Yes, this corrects it. Thank you.

-- 
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago@mail.cz, jabber: santiago@njs.netlab.cz)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2006-05-23 21:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-15 21:03 Two bugs in fbcon? Ondrej Zajicek
2006-05-20  0:30 ` Antonino A. Daplas
2006-05-20  1:40   ` Panning in the intelfb driver Dennis Munsie
2006-05-23 21:11   ` Ondrej Zajicek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-16 14:07 Two bugs in fbcon? Ondrej Zajicek

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=20060523211105.GA2190@localhost.localdomain \
    --to=santiago@mail.cz \
    --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).