#1461 LOW Trial-2: Screen not blank after idle it for more than then minutes in command mode.

[Zarro Boogs per Child]

#1461: Screen not blank after idle it for more than then minutes in command mode.
---------------------------+------------------------------------------------
  Reporter:  chiaying.lin  |       Owner:  jfuhrer
      Type:  defect        |      Status:  new    
  Priority:  low           |   Milestone:  Trial-2
 Component:  kernel        |     Version:         
Resolution:                |    Keywords:         
  Verified:  0             |  
---------------------------+------------------------------------------------
Changes (by JordanCrouse):

  * priority:  normal => low

Comment:

 This is probably because the console blank code doesn't understand the
 console.  Right now, we only do the normal blank process as per VESA (kill
 vsync, kill hsync, kill DACS, in that order as the sleep get
 sprogressively deeper).  Since the DCON continues to display regardless,
 losing hsync and vsync without putting the DCON into a quiet state results
 in badness on the screen.

 The gut reaction would be to add DCON support into the fb_blank hooks in
 gxfb and lxfb, but we've worked really hard to keep the framebuffer
 drivers separate from the DCON, and this is just too low-priority to break
 that separation now.

 Luckily, we have an alternative - the kernel guys have a notifier chain
 for FB events - we can hook the DCON driver into that, and do the
 appropriate sleep routines there.  It would glitch slightly, but thats
 probably not an issue here, since this isn't in the normal usage path.
 I'm lowering the priority though - we have some more important things to
 look at first.

-- 
Ticket URL: <http://dev.laptop.org/ticket/1461#comment:5>
One Laptop Per Child <http://laptop.org/>