| To: | Thomas Koeller <thomas.koeller@baslerweb.com> |
|---|---|
| Subject: | Re: [PATCH] Image capturing driver for Basler eXcite smart camera |
| From: | Pavel Machek <pavel@ucw.cz> |
| Date: | Fri, 18 Aug 2006 08:27:37 +0000 |
| Cc: | Éric Piel <Eric.Piel@lifl.fr>, linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk, linux-mips@linux-mips.org |
| In-reply-to: | <200608172230.30682.thomas.koeller@baslerweb.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <200608102318.04512.thomas.koeller@baslerweb.com> <200608142126.29171.thomas.koeller@baslerweb.com> <20060817153138.GE5950@ucw.cz> <200608172230.30682.thomas.koeller@baslerweb.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.9i |
On Thu 17-08-06 22:30:30, Thomas Koeller wrote: > 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 If it is _common_, we definitely need an API. We do not want the next driver to reinvent it from scratch, right? -- Thanks for all the (sleeping) penguins. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] Remove mfinfo[64] used by get_wchan(), Atsushi Nemoto |
|---|---|
| Next by Date: | Re: [PATCH] Remove mfinfo[64] used by get_wchan(), Franck Bui-Huu |
| Previous by Thread: | Re: [PATCH] Image capturing driver for Basler eXcite smart camera, Thomas Koeller |
| Next by Thread: | Re: [PATCH] Image capturing driver for Basler eXcite smart camera, Bill Davidsen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |