From: Thomas Koeller <thomas.koeller@baslerweb.com>
To: Pavel Machek <pavel@suse.cz>
Cc: "Éric Piel" <Eric.Piel@lifl.fr>,
linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk,
linux-mips@linux-mips.org
Subject: Re: [PATCH] Image capturing driver for Basler eXcite smart camera
Date: Thu, 17 Aug 2006 22:30:30 +0200 [thread overview]
Message-ID: <200608172230.30682.thomas.koeller@baslerweb.com> (raw)
In-Reply-To: <20060817153138.GE5950@ucw.cz>
On Thursday 17 August 2006 17:31, Pavel Machek wrote:
> Well, I guess v4l api will need to be improved, then. That is still
> not a reason to introduce completely new api...
The API as implemented by the driver I submitted is very minimalistic,
because it is just a starting point. There's more to be added in future,
like controlling flashes, interfacing to line-scan cameras clocked by
incremental encodes attached to some conveyor, and other stuff which
is common in industrial image processing applications. You really do
not want to clutter the v4l2 API with these things; that would hardly
be an 'improvement'.
Different interfaces, designed to serve different purposes...
Thomas
--
Thomas Koeller, Software Development
Basler Vision Technologies
An der Strusbek 60-62
22926 Ahrensburg
Germany
Tel +49 (4102) 463-390
Fax +49 (4102) 463-46390
mailto:thomas.koeller@baslerweb.com
http://www.baslerweb.com
next prev parent reply other threads:[~2006-08-17 20:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 21:18 [PATCH] Image capturing driver for Basler eXcite smart camera Thomas Koeller
2006-08-11 19:35 ` Randy.Dunlap
2006-08-11 20:09 ` Alan Cox
2006-08-12 17:27 ` Thomas Koeller
2006-08-14 15:53 ` Éric Piel
2006-08-14 19:26 ` Thomas Koeller
2006-08-17 15:31 ` Pavel Machek
2006-08-17 20:30 ` Thomas Koeller [this message]
2006-08-18 8:27 ` Pavel Machek
2006-08-18 13:19 ` Bill Davidsen
2006-08-22 21:36 ` Thomas Koeller
2006-08-11 20:48 ` Dave Jones
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=200608172230.30682.thomas.koeller@baslerweb.com \
--to=thomas.koeller@baslerweb.com \
--cc=Eric.Piel@lifl.fr \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=pavel@suse.cz \
/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