linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: jsimmons@infradead.org
Cc: Antonino Daplas <adaplas@pol.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Fbdev development list 
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [Linux-fbdev-devel] Re: FBdev updates.
Date: Sun, 9 Mar 2003 22:29:03 +0100	[thread overview]
Message-ID: <20030309212903.GC16578@vana.vc.cvut.cz> (raw)
In-Reply-To: <20030304212906.GA1115@middle.of.nowhere>

Hi James,
  I tried to use fb_cursor and I have quite a lot problems with
it:
(1) it uses global variables for storing last cursor value -
    - but there is no global hardware, so after switching from
    one fbdev to another you can have cursor with wrong shape,
    wrong color and so on...
(2) callback from timer for cursor blinking may set almost any
    FB_CUR_* bits. But in this case fb_cursor callback may be
    called from interrupt context, while accelerator is busy
    and so on... Did I miss some synchronization? Best for me
    would be disabling blinking code in fbcon completely:
    in VGA mode cursor blinks automatically, and in graphics mode
    more lightweight only 'flash' callback is more appropriate
    for me. But then there is problem with
(3) cursor_undrawn... I have no idea how is this supposed to work
    if fbdev provides hardware cursor... And HZ/50 delay after
    putcs makes orientation on screen very complicated, as there
    is no cursor while new characters are appearing on screen.
    
					Thanks,
						Petr Vandrovec
						vandrove@vc.cvut.cz

  parent reply	other threads:[~2003-03-09 21:18 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20  1:09 FBdev updates James Simmons
2003-02-20  1:17 ` Jeff Garzik
2003-02-20  1:22   ` James Simmons
2003-02-20 15:02 ` Dave Jones
2003-02-20 15:07   ` James Simmons
2003-02-20 18:29   ` Petr Vandrovec
2003-02-20 19:03     ` Jurriaan
2003-02-20 19:58     ` James Simmons
2003-02-20 22:00       ` [Linux-fbdev-devel] " Antonino Daplas
2003-02-21  9:09         ` Geert Uytterhoeven
2003-02-21 10:46           ` Antonino Daplas
2003-02-21 11:02             ` Geert Uytterhoeven
2003-02-21  1:45       ` David S. Miller
2003-02-21  9:04         ` [Linux-fbdev-devel] " Geert Uytterhoeven
2003-02-21  0:24     ` Antonino Daplas
2003-03-03 20:35       ` Petr Vandrovec
2003-03-03 21:25         ` Geert Uytterhoeven
2003-03-03 21:32         ` Antonino Daplas
2003-03-05 20:23           ` James Simmons
2003-03-06  1:18             ` Antonino Daplas
2003-03-04 21:29         ` Jurriaan
2003-03-04 21:46           ` Petr Vandrovec
2003-03-09 21:29           ` Petr Vandrovec [this message]
2003-03-09 22:27             ` Antonino Daplas
2003-03-09 22:54               ` Petr Vandrovec
2003-03-09 23:44                 ` Antonino Daplas
2003-03-11 15:31             ` James Simmons
2003-03-05 20:22         ` James Simmons
2003-03-06  7:35           ` Sven Luther
2003-03-06  8:05             ` Antonino Daplas
2003-03-06  8:25               ` Sven Luther
2003-03-28 14:19         ` 2.5.66 fbdev performance (was Re: Re: FBdev updates) Petr Vandrovec
2003-03-28 18:50           ` [Linux-fbdev-devel] " Antonino Daplas
2003-02-20 15:10 ` FBdev updates Ivan Kokshaysky
  -- strict thread matches above, loose matches on Subject: below --
2003-03-05 20:31 [Linux-fbdev-devel] " Petr Vandrovec
2003-03-04 21:53 Petr Vandrovec
2002-06-05 16:50 fbdev updates Russell King
2002-06-05 17:21 ` [Linux-fbdev-devel] " James Simmons

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=20030309212903.GC16578@vana.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=adaplas@pol.net \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --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;
as well as URLs for NNTP newsgroup(s).