Messages in this thread | | | Date | Thu, 15 Mar 2001 09:21:06 +0100 (CET) | From | Geert Uytterhoeven <> | Subject | Re: [Linux-fbdev-devel] [RFC] fbdev & power management |
| |
On Wed, 14 Mar 2001, James Simmons wrote: > >>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).
[...]
> As for fbcon knowing when it is asleep. Hum. We could have a flags to > tell it to have text data updates to be placed in the shadow buffer > (struct vc_datas->vc_screenbuffer) only;
Very simple to implement in the fbdev itself: just replace the drawing ops by dummy drawing ops.
This can already be done now, by providing a dummy struct display_switch, and in the future by providing dummy accels.
Gr{oetje,eeting}s,
Geert
-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In 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/
| |