Re: New Driver for DaVinci DM355/DM365/DM6446

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Em Mon, 1 Jun 2009 13:39:17 -0500
"Paulraj, Sandeep" <s-paulraj@xxxxxx> escreveu:

> > > [Sandeep] WE don't propose any API changes. This module for which we  
> > want to submit patches is a TI proprietary IP. We currently implement this
> > as a character device and have a few IOCTL's.  
> > > We do not follow the V4L2 framework and do not use any V4L2 IOCTLs.
> > >
> > > Can we continue to use it as a character driver?  
> > 
> > In this case, I don't see why you want it to be upstream.  
> [Sandeep] TI customers and TI itself want to see this driver part of open source trees. Considering this we would like to submit our patches to the linux-media mailing list.
> IS this OK?

If you're just providing a character API with some protocol protected by IP,
you're not providing the source code of the driver, but something else. 

It is not ok to provide such driver. 

Also, even if you disclosure your protocol, it makes no sense to create another
API for userspace communication, for features that already exists or can easily
expand to accommodate your needs. 

So, you should really use the V4L2 API for the driver, expanding it where
required, if you want it to be considered for upstream addition.



Cheers,
Mauro
--
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

[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux