#10137 NORM Not Tri: 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:  Not Triaged  
          Component:  kernel     |     Version:  not specified
         Resolution:             |    Keywords:               
        Next_action:  never set  |    Verified:  0            
Deployment_affected:             |   Blockedby:               
           Blocking:             |  
---------------------------------+------------------------------------------

Comment(by corbet):

 If you're building both kernels out of the same source tree, then, yes,
 one of them will require a boot-time parameter at this point.  I could
 also make the parameter runtime writeable so that the system init code
 could tweak it.

 The problem is that the decision needs to be made at the ov7670 level,
 where there's not really any platform-level information available.  I
 don't *think* there is anything to read from the sensor itself to tell
 them apart.  The ov7670 driver is used outside of OLPC, so I need to be
 careful about putting OLPC-specific tweaks into it.

 That said, I guess we could just put in something like this:

 #ifdef CONFIG_OLPC_XO_1_5
 static int max_frame_rate = 90;
 #else
 static int max_frame_rate = 30;
 #endif

 I hate adding more ifdefs, but that might be the most straightforward
 solution here.

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