yeah my mistake eitehr try the camera with a usb 2.0 port if you have one whcih should automatically turn of jpeg support. or you will have to download and recompile libv4l with a patch that will drop bad jpeg frames. the link to the libv4l source and patch are listed below
libv4l source: http://people.atrpms.net/~hdegoede/libv4l-0.5.8.tar.gz libv4l patch: http://groups.google.com/group/microdia/tree/browse_frm/thread/9c8fac5c2af46e49/0d8172a2ed78ddea#doc_b4b3d001b02f388a On Thu, Mar 12, 2009 at 5:35 PM, GWater <[email protected]> wrote: > Am Donnerstag 12 März 2009 22:24:20 schrieb Brian Johnson: >> Ok so it seems that you defiantly have a mt9v112 sensor on slave >> address 0x48. So not only does the 6270 seem to use at least 3 >> different sensors the mt9v112 sensor seems to use two different slave >> addresses as well. >> >> What exactly do you mean by blinking? Are getting any valid picture at >> all? it looks from your mplayer output you are suffering from the fact >> that sometimes libv4l has issues decoding jpeg frames. You could just >> disable jpeg on our driver by using "insmod ./sn9c20x.ko jpeg=0" when >> loading the driver and see if the picture is any better. >> >> Also i'm attaching an updated version of the mt9v112 sensor probe >> patch that will make the probe function check both 0x5d and 0x48 slave >> addresses please make sure it still works for your sensor. you can >> apply it wih the following commands >> # git fetch >> # git reset --hard origin/HEAD >> # git am </path/to/patch file> >> > > Appending "jpeg=0" is a bad idea since the driver decided that the usb > connection is to slow for bayer or yuv422. > > GWater > > --~--~---------~--~----~------------~-------~--~----~ Lets make microdia webcams plug'n play, (currently plug'n pray) To post to this group, send email to [email protected] Visit us online https://groups.google.com/group/microdia -~----------~----~----~----~------~----~------~--~---
