#10137 NORM 1.5-sof: XO-1.5 camera FPS limit inaccurate?

[Zarro Boogs per Child]

#10137: XO-1.5 camera FPS limit inaccurate?
---------------------------------+------------------------------------------
           Reporter:  dsd        |       Owner:  corbet             
               Type:  defect     |      Status:  new                
           Priority:  normal     |   Milestone:  1.5-software-update
          Component:  kernel     |     Version:  not specified      
         Resolution:             |    Keywords:                     
        Next_action:  never set  |    Verified:  0                  
Deployment_affected:             |   Blockedby:                     
           Blocking:             |  
---------------------------------+------------------------------------------

Comment(by corbet):

 Replying to [comment:7 cjb]:
 > Yeah, I think that's right.
 >
 > Something like "if (olpc_board_at_least(olpc_board(BOARD_XO_1_5_B1)))"
 seems preferable to the #ifdef, though, since we could imagine a single
 kernel that runs on both platforms.

 I've gotten really leery of OLPC-specific tweaks since breaking linux-next
 last week.  I can see why the above would appeal from the single-kernel
 perspective, but it is also likely to be hard to upstream.

 My preference would be the runtime-writeable module parameter; it could
 then be tweaked in the init code.  Failing that, we could do the above,
 but it has a real chance of remaining an OLPC-only patch.  Preference?

 Or you could just fix the sensor clock on the 1.5 :)

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