Well, here's a first version. It's still blocked by #45593 and #52019, but I thought I'd put it in anyway.
Created attachment 32082 [details] power-management.xml
Created attachment 32083 [details] images/energy-budget.png
I used the instructions provided in this document and it worked really great for me!
I'll keep a close look at this; hopefully the depending bugs are resolved in a timely manner. Don't try circumventing those bugs, they provide the best solution afaik.
Bug #45593 shouldn't be a real problem, it just needs a maintainer. I'll have a look whether the init script changed for 2.6.7 and attach it there if appropriate. On the other hand, bug #52019 depends on bug #51696, which is marked as WONTFIX now. I'm afraid it'll take some time until the swsusp2 developers have rewritten their code in a way the kernel folk like, if they'll ever do.
The linked guide circumvents both bugs now. If there are no objections against it, I'll have another look at the guide and attach it here. Once (read: if at any time) laptop-mode is in portage, I'll update the howto.
The guide looks really good. I would only change one thing: where you use indentations in all those Code Listings, change your TABs (which are interpreted as 8 chars wide on most browsers) to spaces and only use 2 spaces for each indentation. Otherwise the Code Listings become too wide and make some browsers scroll horizontally (which users don't like). And please attach it; I'm dying to put this one online.
Created attachment 37252 [details] power-management.xml Ok, here you are, 1111 lines of bloody XML. Polished it up once again and did loads of changes according to the coding guidelines (/me still thinks Bug #52440 and http://www.stud.uni-karlsruhe.de/~uxhz/gentoo/misc/xmlformat.conf would be a nice addition), tabs fixed as well. Ready for bug reports now ;-)
> Anyway, the docs themselves still have the 1.0 version in the sourcecode > (you know, as <!-- ... --> comment). I'm not going to change that one as > that would be illegal (I'm not entitled to change documents' license if I'm > not the author) but could those of you who are authors of certain documents > just say "yay" if you're fine with the 2.0 version? Yay
Thanks for the nice doc. Attached you will find the edited version. Mainly: 1. Finish <p>...</p> before starting a <table> or <pre> or similar. 2. Use <p>...</p> <p>...</p> instead of <p>... <br/> ... </p> 3. Some coding style (removed too many newlines) 4. Used better <pre> layout: <pre caption="foobar"> # <i>some command</i> </pre> instead of <pre caption="foobar"> some command </pre> 5. Mark comments as comments, so <pre caption="foobar"> <comment># This is a comment</comment> ... </pre> 6. Use > for ">" signs where possible. Even though it doesn't give an error, it's seen as "Good Design" for XML documents. 7. Use (...) inside comments when they are in between commands: <pre caption="foobar"> <comment>(This is a comment)</comment> # <i>command</i> </pre> I've also committed it to CVS and linked it from the desktop documentation references.
Created attachment 38424 [details] Power Management Guide Updated version; the image has also been committed.
