public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marin Mitov <mitov@issp.bas.bg>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: use videobuf2 framework for drivers/staging/dt3155v4l driver
Date: Wed, 29 Jun 2011 21:17:39 +0300	[thread overview]
Message-ID: <201106292117.40272.mitov@issp.bas.bg> (raw)
In-Reply-To: <20110629042124.GA18344@kroah.com>

On Wednesday, June 29, 2011 07:21:24 am Greg KH wrote:
> On Wed, Jun 29, 2011 at 06:46:02AM +0300, Marin Mitov wrote:
> > On Tuesday, June 28, 2011 11:25:15 pm Greg KH wrote:
> > > On Sat, May 28, 2011 at 09:45:27PM +0300, Marin Mitov wrote:
> > > > This patch transforms drivers/staging/dt3155v4l driver to use videobuf2 framework.
> > > > Tested and works with "xawtv -f".
> > > > 
> > > > Either streaming API or read method should be selected during kernel configuration.
> > > 
> > > I've applied this, but why would you ever not want to use the streaming
> > > api?
> > 
> > There are no reasons for that, sure, but for now xawtv do not work if both are
> > specified in the driver. I have to debug it.
> 
> Ok, but why not just remove the read method then?  Or do some userspace
> programs still require it?

In current version if you select streaming API you effectively remove read method.
If you select read method you effectively remove streaming API. At lest this is
what userland programs are seeing as driver capabilities.

For now I see some changes in videobuf2-core are in discussion. When they become part
of the kernel I will test the driver again.

Thanks.

Marin Mitov

> 
> greg k-h
> 

      reply	other threads:[~2011-06-29 18:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-28 18:45 [PATCH] use videobuf2 framework for drivers/staging/dt3155v4l driver Marin Mitov
2011-06-28 20:25 ` [PATCH] staging: " Greg KH
2011-06-29  3:46   ` Marin Mitov
2011-06-29  4:21     ` Greg KH
2011-06-29 18:17       ` Marin Mitov [this message]

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=201106292117.40272.mitov@issp.bas.bg \
    --to=mitov@issp.bas.bg \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    /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