Messages in this thread | | | Subject | Re: [PATCH] Framebuffer: client notification mecanism & PM | From | Benjamin Herrenschmidt <> | Date | 29 Jul 2003 09:59:00 -0400 |
| |
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.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |