EDIT - bah, ASCII diagram didn't work ;(
Last edited by bridgman; 12-22-2008 at 11:07 PM.
Geez... I was just being silly. No need to drive home an obvious point. I hope you didn't burst a vein coming up with your response.It's fact that despite best intentions and planning thing don't always go as well as expected. Until actual implementation is actually out there and performing as well as expected it's pure speculation.
I highly doubt that somebody really needs kms. At least it does not matter for me if switching to a vt takes a few monents or if the default res is already the highest possible. Stability is much more important - also correct rendering and flickerfree videos/games when Vsync is enabled. The rest it nice to have, but not a requirement.
KMS is way more interesting to me than DRI2 is. GEM interests me most of all, of course. Without it, neither DRI2 nor KMS could really work.
Ok, I do not own a laptop, so I never use suspend. Hibernation/Suspend to Disk is useless anyway because you would read in worst case more data than you would do with a normal boot when you memory is big and used.
I guess the argument for suspend/resume is that it maintains your application state as well ?
The other advantage to KMS I see is that it puts all of the state info you need for good power management in one place. Right now the engine state is in drm (unless you're running without 3d) and the display state is in ddx, but you really need both to make on-the-fly power management decisions.