Laurent, Responses inline.
Sincerely, Chase Maupin Software Applications Catalog DSP Products e-mail: chase.mau...@ti.com phone: (281) 274-3285 For support: Forums - http://community.ti.com/forums/ Wiki - http://wiki.davincidsp.com/ > -----Original Message----- > From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com] > Sent: Thursday, February 25, 2010 6:35 PM > To: Maupin, Chase > Cc: Hans Verkuil; sakari.ai...@maxwell.research.nokia.com; > mche...@infradead.org; vpss_driver_des...@list.ti.com - This list is to > discuss the VPSS driver design (May contain non-TIers); linux- > me...@vger.kernel.org > Subject: Re: Requested feedback on V4L2 driver design > > 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 ? The proxy driver is the piece of code in the firmware that is actually exposing the VPSS API to the master CPU. It is responsible for listening for requests from the master CPU and then executing those requests on the VPSS CPU. Without the proxy there is no way to tell the VPSS CPU which functions to execute. > > > 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. Thanks for the input. We'll keep this in mind and see what we can do. > > By the way, will the firmware be loaded at runtime by the driver, or will > it > be stored internally in the chip ? The firmware will not be stored internally on the chip and will have to be loaded at runtime. We have not settled on how the loading will be done. Currently we are thinking on loading it from u-boot similar to an FPGA firmware load but it could also be done from the kernel. > > -- > Regards, > > Laurent Pinchart -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html