public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Scott Smedley <ss@aao.gov.au>
Cc: Marin Mitov <mitov@issp.bas.bg>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Yet another dt3155 driver for drivers/staging
Date: Wed, 13 Jan 2010 19:40:55 -0800	[thread overview]
Message-ID: <20100114034055.GA27311@kroah.com> (raw)
In-Reply-To: <20100114031345.GA22542@aao.gov.au>

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

  reply	other threads:[~2010-01-14  3:40 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 [this message]
2010-01-14 19:39               ` Marin Mitov
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=20100114034055.GA27311@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