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).
Gr{oetje,eeting}s,
Geert
-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.orgIn personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
- 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/
This archive was generated by hypermail 2b29 : Thu Mar 15 2001 - 21:00:16 EST