From: Antonio Ospite <ao2@ao2.it>
To: Matt Ranostay <matt@ranostay.consulting>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Attila Kinali <attila@kinali.ch>, Marek Vasut <marex@denx.de>
Subject: Re: [RFC] v4l2 support for thermopile devices
Date: Thu, 3 Nov 2016 08:35:33 +0100 [thread overview]
Message-ID: <20161103083533.9ebc9c88d883b09bf16d44c0@ao2.it> (raw)
In-Reply-To: <CAJ_EiSQRai=XqOryMW1WLKvFDPZUVVmkjXSF3TyxpPNMsVsR_Q@mail.gmail.com>
On Wed, 2 Nov 2016 23:10:41 -0700
Matt Ranostay <matt@ranostay.consulting> wrote:
> On Fri, Oct 28, 2016 at 7:59 PM, Matt Ranostay <matt@ranostay.consulting> wrote:
> > On Fri, Oct 28, 2016 at 2:53 PM, Hans Verkuil <hverkuil@xs4all.nl> wrote:
> >> Hi Matt,
> >>
> >> On 28/10/16 22:14, Matt Ranostay wrote:
> >>>
> >>> So want to toss a few thoughts on adding support for thermopile
> >>> devices (could be used for FLIR Lepton as well) that output pixel
> >>> data.
> >>> These typically aren't DMA'able devices since they are low speed
> >>> (partly to limiting the functionality to be in compliance with ITAR)
> >>> and data is piped over i2c/spi.
> >>>
> >>> My question is that there doesn't seem to be an other driver that
> >>> polls frames off of a device and pushes it to the video buffer, and
> >>> wanted to be sure that this doesn't currently exist somewhere.
> >>
> >>
> >> Not anymore, but if you go back to kernel 3.6 then you'll find this driver:
> >>
> >> drivers/media/video/bw-qcam.c
> >>
> >> It was for a grayscale parallel port webcam (which explains why it was
> >> removed in 3.7 :-) ), and it used polling to get the pixels.
> >
> > Yikes parallel port, but I'll take a look at that for some reference :)
>
>
> So does anyone know of any software that is using V4L2_PIX_FMT_Y12
> currently? Want to test my driver but seems there isn't anything that
> uses that format (ffmpeg, mplayer, etc).
>
> Raw data seems correct but would like to visualize it :). Suspect I'll
> need to write a test case application though
>
You could add a conversion routine in libv4lconvert from v4l-utils to
have a grayscale representation of Y12, I did something similar for the
kinect depth map, discarding the least significant bits:
https://git.linuxtv.org/v4l-utils.git/commit/lib/libv4lconvert?id=6daa2b1ce8674bda66b0f3bb5cf08089e42579fd
After that any v4l2 program using libv4l2 will at least be able to show
_an_ image.
You can play with "false color" representations too in libv4lconvert,
however I don't know if such representations are generic enough to be
mainlined, in the Kinect case the false color representation of the
depth map was done in specialized software like libfreenect.
Ciao,
Antonio
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
next prev parent reply other threads:[~2016-11-03 8:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 20:14 Matt Ranostay
2016-10-28 20:30 ` Devin Heitmueller
2016-10-28 20:40 ` Marek Vasut
2016-10-29 2:56 ` Matt Ranostay
2016-10-29 2:58 ` Matt Ranostay
2016-10-28 21:53 ` Hans Verkuil
2016-10-29 2:59 ` Matt Ranostay
2016-11-03 6:10 ` Matt Ranostay
2016-11-03 7:35 ` Antonio Ospite [this message]
2016-11-03 8:41 ` Hans Verkuil
2016-11-03 13:21 ` Attila Kinali
2016-11-03 15:11 ` Luca Barbato
2016-11-04 5:11 ` Matt Ranostay
2016-11-17 17:31 ` Sakari Ailus
2016-11-26 13:16 ` 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=20161103083533.9ebc9c88d883b09bf16d44c0@ao2.it \
--to=ao2@ao2.it \
--cc=attila@kinali.ch \
--cc=hverkuil@xs4all.nl \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=marex@denx.de \
--cc=matt@ranostay.consulting \
/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
all inboxes | Powered by JetHome®