Messages in this thread | | | From | Benjamin Herrenschmidt <> | Subject | Re: [Linux-fbdev-devel] [RFC] fbdev & power management | Date | Wed, 14 Mar 2001 15:05:50 +0100 |
| |
>> 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).
We do already have the backup image since we need to backup & restore the framebuffer content.
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/
| |