All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Dufresne <nicolas@ndufresne.ca>
To: Stanimir Varbanov <stanimir.varbanov@linaro.org>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	linux-media@vger.kernel.org
Subject: Re: [RFC/WIP 0/4] HEIC image encoder
Date: Fri, 11 Jun 2021 10:46:31 -0400	[thread overview]
Message-ID: <7bcab342492b41c952522c26eb2aaa497b90c5f8.camel@ndufresne.ca> (raw)
In-Reply-To: <3916c03f-9996-3de3-4365-3e88abf052d2@linaro.org>

Le vendredi 11 juin 2021 à 16:12 +0300, Stanimir Varbanov a écrit :
> > 
> > Would it be possible for the driver to handle this internally? I.e.,
> > if it detects that it needs to switch to grid mode, can it just encode
> > each grid and copy it in the capture buffer? This assumes that there is
> > metadata that can be used by a decoder do find and decode each grid.
> > 
> 
> In case that is is part of the spec I don't think we have to do it.
> Something more, when each tile is separate image the decoding process
> could be done in parallel.

Does it means there is no userspace (or at least no Open Source) userspace for
it ?



  reply	other threads:[~2021-06-11 14:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 13:28 [RFC/WIP 0/4] HEIC image encoder Stanimir Varbanov
2021-04-29 13:28 ` [RFC/WIP 1/4] media: Add HEIC compressed pixel format Stanimir Varbanov
2021-05-18 17:11   ` Nicolas Dufresne
2021-05-25  7:42     ` Stanimir Varbanov
2021-04-29 13:28 ` [RFC/WIP 2/4] v4l2-ctrls: Add HEIC grid size control Stanimir Varbanov
2021-04-29 13:28 ` [RFC/WIP 3/4] venus: helpers: Add a new helper for buffer processing Stanimir Varbanov
2021-04-29 13:28 ` [RFC/WIP 4/4] venus: Add HEIC image encoder Stanimir Varbanov
2021-05-18 17:07 ` [RFC/WIP 0/4] " Nicolas Dufresne
2021-05-24 13:16   ` Stanimir Varbanov
2021-05-27  7:54 ` Hans Verkuil
2021-06-11 13:12   ` Stanimir Varbanov
2021-06-11 14:46     ` Nicolas Dufresne [this message]
2021-06-12  8:45       ` Stanimir Varbanov

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=7bcab342492b41c952522c26eb2aaa497b90c5f8.camel@ndufresne.ca \
    --to=nicolas@ndufresne.ca \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=stanimir.varbanov@linaro.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.