Comments on: A Dirty Hack for OpenCV on the OLPC XO http://eclecti.cc/olpc/a-dirty-hack-for-opencv-on-the-olpc-xo Sat, 27 Feb 2010 16:48:58 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Mitchell http://eclecti.cc/olpc/a-dirty-hack-for-opencv-on-the-olpc-xo/comment-page-1#comment-1314 Mitchell Tue, 04 Nov 2008 07:40:59 +0000 http://eclecti.cc/code/a-dirty-hack-for-opencv-on-the-olpc-xo#comment-1314 An alternative to compiling on a real XO is to compile in emulation, and then copy across the resulting files. For example, I've had an emulation image, with enlarged disk, and the full gcc toolchain. But cameras have not been supported in emulation, so that may not help here. And emulation isn't well supported by OLPC, so for the last few months, only qemu from CVS has been able to run current builds. An alternative to compiling on a real XO is to compile in emulation, and then copy across the resulting files. For example, I’ve had an emulation image, with enlarged disk, and the full gcc toolchain. But cameras have not been supported in emulation, so that may not help here. And emulation isn’t well supported by OLPC, so for the last few months, only qemu from CVS has been able to run current builds.

]]> By: nrp http://eclecti.cc/olpc/a-dirty-hack-for-opencv-on-the-olpc-xo/comment-page-1#comment-50 nrp Fri, 11 Apr 2008 06:48:58 +0000 http://eclecti.cc/code/a-dirty-hack-for-opencv-on-the-olpc-xo#comment-50 It turns out the actual problem is not with the colorspace as I suspected, but the field value. It is fixed in the latest CVS source. Changing line 414 from capture->form.fmt.pix.field = V4L2_FIELD_INTERLACED; to capture->form.fmt.pix.field = V4L2_FIELD_ANY; will fix the problem. The fix described in the post works, but this fix will more generally work for other cameras. It turns out the actual problem is not with the colorspace as I suspected, but the field value. It is fixed in the latest CVS source.

Changing line 414 from
capture->form.fmt.pix.field = V4L2_FIELD_INTERLACED;
to
capture->form.fmt.pix.field = V4L2_FIELD_ANY;
will fix the problem.

The fix described in the post works, but this fix will more generally work for other cameras.

]]>