From: Nicolas Dufresne <nicolas@ndufresne.ca>
To: Ming Qian <ming.qian@nxp.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"hverkuil-cisco@xs4all.nl" <hverkuil-cisco@xs4all.nl>
Cc: "shawnguo@kernel.org" <shawnguo@kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
dl-linux-imx <linux-imx@nxp.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [EXT] Re: [PATCH] media: amphion: only insert the first sequence startcode for vc1l format
Date: Fri, 08 Jul 2022 09:32:20 -0400 [thread overview]
Message-ID: <2f35d8250ce133e21eb3987977a92af583e32d0d.camel@ndufresne.ca> (raw)
In-Reply-To: <AM6PR04MB63416B4BA53E80123037AC8EE7809@AM6PR04MB6341.eurprd04.prod.outlook.com>
Le mercredi 06 juillet 2022 à 04:09 +0000, Ming Qian a écrit :
> > Can't you save the slow copy by using data_offset then ? I think most of the
> > confusion comes from this commit message, someone else then you should be
> > able to understand what it means.
>
> I'll modify the commit message that remove the unrelated vp8 description.
> And unfortunately the amphion vpu only support the ring buffer mode, so
> copying is inevitable.
Great thanks, I had forgotten that Amphion was based on a ring buffer. Indeed,
this is the way to go, same applied to CODA driver.
Nicolas
prev parent reply other threads:[~2022-07-08 13:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 5:20 Ming Qian
2022-06-29 12:10 ` Hans Verkuil
2022-06-29 12:53 ` [EXT] " Ming Qian
2022-06-29 13:03 ` Hans Verkuil
2022-06-29 13:08 ` Ming Qian
2022-07-04 16:05 ` Nicolas Dufresne
2022-07-05 2:00 ` [EXT] " Ming Qian
2022-07-05 11:27 ` Ming Qian
2022-07-05 12:59 ` Nicolas Dufresne
2022-07-06 4:09 ` Ming Qian
2022-07-08 13:32 ` Nicolas Dufresne [this message]
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=2f35d8250ce133e21eb3987977a92af583e32d0d.camel@ndufresne.ca \
--to=nicolas@ndufresne.ca \
--cc=festevam@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ming.qian@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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 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®