From: Thomas Koeller <thomas.koeller@baslerweb.com>
To: "Bill Davidsen" <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk,
linux-mips@linux-mips.org,
"Thomas Köller" <thomas@koeller.dyndns.org>
Subject: Re: [PATCH] Image capturing driver for Basler eXcite smart camera
Date: Tue, 22 Aug 2006 23:36:12 +0200 [thread overview]
Message-ID: <200608222336.12137.thomas.koeller@baslerweb.com> (raw)
In-Reply-To: <44E5BE77.9040200@tmr.com>
On Friday 18 August 2006 15:19, Bill Davidsen wrote:
>
> Don't take it personally, just write working code people can patch in.
> When your code has the features you mentioned it will be highly useful
> and hopefully ported to many devices. I guess security monitoring is an
> "industrial image processing application," which interests me. At the
> moment I would call it an impressive proof of concept, but you have many
> useful ideas for its future.
I am not offended at all, I certainly agree with Pavel's opinion of 'do
not invent new interfaces needlessly'. But this is a use case significantly
different from what the v4l2 api is aimed at.
As I wrote earlier, if it were not for other reasons, then changing the
API is not an option because the software already ships. I can place the
driver somewhere else in the kernel tree. I can fix any issues that
someone may find with it. I certainly cannot replace it with something
entirely different. If it is rejected, my only option is to submit the
rest of the code, without the capturing driver (the platform is already
in the kernel tree). Some may feel that a camera that cannot capture
images is somewhat pointless, though...
Of course, everyone is free to write a v4l2 driver, but will likely
find that the hardware is not very suitable as a streaming video
device. At least, it would be a very expensive one...
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-22 21:36 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
2006-08-18 8:27 ` Pavel Machek
2006-08-18 13:19 ` Bill Davidsen
2006-08-22 21:36 ` Thomas Koeller [this message]
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=200608222336.12137.thomas.koeller@baslerweb.com \
--to=thomas.koeller@baslerweb.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=thomas@koeller.dyndns.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