From: Vrihad S. <vr...@my...> - 2003-06-14 09:58:43
|
>> I am part of a team which is working on a linux based set top >> box project. It is based on SiS552 chipset. It contains an >> inbuilt hardware mpeg decoder. SiS is ready to supply a binary >> kernel module and a shared library. They will also provide the >> API specs for the library once we sign the NDA. > >how exactly do you pretend to write a xine plugin if the API is >protected by an NDA? Well, first of all there is a talk in the xine-devel list about support for via supplied hardware. If they can provide the API specs to a developer under NDA and the developer provides wrapper code along with a binary object, I think that can apply to this case too. In fact I hate to take this approach where 99% of your code is free software and for 1% you are forced to keep things under wraps. But that's the way some of the major companies do business :-( >i might be wrong, but i would say that it is ok to use >a binary kernel module. however, the shared library will >be linked to xine and thus must be GPL'ed (as well as >the plugin itself). This is quite interesting. Xine and GNU/Linux kernel both are under GPL. There is not a difference of a single character in licensing terms. Now if binary object file for kernel module is ok, then why similar object file is not applicable for xine? We will write wrappers for our own object file which will hide the API of SiS supplied module. In my opinion that's the only way to work under their NDA. Is there any other way? cheers vrihad _______________________________________________ No banners. No pop-ups. No kidding. Introducing My Way - http://www.myway.com |