From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Framebuffer: client notification mecanism & PM
Date: 29 Jul 2003 09:59:00 -0400 [thread overview]
Message-ID: <1059487140.8537.35.camel@gaston> (raw)
In-Reply-To: <89CD6530893@vcnet.vc.cvut.cz>
On Tue, 2003-07-29 at 09:39, Petr Vandrovec wrote:
> Oops... You probably did not want IBM LCD diffs in fbmem.c posted.
>
> matroxfb tried to use a 'dead' for handling hot removal, but your code
> looks definitely saner
Hrm... right, that ibmlcd bit can go ;) Hopefully someone else will
get the real ibmlcd driver in sooner or later...
My code wasn't really intended to deal with hot-removal, more with
"what happens if printk occurs during the Power Management suspend
sequence", but I tried to keep the notification mecanism simple
enough so it could be used for that as well. Also, indeed, the fbcon
changes should deal with hot-removal in some way (though you surely
also want to "deatch" from the fbdev's in this case).
Among other things that could be used for is live monitor insertion/
removal detection (some HW are able to do that), "pivot" monitor
kind of things, etc... typically via the mode_changed hook.
Ben.
next prev parent reply other threads:[~2003-07-29 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 13:39 [PATCH] Framebuffer: client notification mecanism & PM Petr Vandrovec
2003-07-29 13:59 ` Benjamin Herrenschmidt [this message]
2003-07-29 16:55 ` James Simmons
2003-07-29 20:22 ` Benjamin Herrenschmidt
2003-07-29 21:31 ` James Simmons
2003-07-30 12:22 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2003-07-29 13:13 Benjamin Herrenschmidt
2003-07-29 17:49 ` Pavel Machek
2003-07-30 12:14 ` Benjamin Herrenschmidt
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=1059487140.8537.35.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=VANDROVE@vc.cvut.cz \
--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).