Hi Chase, On Tuesday 16 February 2010 14:00:11 Maupin, Chase wrote: > Laurent, > > To follow up with some of the comments I made before I got additional > clarification about the commands supported by the proxy driver running on > the VPSS MCU. The proxy will support all of the commands used by V4L2 as > well as those proposed extensions to V4L2 that Hans has mentioned. > Basically, the list of commands supported at initial release is not only > those required today, but a full set for all the features of the VPSS. In > this was as new APIs are added to V4L2 the support for those features will > already be supported by the VPSS MCU proxy driver. Thank you for the clarification. A few things are still uncleared to me, as stated in my previous mail (from a few minutes ago). My main question is, if the VPSS API is full-featured and accessible from the master CPU, why do we need a proxy driver in the firmware at all ? > As for the license of the firmware this is still being worked. It is > currently under TI proprietary license and will be distributed as binary > under Technical Software Publicly Available (TSPA) which means it can be > obtained by anyone. If you feel that source code is required for the > firmware at launch to gain acceptance please let us know and we can start > working that issue. I think it would definitely help keeping the Linux driver and the VPSS firmware in sync if the VPSS firmware source was available. The firmware source code could even be distributed along with the Linux driver. By the way, will the firmware be loaded at runtime by the driver, or will it be stored internally in the chip ? -- 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
