#10251 NORM Not Tri: Bayer-mode imaging is broken on XO-1.5

[Zarro Boogs per Child]

#10251: Bayer-mode imaging is broken on XO-1.5
--------------------------+-------------------------------------------------
 Reporter:  bemasc        |                 Owner:               
     Type:  defect        |                Status:  new          
 Priority:  normal        |             Milestone:  Not Triaged  
Component:  not assigned  |               Version:  not specified
 Keywords:                |           Next_action:  never set    
 Verified:  0             |   Deployment_affected:               
Blockedby:                |              Blocking:               
--------------------------+-------------------------------------------------
 On the XO-1, Bayer imaging was always slightly broken.  If you captured a
 Bayer image immediately after boot you got images that looked like
 xo1-immediate.png.  There was a workaround though; if you opened the
 device in YUYV, and then closed it, subsequent captures in Bayer mode
 would work fine (xo1-workaround.png).  This was an annoying
 driver/hardware bug, but at least it had a workaround.

 On the XO-1.5, Bayer mode imaging is much more badly broken.  In
 particular, the images have the wrong size.  The workaround from the XO-1
 does not have a helpful effect.

 I discovered this problem while writing a simple command-line Bayer image
 capture program for the XO, which you can get at
 http://git.sugarlabs.org/projects/still-
 life/repos/mainline/blobs/master/capture.c (note: that's an HTML page).
 It produced all 4 of these files, invoked as

 capture -d /dev/video0 -w 10 -o /tmp/outfile.pgm

 The kernels that produced these images are respectively

 2.6.25-20090223.1.olpc.69098d87d56945c
 and
 2.6.31_xo1.5-20100423.1840.1.olpc.2884b56

 I can reflash the machines and retest with newer kernels if that's
 helpful.

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