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] [day] [month] [year] [list]

Date:	Fri, 15 Jan 2010 09:33:11 -0800
From:	Greg KH <greg@...ah.com>
To:	Marin Mitov <mitov@...p.bas.bg>
Cc:	Scott Smedley <ss@....gov.au>, linux-kernel@...r.kernel.org
Subject: Re: [RFC] Yet another dt3155 driver for drivers/staging

On Thu, Jan 14, 2010 at 09:39:26PM +0200, Marin Mitov wrote:
> Hi Greg,
> > > 
> > > No. They are both standalone drivers. If we want V4L2 compatibility
> > > we would have to modify (either) driver significantly.
> 
> Both are character drivers. My one uses open, read, mmap, ioctl, close.
> Mainly tested on read. mmap works, but not yet extensively tested.
> ioctl is used to start/stop acquisition, get info about buffer length,
> and some error statistics collected during acquisitions.
> 
> see:
> 
> http://lfb.issp.bas.bg/~mitov/linux/dt3155pci/00README
> 
> for more detailed description.

Thanks, but the code needs to use the v4l interface, as it is a video
device.

> > Well, that will be the requirement to get it merged into the main
> > portion of the kernel tree.  No special interfaces are allowed, sorry.
> 
> I do not quite understand V4L2 lib in particular how can I get a
> contiguous buffer in physical memory which do not cross 4MB
> boundary (hardware requirement).

Try asking on the linux-media mailing list, I don't think this is a big
deal, as you have already done it in the driver, so that would not have
to be reworked.

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/