2010/1/8 Michael 'Mickey' Lauer <span dir="ltr"><<a href="mailto:mickey@vanille-media.de">mickey@vanille-media.de</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Am Donnerstag, den 07.01.2010, 21:57 +0100 schrieb Michal Brzozowski:<br>
<div class="im">> Sorry this has been documented somewhere. I'm playing with the<br>
> 'Display' resource, and I'm totally confused.<br>
<br>
</div>I can understand that. The semantics of the Display (and CPU) resource<br>
is somewhat different from the semantics of the other peripherals.<br>
<br>
The display resource is _not_ controlling the display. What it does<br>
instead is modifying the way the Idle Notifier works. When you claim the<br>
display resource, then the Idle Notifier IDLE_DIM (and subsequent<br>
states, such as LOCK and SUSPEND) will no longer be sent, hence the<br>
display will stay on and the device will not go into suspend.<br>
<div class="im"><br><br></div></blockquote><div> </div></div>Thanks! That explains everything :-)<br>