All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Thomas Koeller <thomas.koeller@baslerweb.com>
Cc: "Éric Piel" <Eric.Piel@lifl.fr>,
	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: Thu, 17 Aug 2006 15:31:38 +0000	[thread overview]
Message-ID: <20060817153138.GE5950@ucw.cz> (raw)
In-Reply-To: <200608142126.29171.thomas.koeller@baslerweb.com>

Hi!

> > If so then the Video4Linux2 API is still the best way to implement the
> > protocol to pass data between the user-space programs and the driver.
> > The V4L2 API doesn't says that the camera must be far away from the
> > processor, it can work for USB webcams, for Firewire video camera, PCI
> > TV tuners, and probably also for your device. Using the V4L2 not only
> > has the advantage of being a well tested API for communicating video
> > related information with the user-space but it also buys you the fact
> > that any program available on Linux for video should be able to directly
> > detect and use the captor!
> 
> Sorry, but no. The camera has been designed to be used in industrial
> control applications, such as quality assurance. Think of an automated
> inspection of a certain product, where the inspection is integrated
> into the production process. Faulty products are sorted out. For this to
> work it is absolutely necessary to get the maximum speed (image frames
> per second) out of the hardware, so image acquisition and processing
> must be carried out in parallel. The way to achieve this is have the
> driver manage a queue of image buffers to fill, so it will continue
> grabbing images even if no read operation is currently pending. Also,
> the ability to attach user-specific context information to every buffer
> is essential.

Well, I guess v4l api will need to be improved, then. That is still
not a reason to introduce completely new api...

-- 
Thanks for all the (sleeping) penguins.

  reply	other threads:[~2006-08-17 15: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 [this message]
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
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=20060817153138.GE5950@ucw.cz \
    --to=pavel@suse.cz \
    --cc=Eric.Piel@lifl.fr \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=thomas.koeller@baslerweb.com \
    --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 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.