From: Peter Paul <abnominales@web.de>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: One Video Decoding API to rule them all
Date: Sat, 20 Feb 2010 11:29:31 +0100 [thread overview]
Message-ID: <1266661771.1707.4.camel@virtubuntu-alpha> (raw)
In-Reply-To: <22466.1266605284@localhost>
On Friday, 19.02.2010, 13:48 -0500 Valdis.Kletnieks@vt.edu wrote:
> What you need is a statement that API XYZ is the One True API, *and* statements
> from the non-XYZ vendors that they intend to move in that direction. Let's
> face it - if you don't get NVidia and AMD saying they're both going in the
> same direction, you end up having to support both directions no matter what
> we say regarding the desired direction.
I was more thinking of what the Open Source drivers will move to (e.g.
will Gallium3D support VDPAU or VA-API, will the CrystalHD API remain or
will it be changed to use VDPAU/VA-API).
next prev parent reply other threads:[~2010-02-20 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 16:39 One Video Decoding API to rule them all Peter Paul
2010-02-19 18:48 ` Valdis.Kletnieks
2010-02-20 10:29 ` Peter Paul [this message]
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=1266661771.1707.4.camel@virtubuntu-alpha \
--to=abnominales@web.de \
--cc=Valdis.Kletnieks@vt.edu \
--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