linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: "Geert.Uytterhoeven" <Geert.Uytterhoeven@sonycom.com>,
	Geoff Levand <geoffrey.levand@am.sony.com>
Subject: Re: unregister_framebuffer() and cursor
Date: Fri, 04 May 2007 17:42:02 +0800	[thread overview]
Message-ID: <1178271722.4722.11.camel@daplas> (raw)
In-Reply-To: <Pine.LNX.4.62.0705041045310.9684@pademelon.sonytel.be>

On Fri, 2007-05-04 at 10:50 +0200, Geert Uytterhoeven wrote:
> 	Hi,
> 
> It looks like unregister_framebuffer() doesn't cause fbcon_del_cursor_timer()
> to be called.
> 
> Hence if cursor_timer_handler() runs, it will try to schedule work on
> fb_info.queue, which is no longer valid, and queue_work() will BUG_ON().
> 
> Or am I missing something?

The console cursor is not part of fbdev.  fbcon_del_cursor_timer() is
done in fbcon_exit() in fbcon.c. You cannot (or, rather, should not)
call unregister_framebuffer() unless fbcon unbinds the underlying
driver.

Tony  



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

  reply	other threads:[~2007-05-04  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04  8:50 unregister_framebuffer() and cursor Geert Uytterhoeven
2007-05-04  9:42 ` Antonino A. Daplas [this message]
2007-05-25 10:13   ` Geert Uytterhoeven
2007-05-25 21:25     ` Antonino A. Daplas

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=1178271722.4722.11.camel@daplas \
    --to=adaplas@gmail.com \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=geoffrey.levand@am.sony.com \
    --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).