[Trac #767] Battery test in OFW will happened problem.

[Zarro Boogs per Child]

#767: Battery test in OFW will happened problem.
---------------------------------+------------------------------------------
 Reporter:  garysu               |        Owner:  wmb at firmworks.com
     Type:  defect               |       Status:  closed           
 Priority:  normal               |    Milestone:  BTest-3          
Component:  ofw - open firmware  |   Resolution:  fixed            
 Keywords:                       |  
---------------------------------+------------------------------------------
Changes (by wmb at firmworks.com):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 OFW remembers the state of the RTC "bad battery" bit in a CMOS RAM
 location and
 only clears a bad-battery indication when you set the RTC date and time
 with
 the OFW "set-time" method.  The intention is to let you know that the date
 information in the RTC is invalid.

 That "sticky bad battery" feature has been a lot of trouble, so I am
 turning it off in the OFW source code.  The next OFW release will have it
 off, so that you will only see the "bad battery" status if the battery was
 bad at this power-up.

 OFW will not try to keep track of whether the data and time is valid after
 this change.

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