Hello, Laurent, About using daemon, we have proprietary image processing and optimization code that needs to sit between application and driver. I wasn't working on V4L2 at the time, but this constraint was discussed in the 2010 mini summit. And it was mentioned in section (1) of http://www.linuxtv.org/news.php?entry=2010-06-22.mchehab. Regards, Shuzhen -----Original Message----- From: Laurent Pinchart [mailto:laurent.pinchart@xxxxxxxxxxxxxxxx] Sent: Wednesday, November 24, 2010 4:02 AM To: Shuzhen Wang Cc: linux-media@xxxxxxxxxxxxxxx; 'Hans de Goede' Subject: Re: Zooming with V4L2 Hi Shuzhen, On Monday 22 November 2010 23:51:41 Shuzhen Wang wrote: > Hello, Laurent, > > I Get the logic you have behind using cropping/scaling. > > The reason I wanted to use V4L2_CID_ZOOM_ABSOLUTE are that the application > will have a simpler interface to control zoom level supported by the > hardware (yet may be less flexible). In other words, the driver gives out > the zoom range, and the application doesn't need to calculated different > cropping windows. By doing this we don't add policies into the driver, > because in our implementation the request is forwarded by the driver to a > user space daemon, who in turn talks back to the driver to control the > hardware. That's even worse. No userspace daemons please. > I guess I will need to conform to the cropping/scaling interface then. -- Regards, Laurent Pinchart -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
