From: Marin Mitov <mitov@issp.bas.bg>
To: ss@aao.gov.au
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Yet another dt3155 driver for drivers/staging
Date: Thu, 14 Jan 2010 21:23:57 +0200 [thread overview]
Message-ID: <201001142123.57736.mitov@issp.bas.bg> (raw)
In-Reply-To: <20100114010335.GB20569@aao.gov.au>
Hi Scot & Greg,
>
> I'd be interested in Marin's opinion as he appears to have used both
> drivers extensively.
I have successfully used SourceForge(SF) driver since 2003 on 2.4.xx
kernels till the time of 2.6.17 kernel when I switched to 2.6.17 as described in
http://lfb.issp.bas.bg/~mitov/linux/dt3155pci/00README
At this time I needed 1 fps, so the SF driver was OK for me.
>
> I'd like a userspace program to actually try out Marin's driver
I have one using KDE 3.5 libraries. If you use KDE 3.5 I could send it to you.
> , 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.
Since today it could do 30 fps as well :-). Updated.
> - 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.
Since today - here also.
> - It is well tested.
> - It works with most kernel versions. ie. 2.2, 2.4, & 2.6. (mostly)
Production tested/used (every day use) on 2.6.27.43-i686.
Compile tested on 2.6.33.-rc4-x86_64 :-)
> - It works with multiple boards.
Here in principal - also, but not tested.
> - 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.)
>
> Marin, if you are considering upgrading your driver, I propose
> we send an email to the DT3155 SF mailing list & ask for help
> testing.
OK. I agree. Which kind of upgrade you mean?
If CCIR/RS-170 - it is already done (but not tested on RS-170,
I have no such camera).
I would ask your help for contacting "the DT3155 SF mailing list & ask for help"
> (I already know of 1 other person who is happy to help
> test.) I recommend making userspace programs (like examples/acquire
> & examples/Xview in the SF driver) available first. Ideally, these
> example programs & user space libraries would become the major
> component of the evolved DT3155 SF project.
Here I could propose a KDE program, but it needs KDE, I am not familiar
with GNOME programing.
Marin Mitov
prev parent 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
2010-01-15 17:33 ` Greg KH
2010-01-14 19:23 ` 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=201001142123.57736.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.