Le mardi 19 février 2008 11:11, Ilyes Gouta a écrit : > Hi! > > > > This leads me to belive two different scenarios > > > 1) The driver / BisonCam application is braindead and the software > > > scales everything. > > Oh yeah, that's a possibility. The windows driver for my > m5603c/mt9v011 does all the color conversion, filtering, noise > reduction in software, heh. I remember that the CPU utilization tops > at 70% during the capture which is insane and unpractical for a USB > device such as a cheap webcam. I think that a driver should reflect > the exact capabilities of the piece of hardware it's controlling.
Cheap webcam: that's the word. cheap implies delegates all processing to an external device, eg the main computer cpu. I recall that I have entirely reverseengeneered the windows driver for Ali5603c bisoncam except some specific video routines. Works for lot of sensors and sensor variations. And yes, the driver is minimalist in specific initializations. Lots of computation on every frame (awb, resize). Franck ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ M560x-driver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/m560x-driver-devel
