public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Marin Mitov <mitov@issp.bas.bg>
Cc: Scott Smedley <ss@aao.gov.au>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Yet another dt3155 driver for drivers/staging
Date: Fri, 15 Jan 2010 09:33:11 -0800	[thread overview]
Message-ID: <20100115173311.GA10695@kroah.com> (raw)
In-Reply-To: <201001142139.26837.mitov@issp.bas.bg>

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

  reply	other threads:[~2010-01-15 18:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 20:42 [RFC] Yet another dt3155 driver for drivers/staging Marin Mitov
2010-01-12 23:52 ` Scott Smedley
2010-01-13  0:17   ` Greg KH
2010-01-13  6:16     ` Marin Mitov
2010-01-14  1:03       ` Scott Smedley
2010-01-14  2:36         ` Greg KH
2010-01-14  3:13           ` Scott Smedley
2010-01-14  3:40             ` Greg KH
2010-01-14 19:39               ` Marin Mitov
2010-01-15 17:33                 ` Greg KH [this message]
2010-01-14 19:23         ` Marin Mitov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100115173311.GA10695@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mitov@issp.bas.bg \
    --cc=ss@aao.gov.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox