#9694 NORM Not Tri: Openchrome lies about memory speed

[Zarro Boogs per Child]

#9694: Openchrome lies about memory speed
-----------------------------------------+----------------------------------
           Reporter:  wmb at firmworks.com  |       Owner:  jnettlet                          
               Type:  defect             |      Status:  new                               
           Priority:  normal             |   Milestone:  Not Triaged                       
          Component:  x window system    |     Version:  Development source as of this date
         Resolution:                     |    Keywords:                                    
        Next_action:  code               |    Verified:  0                                 
Deployment_affected:                     |   Blockedby:                                    
           Blocking:                     |  
-----------------------------------------+----------------------------------
Changes (by wmb at firmworks.com):

  * owner:  wmb at firmworks.com => jnettlet
  * status:  assigned => new
  * version:  Development firmware => Development source as of this date
  * component:  ofw - open firmware => x window system
  * milestone:  1.5-firmware => Not Triaged


Comment:

 I am reassigning this to "x-window-system", as the closest proxy for the
 real culprit which is the openchrome driver.

 That driver needs to use a timing methodology that is unaffected by CPU
 throttling, for example the ACPI timer register or maybe HPETs.  Comment
 #4 cites the deficient routine.

-- 
Ticket URL: <http://dev.laptop.org/ticket/9694#comment:6>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system