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 18:36:55 -0800 [thread overview]
Message-ID: <20100114023655.GA25618@kroah.com> (raw)
In-Reply-To: <20100114010335.GB20569@aao.gov.au>
On Thu, Jan 14, 2010 at 12:03:36PM +1100, Scott Smedley wrote:
> Hi Greg & Marin,
>
> > > Scott, any comparison between the two of them as to which one actually
> > > works better?
>
> I'd be interested in Marin's opinion as he appears to have used both
> drivers extensively.
>
> I'd like a userspace program to actually try out Marin's driver, but
> I can still make some general comments:
>
> Things I like about Marin's driver:
> - It is only ~1/3rd the size. (by counting new lines)
> - The code is much neater.
> - It can acquire frames at 25 fps (real-time), according to Marin.
> - At least 1 person with intimate knowledge of the code seems keen to
> maintain it.
>
> Things I like about the sourceforge (SF) driver:
> - It works in CCIR mode (768x576) or 640x480 mode.
> - It is well tested.
> - It works with most kernel versions. ie. 2.2, 2.4, & 2.6. (mostly)
> - It works with multiple boards.
> - The code is moderately well commented.
> - It includes simple (user space) example programs.
>
>
> Clearly each driver has strengths over the other.
>
> It would probably be easier to upgrade Marin's driver to match the
> strengths of the SF driver than the other way around. The only
> difficulty might be in making Marin's driver work with older kernel
> versions. IMO, that's probably an acceptable sacrifice to make. (For
> users of legacy systems, we could point them to the (unmaintained)
> driver on SF.)
We don't need to worry about older kernel versions from here on out.
That will make the one in the staging tree smaller as well, as the
compatibility code will soon be deleted.
So that leaves the functionality issues. Is the only difference that
one can capture faster than the other? They should be using the v4l
apis so userspace shouldn't be a difference either, right?
thanks,
greg k-h
next prev parent reply other threads:[~2010-01-14 2:43 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 [this message]
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
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=20100114023655.GA25618@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