All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marin Mitov <mitov@issp.bas.bg>
To: Greg KH <greg@kroah.com>
Cc: Scott Smedley <ss@aao.gov.au>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Yet another dt3155 driver for drivers/staging
Date: Thu, 14 Jan 2010 21:39:26 +0200	[thread overview]
Message-ID: <201001142139.26837.mitov@issp.bas.bg> (raw)
In-Reply-To: <20100114034055.GA27311@kroah.com>

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.
> 
> 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).

Thanks,

Marin Mitov

  reply	other threads:[~2010-01-15  7:41 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 [this message]
2010-01-15 17:33                 ` Greg KH
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=201001142139.26837.mitov@issp.bas.bg \
    --to=mitov@issp.bas.bg \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.