From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: <kieran.bingham@ideasonboard.com>, <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 3/4] kms++util: Add verification module
Date: Mon, 18 Dec 2017 14:04:45 +0200 [thread overview]
Message-ID: <99e99d24-6ee3-884d-edf9-570fcbc5ab14@ti.com> (raw)
In-Reply-To: <4127740.6d2LxRg6UI@avalon>
On 18/12/17 13:50, Laurent Pinchart wrote:
> That's an option too. I had a look at the code once to find out how
> ImageMagick was performing scaling and gave up with a headache soon
> afterwards. We need more formats than what ImageMagick currently supports
> (it's mostly focused on image file formats instead of raw image formats), with
> all kind of RGB, YUV (and ideally Bayer) formats, and I don't think extending
> ImageMagick would be the way to go.
Yep, I can image that ImageMagick can't handle it all. I don't really
have much experience with it. I did find that it has enough tunables to
manage rgbx8888 with different byte orders and the "extra" alpha channel:
convert -depth 8 -size $1x$2 -color-matrix "0 0 1 0 1 0 1 0 0" -alpha
deactivate rgba:$3 png:-
But things like argb1555 or yuv422 might prove to be too difficult for
ImageMagick.
Where's the source for v4l2convert? What does it do?
I wonder how difficult it would be to create a
brute-force-no-optimizations style of a function to which you give the
exact bit definition of the buffer's pixel format, and which gives you
RGB888 or YUV444, depending on the input format (I presume most image
encoders would accept RGB888 & YUV444).
I think the function wouldn't even need to care whether the data is RGB
or YUV, it would just unpack it according to the format definition.
Tomi
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2017-12-18 12:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 23:10 [PATCH 0/4] kms++util: Provide validation helpers Kieran Bingham
2017-12-13 23:10 ` [PATCH 1/4] videodevice: Fix minor spacing Kieran Bingham
2017-12-18 11:23 ` Laurent Pinchart
2017-12-13 23:10 ` [PATCH 2/4] py: pyvid: Provide stream_off binding Kieran Bingham
2017-12-18 11:29 ` Laurent Pinchart
2017-12-13 23:10 ` [PATCH 3/4] kms++util: Add verification module Kieran Bingham
2017-12-15 13:43 ` Tomi Valkeinen
2017-12-16 16:13 ` Kieran Bingham
2017-12-18 11:36 ` Laurent Pinchart
2017-12-18 11:46 ` Tomi Valkeinen
2017-12-18 11:50 ` Laurent Pinchart
2017-12-18 12:04 ` Tomi Valkeinen [this message]
2017-12-18 15:41 ` Laurent Pinchart
2017-12-18 15:48 ` Tomi Valkeinen
2017-12-18 12:06 ` Geert Uytterhoeven
2017-12-18 11:49 ` Tomi Valkeinen
2017-12-13 23:10 ` [PATCH 4/4] kms++util: Add frame compare functionality Kieran Bingham
2017-12-14 8:52 ` Geert Uytterhoeven
2017-12-14 10:28 ` Kieran Bingham
2017-12-15 14:09 ` Tomi Valkeinen
2017-12-16 16:41 ` Kieran Bingham
2017-12-18 11:47 ` Laurent Pinchart
2017-12-13 23:17 ` [PATCH 0/4] kms++util: Provide validation helpers Kieran Bingham
2017-12-15 14:10 ` Tomi Valkeinen
2017-12-16 16:46 ` Kieran Bingham
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=99e99d24-6ee3-884d-edf9-570fcbc5ab14@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.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.