Messages in this thread | | | Date | Tue, 29 Jul 2003 17:55:18 +0100 (BST) | From | James Simmons <> | Subject | Re: [PATCH] Framebuffer: client notification mecanism & PM |
| |
> > matroxfb tried to use a 'dead' for handling hot removal, but your code > > looks definitely saner > > 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.
I knew it was a matter of time before "client" management would happen. Is this a 2.6.X thing tho or shoudl we wait for the next developement cycle. I don't mind working on experimental stuff.
- 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/
| |