linux-kernel - Re: [RFC] Yet another dt3155 driver for drivers/staging

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20100114034055.GA27311@kroah.com>
Date:	Wed, 13 Jan 2010 19:40:55 -0800
From:	Greg KH <greg@...ah.com>
To:	Scott Smedley <ss@....gov.au>
Cc:	Marin Mitov <mitov@...p.bas.bg>, linux-kernel@...r.kernel.org
Subject: Re: [RFC] Yet another dt3155 driver for drivers/staging

On Thu, Jan 14, 2010 at 02:13:45PM +1100, Scott Smedley wrote:
> Hi Greg,
> 
> > We don't need to worry about older kernel versions from here on out.
> 
> Ok.
> 
> > So that leaves the functionality issues.   Is the only difference that
> > one can capture faster than the other?
> 
> As mentioned, Marin's driver only supports CCIR mode & it
> hasn't been tested with multiple boards.

Ah, ok.

> >  They should be using the v4l
> > apis so userspace shouldn't be a difference either, right?
> 
> No. They are both standalone drivers. If we want V4L2 compatibility
> we would have to modify (either) driver significantly.

Well, that will be the requirement to get it merged into the main
portion of the kernel tree.  No special interfaces are allowed, sorry.

Anyway, I suggest the two of you decide on a plan forward.

thanks,

greg k-h
--
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/