From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: camera application for testing (was Re: v4l subdevs without big device)
Date: Sun, 1 May 2016 21:21:31 +0200 [thread overview]
Message-ID: <20160501192131.GH14243@amd> (raw)
In-Reply-To: <20160501140831.GH26360@valkosipuli.retiisi.org.uk>
Hi!
> >
> > What is reasonable camera application for testing?
> >
> > N900 looks like a low-end digital camera. I have now have the hardware
> > working (can set focus to X cm using command line), but that's not
> > going to be useful for taking photos.
>
> I guess you already knew about omap3camd; it's proprietary but from purely
> practical point of view it'd be an option to support taking photos on the
> N900. That would not be extensible any way, the best possible functionality
> is limited what the daemon implements.
>
> I'm just mentioning the option of implementing wrapper for the omap3camd so
> that it can work with upsteam APIs, I don't propose that however.
I knew it existed, but I'd prefer not to touch proprietary code.
> > In particular, who is going to do computation neccessary for
> > autofocus, whitebalance and exposure/gain?
>
> I think libv4l itself has algorithms to control at least some of these. It
> relies on the image data so the CPU time consumption will be high.
>
> AFAIR Laurent has also worked on implementing some algorithms that use the
> histogram and some of the statistics. Add him to cc list.
Aha, good, let me know.
> > There's http://fcam.garage.maemo.org/gettingStarted.html that should
> > work on maemo, but a) it is not in Debian, b) it has non-trivial
> > dependencies and c) will be a lot of fun to get working...
> >
> > (and d), will not be too useful, anyway, due to 1sec shutter lag:
>
> I believe this will be shorter nowadays. I don't remember the exact
> technical solution which the text below refers to but I'm pretty sure it'll
> be better with the current upstream. API-wise, there's work to be done there
> (to port FCAM to upsteram APIs) but it's a possibility.
I took a look at fcam-dev in the meantime... and it does not look too
bad. It is quite n900-specific -- it needs hardware support for
histograms and sharpness maps -- but it should not be too hard to
modify.
Relying on hardware support without having fallback software
implementation feels wrong, but... it should actually be ok as I
already have the hardware...
(Is there accepted "upstream" for it?)
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2016-05-01 19:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 8:45 drivers/media/i2c/adp1653.c: does not show as /dev/video* or v4l-subdev* Pavel Machek
2016-04-29 7:15 ` v4l subdevs without big device was " Pavel Machek
2016-04-29 7:31 ` Hans Verkuil
2016-04-29 7:56 ` Sakari Ailus
2016-04-29 9:50 ` Pavel Machek
2016-04-29 10:59 ` Sakari Ailus
2016-04-29 11:05 ` Pali Rohár
2016-04-29 11:23 ` Sakari Ailus
2016-04-29 14:06 ` Pavel Machek
2016-04-29 10:15 ` Pavel Machek
2016-04-29 21:30 ` [pre-rfc] focus and flash for Nokia N900 (was Re: v4l subdevs without big device was Re: drivers/media/i2c/adp1653.c: does not show as /dev/video* or v4l-subdev*) Pavel Machek
2016-04-29 22:13 ` camera application for testing (was Re: v4l subdevs without big device) Pavel Machek
2016-04-29 22:20 ` Pali Rohár
2016-04-29 22:47 ` Ivaylo Dimitrov
2016-05-01 14:08 ` Sakari Ailus
2016-05-01 19:21 ` Pavel Machek [this message]
2016-06-21 22:32 ` Pavel Machek
2016-06-21 23:59 ` Laurent Pinchart
2016-06-22 11:52 ` Pavel Machek
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=20160501192131.GH14243@amd \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).