All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <rpurdie@rpsys.net>
To: adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH 4/9] fbcon/fbdev: Add blanking notification
Date: Wed, 12 Jan 2005 10:43:08 -0000	[thread overview]
Message-ID: <009001c4f893$87964630$0f01a8c0@max> (raw)
In-Reply-To: 20041221213648.89B701A0278@smtp-1.hotpop.com

Tony,

I've just switched to using this patch when I updated to 2.6.11-rc1 and I've 
noticed a problem. Basically my code which is monitoring FB_EVENT_BLANK 
events doesn't see any.

> diff -Nru a/drivers/video/console/fbcon.c b/drivers/video/console/fbcon.c
> --- a/drivers/video/console/fbcon.c 2004-11-17 18:15:17 +08:00
> +++ b/drivers/video/console/fbcon.c 2004-12-21 05:55:41 +08:00
[...]
> + if (ops->blank_state != blank) {
> + if (info->fbops->fb_blank &&
> +     info->fbops->fb_blank(blank, info))
> + fbcon_generic_blank(vc, info, blank);
> +
> + ops->blank_state = blank;
> + }

I think this is the problem (in fbcon.c). Instead of calling 
info->fbops->fb_blank(blank, info)), I think this should call fb_blank(info, 
blank) (in fbmem.c) which can then make the fbops call itself.

If you agree, I'll send a patch (or you can patch it - I don't mind). Let me 
know...

Richard 



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

  reply	other threads:[~2005-01-12 10:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21 21:35 [PATCH 4/9] fbcon/fbdev: Add blanking notification Antonino A. Daplas
2005-01-12 10:43 ` Richard Purdie [this message]
2005-01-12 20:24   ` 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='009001c4f893$87964630$0f01a8c0@max' \
    --to=rpurdie@rpsys.net \
    --cc=adaplas@pol.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.