From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
Richard Purdie <rpurdie@rpsys.net>
Cc: adaplas@pol.net, zap@homelink.ru
Subject: Re: fbdev: Add FB_EVENT_BLANK to notify listeners of a blanking status change
Date: Tue, 30 Nov 2004 07:29:07 +0800 [thread overview]
Message-ID: <200411300729.10877.adaplas@hotpop.com> (raw)
In-Reply-To: <01f301c4d664$5c950440$0f01a8c0@max>
On Tuesday 30 November 2004 06:36, Richard Purdie wrote:
> Add FB_EVENT_BLANK to notify listeners of a blanking status change. This
> allows backlight drivers to be implemented completely separately from any
> framebuffer driver. The new blanking mode is passed in event.data.
Almost. Note that my intent is to notify the console of the blank status
_and_ do something about it, so we also need to do
'do_blank_screen/do_unblank_screen' at the fbcon level.
I already have a patch in my tree, and will submit it after 2.6.10 comes
out. But for now and for your own use, this will do just fine.
Tony
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-11-29 23:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 17:04 Default timings in vga16fb driver Martin Wilck
2004-11-24 16:16 ` Antonino A. Daplas
2004-11-25 14:55 ` Martin Wilck
2004-11-25 19:51 ` Antonino A. Daplas
2004-11-26 9:11 ` Geert Uytterhoeven
2004-11-27 14:53 ` FB_EVENT (blank and unblank?) Richard Purdie
2004-11-27 22:43 ` Antonino A. Daplas
2004-11-27 23:59 ` Richard Purdie
2004-11-28 0:24 ` Antonino A. Daplas
2004-11-28 0:59 ` Richard Purdie
2004-11-28 1:14 ` Antonino A. Daplas
2004-11-29 22:36 ` fbdev: Add FB_EVENT_BLANK to notify listeners of a blanking status change Richard Purdie
2004-11-29 23:29 ` Antonino A. Daplas [this message]
2004-11-29 10:53 ` cursor color changes ramprasad
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=200411300729.10877.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=rpurdie@rpsys.net \
--cc=zap@homelink.ru \
/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.