From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Rob Herring <robh+dt@kernel.org>,
linux-tegra@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v1 0/2] NVIDIA Tegra20 video decoder driver
Date: Tue, 26 Sep 2017 08:54:47 +0200 [thread overview]
Message-ID: <20170926065447.GC6250@kroah.com> (raw)
In-Reply-To: <cover.1506377430.git.digetx@gmail.com>
On Tue, Sep 26, 2017 at 01:15:41AM +0300, Dmitry Osipenko wrote:
> This driver provides accelerated video decoding to NVIDIA Tegra20 SoC's,
> it is a result of reverse-engineering efforts. Driver has been tested on
> Toshiba AC100 and Acer A500, it should work on any Tegra20 device.
>
> In userspace this driver is utilized by libvdpau-tegra [0] that implements
> VDPAU interface, so any video player that supports VDPAU can provide
> accelerated video decoding on Tegra20 on Linux.
Why not use the v4l2 api instead? Doesn't that provide the same needed
user/kernel api here instead of creating yet-another-custom ioctl?
thanks,
greg k-h
next prev parent reply other threads:[~2017-09-26 6:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 22:15 Dmitry Osipenko
2017-09-25 22:15 ` [PATCH v1 1/2] staging: Introduce " Dmitry Osipenko
2017-09-25 23:01 ` Stephen Warren
2017-09-25 23:45 ` Dmitry Osipenko
2017-09-26 5:11 ` Stephen Warren
2017-09-26 12:02 ` Dmitry Osipenko
2017-09-27 9:45 ` Dan Carpenter
2017-09-27 23:28 ` Dmitry Osipenko
2017-09-28 7:23 ` Dan Carpenter
2017-09-28 11:37 ` Dmitry Osipenko
2017-09-27 23:31 ` Dmitry Osipenko
2017-09-25 22:15 ` [PATCH v1 2/2] ARM: dts: tegra20: Add video decoder node Dmitry Osipenko
2017-09-26 6:54 ` Greg Kroah-Hartman [this message]
2017-09-26 12:32 ` [PATCH v1 0/2] NVIDIA Tegra20 video decoder driver Dmitry Osipenko
2017-09-26 21:35 ` Greg Kroah-Hartman
2017-09-26 22:17 ` Dmitry Osipenko
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=20170926065447.GC6250@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
/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
Powered by JetHome