From: Attila Kinali <attila@kinali.ch>
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>, Marek Vasut <marex@denx.de>,
Luca Barbato <lu_zero@gentoo.org>
Subject: Re: [RFC] v4l2 support for thermopile devices
Date: Thu, 3 Nov 2016 14:21:34 +0100 [thread overview]
Message-ID: <20161103142134.4a59dfc34c593391086c0508@kinali.ch> (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:
>
> 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
I was pretty sure that MPlayer supports 12bit greyscale, but I cannot
find where it was handled. You can of course pass it to the MPlayer
internas as 8bit greyscale, which would be IMGFMT_Y8 or just pass
it on as 16bit which would be IMGFMT_Y16_LE (LE = little endian).
You can find the internal #defines of the image formats in
libmpcodecs/img_format.h and can use https://www.fourcc.org/yuv.php
to decode their meaning.
The equivalent for libav would be libavutil/pixfmt.h
Luca Barbato tells me that adding Y12 support to libav would be easy.
Attila Kinali
--
It is upon moral qualities that a society is ultimately founded. All
the prosperity and technological sophistication in the world is of no
use without that foundation.
-- Miss Matheson, The Diamond Age, Neil Stephenson
next prev parent reply other threads:[~2016-11-03 13:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 20:14 [RFC] v4l2 support for thermopile devices 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
2016-11-03 8:41 ` Hans Verkuil
2016-11-03 13:21 ` Attila Kinali [this message]
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=20161103142134.4a59dfc34c593391086c0508@kinali.ch \
--to=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=lu_zero@gentoo.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;
as well as URLs for NNTP newsgroup(s).