From: Peter Paul <abnominales@web.de>
To: linux-kernel@vger.kernel.org
Subject: One Video Decoding API to rule them all
Date: Fri, 19 Feb 2010 17:39:00 +0100 [thread overview]
Message-ID: <1266597540.2383.20.camel@virtubuntu-alpha> (raw)
Hi,
currently we've got three APIs to accelerate video decoding in hardware,
but to cover all available video decoding hardware, an application
writer would have to support all of them.
There is VDPAU which has a prominent supporter with nvida and is
implemented by the proprietary nvidia and S3 driver.
Than there is VA-API that is implemented in the proprietary poulsbo
driver and that can use VDPAU or AMD's proprietary XvBA as a backend.
And more recently we got CrystalHD that is implemented by Broadcom's
eponymous driver and targets their dedicated video decoding chips.
Now there are already applications that take advantage of one or more of
those APIs, but hardly anyone can support all of them, thus always
excluding users of specific hardware.
I think it would therefore be helpful to have an official statement
which API is the preferable one so, that the open source drivers and
applications could migrate to that one.
Regards,
Peter
next reply other threads:[~2010-02-19 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 16:39 Peter Paul [this message]
2010-02-19 18:48 ` One Video Decoding API to rule them all Valdis.Kletnieks
2010-02-20 10:29 ` Peter Paul
2010-02-20 14:19 ` Felipe Contreras
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=1266597540.2383.20.camel@virtubuntu-alpha \
--to=abnominales@web.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox