Messages in this thread | | | Subject | Re: [Linux-fbdev-devel] [RFC] fbdev & power management | From | Brad Douglas <> | Date | 14 Mar 2001 12:57:20 -0800 |
| |
On 14 Mar 2001 14:39:57 +0100, Geert Uytterhoeven wrote: > On Wed, 14 Mar 2001, Benjamin Herrenschmidt wrote: > > >I think registering fbcon as a PM client and doing the above when the > > >fbdev suspend/resume hooks are called should work. A memory backup is > > >worked on until the resume is run and the backup is restored to the > > >display. > > > > > >So the fbdev drivers would register PM with fbcon, not PCI, correct? > > > > Either that, or the fbdev would register with PCI (or whatever), _and_ > > fbcon would too independently. In that scenario, fbcon would only handle > > things like disabling the cursor timer, while fbdev's would handle HW > > issues. THe only problem is for fbcon to know that a given fbdev is > > asleep, this could be an exported per-fbdev flag, an error code, or > > whatever. In this case, fbcon can either buffer text input, or fallback > > to the cfb working on the backed up fb image (that last thing can be > > handled entirely within the fbdev I guess). > > I'd go for a fallback to dummycon. It's of no use to waste power on creating > graphical images of the text console when asleep. And the fallback to dummycon > is needed anyway while a fbdev is opened (in 2.5.x).
But wouldn't falling back to dummycon prevent the driver specific suspend/resume calls from working? Or at a minimum, make handling those calls more complex?
No, there does not need to be graphical images of the text console -- a simply text buffer would suffice. But what about things like GTKFb and Embedded QT? They would certainly benefit from having a backup screen image, right? I do not believe there is any way to determine if the console is in fact in a 'text' or graphical state.
Brad Douglas brad@neruo.com http://www.linux-fbdev.org
- 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/
| |