linux-kernel - Re: New Driver for DaVinci DM355/DM365/DM6446

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090601155854.38350ab5@pedra.chehab.org>
Date:	Mon, 1 Jun 2009 15:58:54 -0300
From:	Mauro Carvalho Chehab <mchehab@...radead.org>
To:	"Paulraj, Sandeep" <s-paulraj@...com>
Cc:	"linux-media@...r.kernel.org" <linux-media@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Grosen, Mark" <mgrosen@...com>
Subject: Re: New Driver for DaVinci DM355/DM365/DM6446

Em Mon, 1 Jun 2009 13:39:17 -0500
"Paulraj, Sandeep" <s-paulraj@...com> 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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/